"I don't know what to hand over to my team." Start with decisions, not tasks.
You cannot work out what to hand over because nothing in the business is written down as a decision limit. Task lists fail: they move the work and keep the authority with you, so everything routes back within a month. What transfers cleanly is an outcome, with a number the owner can see and a limit they can act inside.
The short answer
Stop trying to delegate tasks. Hand over outcomes, each with a named owner, a visible number and a written limit on what they can decide without you. Do it in that order — visibility, then authority, then ownership — and the questions stop coming. Do it as a list of jobs and you will be re-absorbing them by the end of the quarter.
The reason the exercise feels impossible is that you are trying to answer "what should they do?" when the real question is "what are they allowed to decide?" The first has a thousand answers. The second has about a dozen, and once they are written down, the tasks sort themselves.
Why the task list does not work
Most founders begin with an honest brain-dump of everything they do in a week, then try to assign lines to people. It fails for a structural reason, not a personal one: a task can be done without any authority, so the person doing it still has to come back to you at every point where a decision is needed. You have delegated the typing and kept the deciding.
| Handing over a task | Handing over an outcome | |
|---|---|---|
| What moves | The activity. "Chase the overdue invoices." | The result and the authority to reach it. "Debtor days under 45, and you decide what to offer to get there." |
| Who decides | Still you, at every exception. | The owner, inside a written limit; you only above it. |
| How you find out | When they ask, or when it goes wrong. | From a number, weekly, before it goes wrong. |
| When it slips | It lands back on your desk. | The owner explains it in the leadership meeting and says what they are changing. |
The right-hand column is what Accountability Design means in practice: one owner per outcome, not one person per job.
What to hand over, in order
This takes an afternoon to draft and one meeting to put in place. It is the same sequence I use inside every engagement, because it is the only order in which it holds.
- List the decisions, not the jobs. Go through the last fortnight and write down every decision that reached you — not tasks, decisions. Approving a quote. Agreeing a refund. Signing off a hire. Choosing which client to prioritise. Most founders find thirty to fifty.
- Sort them by kind, not by urgency. Spend, pricing, people, client commitments, delivery scope. Five or six categories will cover almost everything. The urgency ordering is what has kept you stuck; it makes every decision look unique.
- Set a limit for each category. A value, a threshold, or a rule. "Discounts up to 10% without asking." "Spend to £2,000 inside an approved budget." "Any refund under £500." This is the Decision Authority map, and it is the single document most businesses never write.
- Name one owner per category, and give them the number. Not a team, a person. Then make sure they can see the figure that tells them whether it is working — margin on their jobs, debtor days, utilisation. An owner who cannot see the number will keep coming to you, because you can.
- Say it once, in the room, and then hold to it. One leadership meeting: here are the categories, here are the limits, here is who owns what from Monday. Then the hard part — when someone brings you a decision inside their limit, hand it back. The first fortnight decides whether the map is real.
The two things to keep, for now
Not everything should move on day one. Two things stay with you until the structure underneath them exists, because handing them over early creates a different kind of bottleneck.
The cash position, until it is a system rather than a feeling. If the forward view of cash lives in your head, nobody else can safely make a spending decision, however clear their limit. Build the 30 to 90 day forward view first — Financial Visibility — then the spend authority becomes usable.
Any outcome whose number nobody can see. Ownership without visibility is asking someone to be accountable for something they cannot measure. If you cannot show them the figure weekly, you have not finished building the thing you are handing over.
What happens when they do not take it
This is the fear behind the whole exercise, and it is worth naming: you hand something over, and it does not get picked up. It comes back, or it quietly stops happening, and you conclude your team is not ready.
In practice the transfer failed at one of three points, all of them structural. The owner could not see the number, so they could not tell whether they were doing well. The limit was never written, so the safe move was to ask. Or there was no meeting where the outcome was reviewed by name, so nothing ever asked them for it. Fix whichever is missing and try again with the same person before concluding anything about the person.
Ownership does not transfer by announcement. It transfers when someone can see the number, knows their limit, and is asked about it every week.
If you have done all three and it still returns, then you have learned something real about an individual, and that is a different conversation. Most founders never get to find out, because the structure was never in place to test it.
What the business looks like on the other side
The first change is a drop in interruptions. Decisions inside a limit get made the day they arise, by the person closest to them. The second is that the weekly leadership meeting starts producing decisions rather than updates, because each person arrives owning something specific with a number attached — that is Leadership Rhythm doing its job.
The third takes longer and matters most: the business keeps operating at full capacity when you are not in it. If the underlying pattern is one you recognise, the companion piece asks whether a team that cannot manage without you is a leadership problem or a structural one; and the reason they ask you about everything is set out in why your team asks you about everything.
Common questions
Should I hire an assistant first?
Not yet. An assistant takes tasks, and you have not yet worked out which decisions to keep. Delegating jobs one by one without fixing the authority underneath them means the assistant becomes another person routing questions to you. Do the decision map first; it takes an afternoon. Then an assistant, if you still need one, has a clear brief.
Should I write the procedures first?
Write the decision limits before the procedures. A procedure tells someone how to do a task; it does not tell them what they may decide when the task hits an exception, which is exactly where they come back to you. Most businesses that document everything and still bottleneck through the founder have procedures and no authority map.
What if my team is not senior enough to own outcomes?
Test it before you conclude it. Set a small limit, give them the number, review it weekly for a month. Most people rise to a defined boundary quickly, because it removes the risk of guessing wrong. If a specific person genuinely cannot hold an outcome with the structure in place, you now know that with evidence rather than a feeling, and the role — not the map — is what needs changing.
How long does it take?
The map, an afternoon. The first handover meeting, an hour. The point where the questions noticeably stop, two to four weeks, provided you hold the line when decisions inside a limit come back to you. Financial visibility, if it has to be built from nothing, four to eight weeks alongside.
Do I need outside help to do this?
Not for the first draft. The method above is deliberately one you can run yourself. Where founders bring me in is when the first attempt has already returned once — usually because the numbers people need were never built, or because holding the line inside your own business is harder than it sounds. That is the point at which a fractional COO installs the structure and stays until your team holds it without either of us.
Not sure where to start?
The Operational Clarity Call is a focused 30 minutes to establish which decisions are currently routing through you, which should not be, and what would have to exist for your team to hold them. Diagnostic and direct, not a sales pitch. If you can do it yourself from the method above, you will be told so.
