How to delegate decisions without losing control

You are the operating system

Most founders delegate tasks long before they delegate decisions. The result is a team that can execute anything and decide nothing — which feels like delegation but performs like a queue with your name on it.

The test is simple: could you go offline for two weeks without things slipping? If the honest answer is no, the constraint isn’t your team’s capability. It’s that nobody knows what they’re allowed to decide.

Write the decision rights down

Decision rights are boring and transformative. For each recurring decision, write who decides, within what limits, and who simply needs to know. Publish it. Four categories cover most of it:

• Spend thresholds. What can be approved without you, up to what value.
• Client concessions. What discount, extension or goodwill gesture is pre-authorised.
• Hiring steps. Which stages proceed without your sign-off.
• Publishing and commitments. What goes out — to clients, to market — without review.

Delegation is not abdication

The fear underneath most founder bottlenecks is that standards will slip. Reasonable — so build the guardrail rather than staying in the loop. Set the decision right, define the review point, and inspect outcomes rather than approving inputs.

A monthly review of decisions made is far cheaper than a daily queue of decisions pending, and it teaches judgement instead of dependence.

Test it deliberately

Pick a fortnight. Go genuinely offline. What breaks tells you exactly which decision rights are missing — far more honestly than any planning session. Most leaders find two or three gaps, fix them, and never queue that decision again.