Delegation Is a Sequence, Not a Moment

Delegation is taken for a moment when it is an order of steps

The question of how to delegate usually arrives in the room dressed as a technical one: which work, to whom, by when. The executive asking it has generally tried already. The work was declared someone else's in a meeting, the calendar was cleared, a few weeks passed, and then the same work came back. The second attempt is worded more firmly. There is no third attempt; the work is simply done again by the person who meant to hand it over.

The cause is rarely the wrong person. When delegation is staged as a single moment, what gets handed over is the task; what needed handing over was the way the task gets decided. A task can be given in one sentence. A decision right cannot, because a decision right only changes hands after it has been used a few times in front of the person who used to hold it.

The moment a handover is judged to have failed

Most executives count the handover as failed the first time the work returns. The early returns are ordinary, though; they belong to learning rather than to the handover. The real signal is different: when the work comes back, the executive does not hand it over again, but finishes it. At that point the handover has not stalled, it has been cancelled — and because the cancellation is silent, the team reads it as a verdict.

There is a second misreading beside it. Work slows down in the first weeks after it changes hands, and the slowdown gets taken as evidence that the person cannot carry it. Delegated work always runs slower for a while, because its new owner is learning the work and the rules of the work at the same time. Measuring that stretch against the previous owner's pace is the quietest way to end a handover before it has begun.

This piece is not about why the work stays on the desk, which is a different question. It is about the order to follow once the decision to hand over has already been made.

Three sentences that have to be written down

The first version of a handover conversation is almost always incomplete, because it describes the work and not its edge. The team takes the work, does not know the edge, and comes back to check at every step. The executive reads this as either disinterest or a lack of confidence. Usually it is neither; it is the attention of someone walking through an area nobody has marked out. Someone who does not know the edge is not asking in order to avoid a mistake, but to find out how far they are allowed to go.

Three sentences hold a handover up, and all three are short:

• The decision boundary: how large a call can be made without asking. Written in money, in time, or in how reversible the thing is.
• The return threshold: the one condition under which the work comes back. It is a single line rather than a list, and it loses its meaning as it lengthens.
• The review rhythm: when the outcome gets discussed, and against which numbers. Without a date, a review turns into a repossession.

A handover made without those three sentences is a well-meant guess, and a team working from a guess picks the safest available option, which is to ask. The traffic of questions in the first weeks is usually the bill for the missing lines rather than a sign of the wrong person. Once the three are written, most of that traffic falls away within a few weeks, because there is less left to ask.

A boundary is not the same thing as a rule

A boundary states how large a decision may be. A rule states how the decision is made. They are separate, and never having written the rule down is a different fault in the same handover. The three sentences here set the boundary; the rule transfers by making a few decisions together inside it.

The four stages of withdrawing

The version of delegation that works moves in the same order nearly every time. The order can be compressed and cannot be skipped; where it is skipped, the work returns and the return gets read as the other person's limitation.

• First stage: the decision is made together, with the reasoning said out loud. The point is not the decision but making its construction visible.
• Second stage: the team decides and says so before acting. The executive does not correct here, only marks where their own reading differs.
• Third stage: the team decides and acts, and the executive hears about it afterwards. This is the uncomfortable one, and most handovers stop here.
• Fourth stage: the executive keeps only the review rhythm and stays out of individual calls.

What moves a handover between stages is repetition rather than time: once a few decisions of the same kind land where they were expected to, the next stage opens. A handover tied to the calendar arrives early or never; a handover tied to repetition finds its own pace. The only record worth keeping is which decisions were made at which stage; without it, progress is judged by feeling, and feeling always argues for taking the work back.

What the third stage costs

The third stage is the first point at which something is genuinely given up, and the thing given up is not authority but information. Some things will now be learned after they have happened. In the room this gets discussed as trust. More often it is the loss of an information habit, and it comes from the same place as the thinning of what reaches the top.

Delegation completes at the first mistake

Every piece of delegated work eventually produces a bad call. That call is the test, and the test is not in the decision but in whose hands the correction passes through. If the executive corrects it personally, the handover ends there. If the team corrects it and the executive discusses only the outcome, the handover is complete.

The quiet cost of taking the correction back

Correcting it personally always looks cheap in the short run: it is faster, the damage is smaller, nobody argues. The cost lands on the team and lands late. A team corrected once will not choose the riskier option the second time; by the third it asks first. The handover still stands on paper and has been withdrawn in practice.

The real date of a handover is therefore not the day the work was given, but the day the first mistake was repaired by the team that made it. Everything before that is preparation, and the length of the preparation depends less on the size of the work than on what the executive does the first time something goes wrong.

From the room

When someone arrives saying they do not know how to delegate, the first move is not to discuss who should take what. It is to pick one piece of work already considered handed over and find which of the four stages it stopped at. Most often it stopped at the second: the team decides, the executive approves, and the arrangement has been mistaken for a handover for months.

The room's work here is not encouragement but showing where the sequence was cut — once the cut is located, the next step rarely needs an argument. The difficult part comes after it, in the first mistake the executive has to let pass through someone else's hands, and most of what we discuss belongs to those few weeks.

Delegation is not a test of character; it is work with an order to it. Requesting a conversation begins by finding which stage a supposedly delegated piece of work stopped at.