![The fear that follows a successful handover is rarely said out loud, and it sounds like this: if...]()
The fear that follows a successful handover is rarely said out loud, and it sounds like this: if the work runs without me, what exactly am I for?
Owners who name that early tend to design past it. Owners who leave it unnamed answer it by taking something back, usually within a month, usually something that had already transferred cleanly.
There are three destinations available to a recovered hour and only one of them is worth having. Reabsorption sends the hour back into the work just moved, and every individual instance of it is defensible, which is why it is nearly invisible while it happens.
Adjacency sends it sideways into other operational work, which feels like progress and produces none. Forward work is the third, and its signature is specific: it produces nothing measurable this week, it cannot be delegated without changing what the business is, and skipping it costs nothing today.
That combination is exactly why forward work loses every hour it has to compete for. It needs a claim of its own, made in advance.
Which of the three took the last hour a handover gave back?![Most leaders push the task first and manage the resistance afterwards. The order that actually...]()
Most leaders push the task first and manage the resistance afterwards. The order that actually works is the reverse.
Design the conditions that make a task takeable, then offer it, and half the resistance never appears. In practice that is three things settled in advance. What comes off their plate to make the room real. What they are allowed to get wrong without it landing on them in public. Where the edge of their call sits, written down, so they are not reading the leader's mood for the answer.
None of that is generosity. It is the difference between handing someone a live decision and handing them a trap with someone else's name on the exit.
The goal is not to persuade a reluctant person into a seat that is not ready. It is to finish the seat, so the offer mostly carries itself.
What would need settling before the offer, rather than after?![The fear that keeps most handovers stuck on one desk is rarely about the quality of the work. It is...]()
The fear that keeps most handovers stuck on one desk is rarely about the quality of the work. It is the fear of offering something, hearing a no, and being left holding it with less standing than before.
That fear eases once the no is read properly, because a capable person's no almost always comes from one of three places. No room means they are already full, and the task was an addition rather than a transfer. No safety means a past decision was overruled in a way that stuck, and the caution is learned. No clarity means the boundary between their call and the leader's has never been drawn, so declining beats guessing.
Only one of the three is really about the person, and it is the least common of the three. The other two are conditions the business built and the business can change. Naming the right one is the difference between a motivation conversation that goes nowhere and a repair that holds.
Which of the three is sitting in a team right now, wearing the costume of the other two?![Always wonderful to recieve 5-star feedback!]()
Always wonderful to recieve 5-star feedback! ![Two people were offered the same step up. One asked what else she could take on. The other went...]()
Two people were offered the same step up. One asked what else she could take on. The other went quiet and found reasons the timing was wrong.
The easy read is that one wants it and one does not, so you build around the one who does. The more accurate read starts with a different question. What happened the last time the quiet one made a call without checking?
Often the answer is a decision that was walked back in public, more than once, for work that turned out to be sound. That is not a shortage of ambition. It is a person doing precisely what the last two years taught them to do.
A culture where reaching for more feels safe enough that both of them ask is not a personality outcome. It is a design one, and the design is the leader's to build.
What has the business quietly taught its quiet people to do?![A capable person operating inside an undefined boundary spends part of every week on a calculation...]()
A capable person operating inside an undefined boundary spends part of every week on a calculation that has nothing to do with the work.
Where does this decision sit. Whether asking looks prudent or looks like they cannot cope. What happened the last time somebody in that seat decided without checking first.
None of it appears on a workload review, and all of it consumes capacity the business is already paying for.
When the boundaries get defined, that background noise drops away quickly. The work does not reduce. The weight of the uncertainty around the work does, and the difference shows up on the drive home rather than in the diary.
Designing yourself out of the daily running is usually framed as a founder's project, measured in a founder's recovered hours. From the other seats in the business it reads quite differently. It looks like the week the organisation finally said out loud what it actually trusted people to do.
If someone's weekends feel busier than their workload explains, the question worth asking is which part is the job and which part is the uncertainty around it.![A nine-year accounting practice, eleven staff, one process transferred twice. The first attempt...]()
A nine-year accounting practice, eleven staff, one process transferred twice.
The first attempt moved a monthly client review pack by written checklist. Ninety minutes of documentation, a due date, a standing offer to ask questions. The receiver executed accurately for two cycles. An unusual client situation arose in the third. She escalated it, it was resolved in four minutes, and the pack was permanently back on the founder's desk within a fortnight.
The second attempt began with a conversation that had seemed unnecessary the first time. Five previous packs reviewed together, the judgement calls narrated aloud and written down in her words rather than his. Four escalation triggers defined with the reasoning behind each.
Everything else stated as hers to call, including the calls that might turn out wrong.
The pack has now held through two month-ends. The larger result showed up somewhere nobody was looking: across the rest of her role, escalations fell by close to half within three months, with no additional authority formally granted.
Procedure cannot travel beyond the task it describes. Reasoning is portable, and a receiver who holds it will extend it everywhere.![Five processes can move off a desk while every judgement call inside them continues to return to...]()
Five processes can move off a desk while every judgement call inside them continues to return to it. The result is a busier business and an unchanged bottleneck, which is why delegation goals framed around task volume so often produce months of effort and no structural change.
Decision load measures the thing underneath. Over one representative week, log every decision that arrives at the founder's desk. Against each, ask whether someone else could have made it competently, given the reasoning and a defined boundary. The proportion answering yes is the number that matters.
First counts typically land between sixty and eighty per cent. Leaders find this uncomfortable, which makes it useful, since the discomfort is doing the diagnostic work. A high figure is not a verdict on the team. It is a measure of how much reasoning has never been made explicit.
A realistic quarterly target moves the figure by fifteen to twenty percentage points.
Attempts at more fail on the same mechanism every time: transfers made faster than the reasoning behind them can be shared will bounce, and a bounced transfer costs more trust than it ever saved in time.![Most escalation is not a confidence problem or a capability problem. It is an information problem,...]()
Most escalation is not a confidence problem or a capability problem. It is an information problem, and the missing information is where authority actually ends.
Authority in most organisations is inherited rather than designed. It gets assembled from precedent, a handful of remembered corrections, and one uncomfortable meeting several years ago that nobody has revisited since.
Facing an unfamiliar decision with no map, the rational move is always to send it upward. That escalation is cheap for the sender and expensive for the organisation, and it accumulates until a leader concludes the team lacks initiative.
The Decision Rights Map removes the guesswork in under an hour per role. Three columns, every recurring decision sorted, every entry in the escalate column carrying a stated reason.
Where the sorting is contested, the disagreement is the finding. It names an assumption that was invisible to both parties until the question was asked directly.
A handover without this map moves the task and leaves the boundary undefined. A handover with it moves the task and the authority together, which is the only version that holds under pressure.![A senior accountant was given one process in March. By June she had stopped seeking approval on...]()
A senior accountant was given one process in March. By June she had stopped seeking approval on four other things, and nobody had formally granted her any of them.
She was not overstepping. She had read the handover accurately as evidence about where the boundaries of her judgement actually sat, and acted on the reading.
This is the return that goes unmodelled. A transfer is treated as a subtraction from one desk, measured in hours recovered. On the other side of the desk it is an addition of a different kind, and it rarely stays inside the boundary of the task it arrived in.
Week 3 of this series crosses the desk. The founder's side of a handover has had two weeks of attention. The receiver's side is where the compounding actually happens, and most organisations have never measured it.
What has someone in your business quietly stopped asking about?![A founder I coach took his family to the coast for ten days last month and did not open his laptop...]()
A founder I coach took his family to the coast for ten days last month and did not open his laptop once. When he told me, he said it almost apologetically, as though stepping away that completely was a small failure of commitment.
It was the opposite. The reason he could disappear was not discipline, and it was not luck. It was that the business had become genuinely boring to run without him. Every capability the business claimed was owned by someone other than him, written down somewhere other than his head, and wired with a signal that would flag a problem long before it reached a client.
The lifestyle most owners say they want gets described in terms of freedom, which makes it sound like an indulgence. It is not. It is the visible result of a business that operates what it announces, where the owner has made themselves unnecessary to the daily running on purpose.
Boring to run is the highest compliment a system can earn. The drama lives in the businesses that depend on one person staying reachable.
What would have to be true for you to go genuinely unreachable for ten days? If that feels impossible right now, the booking link is in our bio.![A professional services firm told a client, in writing, that its new platform would produce the...]()
A professional services firm told a client, in writing, that its new platform would produce the month-end advisory pack automatically. Month-end arrived. The platform produced something, and it was wrong.
The figures did not reconcile, an exception the test data had never contained went unhandled, and the result reached a client who had been promised an automated one. The gap between what the firm announced and what it operated had been invisible right up until the moment it became expensive.
What the firm did next is the part worth studying. The common move is to retreat: quietly stop calling the function automated, go back to the manual process, treat the platform as a disappointment. That closes the embarrassment without closing the gap, and the next month-end fails the same way.
This firm treated the wrong pack as a design brief instead. The missed exception showed them what their process did not handle. The absence of anyone who caught it first showed them they had no signal for failure. Six weeks later they operated the capability they had only announced, and could finally demonstrate it on request.
When did you last treat a failure as a brief rather than an embarrassment?![An accountant I work with set himself a goal last quarter that sounded almost too small to write...]()
An accountant I work with set himself a goal last quarter that sounded almost too small to write down. He wanted every capability his firm advertised to actually exist when someone asked for it.
It is the lowest possible bar, and it turned out to be the hardest work he did all year. Closing the distance between what the firm announced and what it operated meant admitting how much had only ever worked in a demonstration.
He started where most people do not, which was not the documentation. He named an owner for each claimed capability, someone whose job formally included running it. Then he built a way to know, within a week, if each one had stopped working. The manual came last, because writing down a capability nobody owns just produces a longer description of the gap.
By the end of the quarter the firm advertised less and operated more of it. The proposals got shorter. The demonstrations got easier, because there was finally something to demonstrate.
Which of your advertised capabilities would survive a request to prove it this week? If you would like help mapping that, the booking link is in our bio.![A capability is easy to announce and slow to operate. The distance between the two is where most...]()
A capability is easy to announce and slow to operate. The distance between the two is where most business risk now lives, and it tends to stay invisible until someone outside the business asks for a demonstration.
There is a blunt test for that distance. Take any capability you have claimed, to a client, a board, or your team, and ask three things. Who runs it when no one is watching. Where is it written. How would you know this week if it had quietly stopped working.
The third question is the one almost everyone skips, and it is usually the one that matters most. A capability with no signal for failure is one you are trusting blindly. This is the pattern behind AI washing: a function described as automated or AI-enabled that nobody can quite demonstrate when it counts.
Run the test on one of your own capabilities this week. If the answers are uncomfortable, that discomfort is a design brief, not a verdict.
Which of your announced capabilities would survive all three questions?![A founder I work with told me about the morning she stopped quietly bracing herself. It was not a...]()
A founder I work with told me about the morning she stopped quietly bracing herself. It was not a sales record or a funding round that did it. It was the realisation that every capability her business advertised was one it could actually demonstrate, owned by someone other than her, and she no longer had to hope nobody asked the wrong question.
That bracing is more common than owners admit. It is the low background hum of hoping a client does not test the thing you described a little too confidently in a proposal. Most people carry it for years and assume it is just what running a business feels like.
It is not. It is the feeling of a gap between what you have announced and what you operate, and it goes away when you close the gap rather than manage it. A business that can prove what it claims is calmer to run, worth more to a buyer, and far less dependent on one person staying in the room.
This week is about how you get there, starting with what it actually looks like.
What would change for you if you stopped hoping nobody asked? If you would like help closing that gap, the booking link is in our bio.
