Jeroen Sangers logo Jeroen Sangers

Removing your own ability to give in makes you stronger in a negotiation

If you can always give in a little more in a negotiation, you automatically give the other side a reason to keep pushing: after all, there is still room. The counterintuitive solution is to remove that room yourself. Give up, in advance, the authority to move any further, and the pressure disappears. Not because you negotiate harder, but because there is simply nothing left to gain by insisting.

This is exactly what a salesperson does with “I’ll have to check with my manager”: they can no longer make concessions themselves, so they become much harder to move than if they could make the call. You can use the same mechanism for yourself by giving a third party the deciding vote: a partner who has to agree, or a fixed threshold above which you automatically pause. You stay the friendly, reasonable person, while the room to negotiate is fixed somewhere else.

The pattern also works against you when you don’t recognise it. Every time you say “in principle” or “usually”, you signal, without meaning to, that the exception is open for negotiation. A boundary that leaves no room for interpretation rarely gets tested.

Delegating a task without the why delegates the action, not the judgment

Almost any task beyond the basics requires decisions along the way: which version, which tone, how much depth. If you hand over only the instruction and not the reason behind it, the other person has nothing to hold on to except that instruction. The moment the situation drifts from what was written down, there is nothing to fall back on, and the work lands back on your desk for you to decide.

That is why delegating without explaining often feels like losing time rather than gaining it. You get back something that doesn’t quite fit and end up redoing it. It works the other way too: when someone delivers far more than needed, it is rarely slowness. More often the scope was unclear, and they assumed more depth than a few bullet points required.

The why of a task is only half of it. The other half is your general judgment, which usually lives in your head: whom you consult first, what you need to know before committing, how you weigh cost against quality. Make it explicit and your team can decide without waiting for you. Two concrete things help. First, say what “good enough” means right now, because under a heavier workload the bar tends to drop and nobody says so out loud. Second, set the threshold for escalating: from which client, which amount or which risk you want to be told.

That is the difference between delegating tasks and delegating authority. With the first, the work leaves your desk but the decisions keep waiting for you. With the second, both leave, and the task makes more sense to the person doing it, because they can see where it fits.

A goal only counts as a goal when you can force the outcome yourself, otherwise it is a dream

We often call something a goal when it is really a dream: an outcome we want, but one that depends largely on other people’s decisions, on timing or on luck. Making the bestseller list, hitting a revenue target, getting hired: it feels concrete and measurable, so it gets the label “goal”. But as soon as someone else decides the result, your own effort becomes necessary without being enough. That difference is exactly why SMART goals so often frustrate. They check whether a goal is specific, measurable and time-bound, and never ask who holds the outcome.

The distinction is more than semantics. It shapes how motivation behaves. As long as you see a clear link between your effort and the result, intrinsic motivation holds up. Once that link breaks, a downward spiral begins: a weaker sense of control leads to less effort, less effort produces a worse result, and that result confirms the feeling of helplessness. A dream treated as a goal undermines the very motivation the goal was meant to spark.

The answer is to keep the ambition and rewrite the goal into something that sits entirely in your own hands. Instead of “bring in 2 million euros in revenue”, the goal becomes “hold 40 sales conversations”. The dream, the revenue, stays in place as a direction, while the goal itself moves out of reach of external factors. That also makes it more unforgiving: there is no market, no competitor and no bad timing left to blame. You either did it or you didn’t.

The real win in delegating is letting go completely, and that takes competence

When you delegate, you hope to save time. But the win you actually feel is a different one: you hand something over and stop thinking about it. No checking back, no low hum of worry, no drama. That only happens when the person you delegate to does it well, does it on time and does it without fuss. Delegating to competence is the one kind of delegating that empties your head; every other kind moves the work from your hands to your attention.

Few people know that feeling. Until recently it was reserved for those who worked with exceptional colleagues or teams. AI assistants suddenly put it within reach of many more people, and that explains a large part of the excitement around them: not the technology itself, but the new experience of being able to let go.

The catch is in the word competence. The first time you hand something over, to a colleague or to an AI, the verdict is often: it doesn’t get me, it did it wrong. That is rarely the receiver’s fault and usually the brief’s: saying precisely what you want is hard, and the context that is obvious inside your head is missing on the other side. If you want the relief of letting go, invest first in clarity and context. Competence on the other end is half the story. The other half is that you make it possible for them to be competent.

Shared rituals give a team meaning, and they work best when the team invents them

A ritual is a habit that has picked up meaning. That is the whole difference: a habit is what you do, a ritual is how you do it, with attention and with intent. Brushing your teeth is a habit. Always brushing before you shower, and finding it odd the other way round, has become a ritual. The reversed-order test is a tool rather than a definition: it points to the place where an action has acquired meaning.

People use rituals to steer their mood: to calm down before a performance, to gear up for a hard task, to wash the workday off. Telling yourself to relax rarely works, because failing at it feels like one more failure. A familiar pattern does work, because it asks for repetition rather than achievement.

In a team, a shared ritual does something extra. People who perform a small ritual together before they start, even something as silly as tapping their shoulders and stamping their feet, rate the work that follows as more meaningful than people who do the same ritual alone. Tea at a fixed hour on a fixed day, closing every meeting by naming one thing a team member pulled off, sharing weekend plans before the agenda: small things, and precisely because they wear in, they start to carry meaning. Fast-growing companies build their whole planning cadence as a series of rituals for the same reason, so everyone knows what each moment means.

Imposed team building beats doing nothing, even when everyone complains: at least they hated it together. A ritual announced from above, six claps and three shouts at the start of every meeting, mostly harvests eye rolls. Let the team invent its own. A leader’s job is to make the room where a ritual can emerge, and then to protect it, consistently.

Behaviour follows its consequences: what gets rewarded grows, what gets punished fades, and what gets rewarded irregularly sticks best

Voluntary behaviour is shaped by what follows it. When an action brings something pleasant, the odds that you repeat it go up. When it brings something unpleasant, they go down. You never have to decide any of this: behaviour adapts to its consequences whether you notice or not.

Underneath that sits a second layer that is easy to miss. It is not only whether a reward arrives that counts, but when and how often. The same behaviour with the same reward can be learned fast or slowly, and can stick weakly or strongly, depending purely on the rhythm in which the reward is handed out. That rhythm is called a reinforcement schedule.

The surprising part is that irregular rewards work better than constant ones. Behaviour that is rewarded only some of the time lasts longer, even after the reward disappears. The logic, as Scott Young lays it out, runs like this: a predictable reward that stops has probably run out. An unpredictable reward that stops may just be a pause, so carrying on pays. That is the mechanism behind the slot machine and behind the apps you keep opening. Once every reward is gone for good, the behaviour slowly sinks back to its old level.

For anyone building a habit, breaking one, or steering a team, this is a practical handle. A child who gets a compliment right after finishing homework learns something different from a child who hears it at the end of the week, and an employee who knows good work gets seen repeats that work. If you want to change behaviour, look beyond the reward itself to the moment and the rhythm in which you give it.

Motivation grows with the perceived distance to the goal, not the real one

The closer you get to a goal, the harder you push. A marathon runner who spots the finish line suddenly finds energy that was nowhere to be found a kilometre earlier. That is not willpower, it is proximity: the reward comes into view and the effort pulls itself along.

What makes this interesting is that the brain responds to perception here, not to facts. A loyalty card with twelve boxes, two of them already stamped, gets filled faster than an empty card with ten boxes, even though the work in both cases is exactly ten stamps. The head start is fictional. The acceleration is real.

That is the lever for anyone who wants to get themselves or others moving. Give a head start, so the first step already looks taken. Make progress visible, so the distance to the finish becomes something you can feel. And cut a big goal into small milestones, so there is always a finish nearby instead of one far away. The effect is strongest in people who feel they have little power or security; those who already feel comfortable need the proximity less.

An indexed PKM of sources and personal syntheses makes a truly personal AI possible

The usual way to give an LLM your documents is to upload them, or to plug in retrieval (RAG). For every question the model hunts down the relevant fragments in the raw sources and pieces together an answer. It works, but nothing builds up. A question that combines five documents gets answered from scratch again next time.

The alternative is a PKM in two layers. The sources sit untouched in a raw layer. Above them lives an indexed layer of summaries, concept notes and cross-references that gets updated with every new source: contradictions flagged, the synthesis revised. Knowledge is compiled once and then kept current. When a question comes in, the LLM reads the index first and then the relevant notes. Up to a few hundred notes that is enough, with no search infrastructure at all.

What turns this into a truly personal AI is the feedback loop. A good answer, whether a comparison, an analysis or a connection you spotted, goes back into the system as a new note. Your own explorations pile up the same way your sources do. The system then holds what you read and what you thought about it, and every next question draws on both.

A PKM built from sources plus atomic notes already has those two layers. The LLM only needs to do the maintenance: indexing, cross-referencing, checking for consistency. Once the system grows large enough, fine-tuning is the next step, so the knowledge lives in the model’s weights instead of its context window.