How to Delegate as Your Team Grows

Tool: Skills Matrix · Time: 1 to 2 days

Before handing anything over, find out who could take it. A skills matrix lists the skills the work needs down one side and the people across the top, and rates each person on each skill. The scale matters less than honesty. People rate themselves more candidly when they are told, in writing, that the grid will not feed pay reviews.

Rate the leader too. The point is to find the skills only the leader has, because those are the tasks stuck in the leader's inbox.

Skip it if: you already have a current, honest skills matrix. Few teams do.

Tool: Delegation Matrix · Time: an afternoon

List everything the leader does in a normal fortnight. Then sort each task on two things: how important it is, and how skilled the best available person is. Stage 1 already answered the second question, so this stage is quick.

Each quadrant has its own answer. Important work with a skilled person: delegate fully. Important work with nobody skilled: keep it for now and train someone. Less important work with a skilled person: delegate with check-ins. Less important work with nobody skilled: stop doing it.

Then do the step most leaders skip. For each task you hand over, say how much authority goes with it: decide and tell me, decide after asking me, or bring me a recommendation. A handover without that sentence gets checked back up the line.

Skip it if: you only have one or two tasks to hand over. Just hand them over.

Tool: RACI Matrix · Time: half a day

Stage 2 decided who takes each task. Once work is spread across more people, the harder question is who decides. A RACI matrix lists each decision down the side and each role across the top, and puts one of four letters in each cell. Every decision gets exactly one A.

Read the draft row by row, looking for two things. Two A's in one row means two people each think the other has decided, so the decision sits. A row full of C's means a decision so many people must approve that it slows everything down.

Skip it if: the team is small enough that everyone hears every decision anyway.

RResponsible

Does the work

AAccountable

Owns the decision and answers for it

CConsulted

Asked for a view before the decision

IInformed

Told after it is made

Tool: Psychological Safety · Time: 4 to 6 weeks after the handovers

Delegation fails quietly when people hide problems. A new owner who fears blame will sit on a slipping deadline until the client calls. Psychological safety is a team's shared belief that it is safe to speak up, ask questions and admit mistakes.

It is measured, not assumed. A short survey helps, but behavior tells you more. Watch how bad news arrives, and what the leader does with a decision someone else made. Check it now, before stage 5 starts judging people on results.

Skip it if: never, once you have handed over anything that matters.

Tool: OKR · Time: 1 to 2 weeks, in one planning cycle

A task handed over as a task comes back as questions. An outcome handed over comes back as a result. OKR stands for objectives and key results. The objective is a short, plain statement of what should change. The key results, usually two to four, are numbers that show whether it did.

The test for each key result is simple. Could someone complete it by working through a checklist? If yes, it is a task, not a result. Rewrite it as the change the task is meant to cause.

Skip it if: the handed-over work is routine and has no outcome worth measuring.

Tool: Succession Planning · Time: 2 to 3 days, then yearly

Delegation creates new key roles. If the tech lead leaves, release sign-off lands back on the founder's desk overnight. Succession planning names the roles the business can't afford to lose, and finds who could step into each.

Be honest about readiness. Ready now, ready in a year or two, and no one yet are all useful answers. The third is the one that tells you whom to hire or develop next.

Skip it if: the team is small and every role has a clear backup already.