Decisions you should delegate, and ones you never should

Most leaders get delegation exactly backwards. They cling to small decisions out of habit and instinct, then hand off the big, hard ones at the moment those decisions most need their judgment. The result is a leader who is exhausted by trivia and a team that feels both micromanaged and unsupported. Sorting which decisions are yours and which are not is one of the most freeing things you can learn to do.

Two questions sort almost everything

Before you decide whether to own a decision or pass it on, ask two things. First: how reversible is it? Second: how much does it depend on something only you can see?

A reversible decision is one you can undo cheaply if it goes wrong. A new meeting format, a tool to try for a month, the wording of an announcement. These should almost always be delegated, because the cost of a wrong call is small and the cost of being a bottleneck is large. The second question catches the exceptions: a decision that genuinely requires context only you hold, like a board conversation or a sensitive personnel matter, stays with you even when it looks small.

Run most decisions through those two filters and the answer becomes obvious far more often than you would expect.

Delegate the reversible, the frequent, and the growth-making

The clearest candidates to hand off share a few traits:

• They are reversible, so a wrong call teaches a cheap lesson instead of causing real damage.
• They happen often, so owning them all makes you a permanent bottleneck.
• They would stretch the person making them, turning a decision into a development opportunity.

That last one matters more than people realize. Every decision you make for someone is a decision they did not learn to make. If you want a team that can operate without you, you have to let them decide things, including things they might get wrong. A reversible mistake made by someone on your team is often a better investment than a correct call you made for them.

Never delegate these

Some decisions are yours, full stop, and trying to delegate them is its own failure of leadership:

• Decisions that set the standard. What behavior gets tolerated, what quality bar holds, who gets promoted. The team reads these as signals of what you actually value, and they have to come from you.
• Decisions that are hard precisely because they are yours to make. Letting go of a struggling person, killing a project someone loves, saying no to a powerful stakeholder. Delegating these is usually just conflict avoidance wearing a nice word.
• Decisions where being wrong is expensive and irreversible. Bet-the-team calls, public commitments, anything you cannot walk back. These need your judgment, and the room needs to see you make them.

Delegating a hard, irreversible decision is not empowerment. It is handing someone the consequences of a call you were too uncomfortable to make.

Delegate the decision, not just the task

The most common half-measure is delegating the work while keeping the decision. You ask someone to research options, then make the call yourself. Sometimes that is right. But if you do it by default, you train people to bring you choices instead of making them, and you stay the bottleneck you were trying to escape.

When you do hand over a decision, hand over the whole thing. Be clear about the boundaries and what would require a check-in, then let them own the outcome. People grow into the authority you actually give them, and shrink from the authority you only pretend to.

Get this sorted and two things happen at once. Your calendar clears of decisions that were never really yours, and your judgment is finally free for the ones that always were.