Organization Design

Delegation and the Levels of Authority

Stop treating delegation as a personality trait and start treating it as an explicit setting: a named level of authority attached to a named class of decision, chosen from the cost of being wrong rather than from how much you happen to trust someone.

  • Intermediate
  • 15 min total
  • 13 chapters

What decision this helps you make: Which decisions leave your desk this quarter, at which level of authority, with what boundary and what checkpoint, and how you will know within four weeks whether the level was set too high or too low.

What this topic is

Delegation is handing someone responsibility for an outcome together with a stated level of authority: how far they may go on their own before they have to come back to you. The second half is the part that gets left out. Most of what managers call a delegation problem is not a problem of trust or capability at all. It is two people holding different, unspoken assumptions about which of them is allowed to decide.

Why it matters

Every decision that still needs you is a queue with one server, and the queue is you. It caps how fast the business can move, it fills your week with work nobody needed you for, and it quietly guarantees that nobody below you ever learns to make the call. The organisations that outgrow their founders are the ones that made the level of authority an explicit, written, boring setting rather than a matter of nerve.

Who should learn it

Any manager whose calendar is full of approvals; founders who have hired good people and are still the last stop on everything; and second-line managers deciding how much room their own managers get.

What you will understand

  • The six levels of authority, and how to name one out loud so both parties are holding the same one
  • How to pick the level from the cost of the error and its reversibility, not from how much you trust the person
  • The arithmetic of a handover: what it costs, when it pays back, and how to tell a bad delegation from a slow one
  • Why taking a decision back is more damaging than never having delegated it, and how to escalate without doing that

Prerequisites

Common misconception

"Delegation means letting go." That framing makes it a test of character, which is why it is usually done badly and in one jump, from deciding everything to deciding nothing, followed by an expensive surprise and a retreat back to deciding everything. Delegation is not binary and it is not about letting go. It is choosing a point on a scale that runs from "do exactly this" to "handle it and I will hear about it at the quarterly review", and the right point is a function of what a bad outcome costs and how easily it can be undone. The second misconception is that authority is what you hand over. What you hand over is the outcome; authority is only the size of the room you gave them to reach it in.