Decision Delegation Lab

Grow your team’s judgement by handing down the decisions you’re still holding.

Decision Delegation Lab

What this fixes

You’d like the team to step up, but the important decisions keep coming back to you. The honest reason usually sounds reasonable: they’re not quite ready for this one.

Here’s the harder version. They’ve never actually been given the decision - so they’ve never had the chance to learn it. The team isn’t under-capable. It’s under-practised because it hasn’t been trusted with the decision. And it isn’t about today’s decision: every decision you keep is one the team never gets to make, which is why their judgement stays where it is.

This isn’t about blaming yourself. You’re protecting outcomes you’re accountable for, and that’s understandable. This tool helps you hand real decisions down safely, so your protection stops limiting your team’s growth.

How this works

Example: a lead lists the decisions they still make - which bugs ship in the release, when to escalate to the client, how to spend the tooling budget. On the ladder, all three sit at “I decide alone”. They move the bug call down a rung: a named engineer decides, within guardrails (anything customer-facing or over a day’s work comes to the lead), reviewed in two weeks - to talk about the judgement, not to take it back.

First, list the decisions you’re still holding and place each on the ladder. Then move two or three real decisions down a rung with clear guardrails. Finally, set a review to coach the person’s judgement - not to take the decision back.

The combination is what makes it work. The ladder on its own is just self-awareness; guardrails on their own are ordinary delegation. Together they make the transfer safe - the decision genuinely moves to a named person, and explicit limits keep the outcome protected.

This is your own work, done quietly. You’re examining where you’re still holding on - usually alone, in twenty focused minutes, before you talk to anyone.

Time required

Solo ✓   About 20–25 minutes to work through the ladder and plan the transfers.

The time required is indicative and will depend on how many decisions you’re holding.

Read the short reflection guide first - about 6–8 minutes. It is a downloadable PDF on this page.

When to use

Bring your real decision load - the decisions that actually come to you in a normal month.

Use it whenever:

  • you’re the bottleneck and the team is waiting on your calls
  • you keep thinking “they’re not ready” about the same decisions
  • someone on the team has stopped growing and you can’t say why
  • you want to develop the team deliberately, not just when there’s spare time

Not the right tool if: you’re trying to free up your own time - that’s a workload question, not a development one; this tool grows the team’s judgement and a lighter load is only a side effect. If you need to strengthen your ownership of decisions you already hold, that’s Decision Ownership Drill. For getting a single meeting to produce decisions, use Decision-Driven Meetings.

What you get

  • A clear picture of the decisions you’re still holding
  • Two or three decisions genuinely handed down, each with a named owner
  • Guardrails and a review date for each - safe transfer, not a leap

You’ve done it well when: someone else makes a real decision you used to make, inside guardrails you both agreed - and you find out about it at the review, not before.

What you’ll notice

  • How many decisions you were holding without deciding to
  • That “they’re not ready” often means “they’ve never been asked”
  • Every decision you keep is one the team never practises

Why this works

People learn judgement by making decisions, not by watching someone else make them. Every decision you keep is one the team never practises. The ladder exposes where you’re still holding decisions, while guardrails make it safe to hand them down - protecting the outcome you’re accountable for while the decision genuinely changes hands.

What you need

Your real decision load. The decisions that actually come to you in a normal month - not a job description. Be specific; vague categories can’t be handed down.

Named people, not roles. A decision handed to “the team” goes to no one. Each transferred decision needs a person’s name on it.

The ladder sheet (supplied). Where you place each decision on the rungs, choose which to move, and record the owner, guardrails and review date.

Willingness to be surprised. They may decide differently from you. If only your answer is acceptable, you haven’t delegated the decision - you’ve delegated the work.

Steps

  1. List the decisions you hold (5 min). Write the decisions that come to you in a normal month. Be specific - “which bugs ship”, not “quality decisions”.
  2. Place each on the ladder (5 min). From “I decide alone” to “the team decides”. Put each decision where it honestly sits today, not where you’d like it to sit.
  3. Choose two or three to move down a rung (4 min). Choose decisions that matter. If the decision has no real consequence, it won’t grow judgement. Name the person who now owns each.
  4. Set the guardrails (4 min). For each: the limits inside which they decide freely (budget, scope) and the triggers that must come to you. Guardrails make it safe; a silent veto makes it pointless.
  5. Book the review (2 min). A date to discuss how the decision went and grow their judgement. Say plainly that it’s to coach, not to take the decision back - then hold to that.

Output / Takeaways

You leave with:

  • The ladder - every decision you hold, and where it sits
  • Two or three decisions transferred, each with a named owner
  • Guardrails and a review date for each

Important rules

  • Hand down real decisions - a trivial one teaches nothing
  • Name a person, never “the team”
  • Guardrails, not a hidden veto - if you can still overrule inside the agreed limits, you delegated the work, not the decision
  • The review coaches, it never reclaims

Planning to facilitate this activity? Access the resources below to get started.

MIndn
Execution must be smooth. Not chaotic or stressful.
Built by Witmer.