Which Decisions Still Need You?

If a team repeatedly asks its leader to decide, “be more autonomous” is an incomplete response. The next question is what makes approval feel necessary. A person may lack information, authority, confidence, access, or protection from a decision being reversed later. These are different problems.

Consider keeping a decision diary for a week. Record the requests that reach you, what the person already knew, and why your involvement was needed. Do not turn it into a count of who interrupts most. Use it to inspect the arrangement around the work.

Some decisions properly belong with a leader. A trade-off between two initiatives may require context across both. A change to a public commitment may exceed the team’s authority. A serious unresolved risk may need someone who can accept its consequences.

Other requests expose a missing piece of the operating model. A team asks which defect to fix because the current priority is unclear. An engineer asks to pause a rollout because stopping conditions were never agreed. A designer asks to contact customers because nobody has explained the access rules.

Answering each request quickly can keep today’s work moving. It can also preserve the reason tomorrow’s request will arrive. After the immediate decision, ask what would let a capable colleague decide the next comparable case.

Sometimes the answer is one sentence. “During the pilot, correctness of submitted orders takes precedence over expanding coverage.” Sometimes it is a boundary: “You may stop the rollout whenever reconciliation fails; tell operations immediately.” Sometimes the person needs to observe your reasoning before taking over.

Show the reasoning, including uncertainty

When a decision does need your involvement, explain the factors that matter. Name what you believe, what you do not know, and which consequence makes the choice difficult. A decision without its reasoning gives the team an answer they may copy into the wrong situation.

For example, suppose you limit an experiment to one customer group. Explain whether the limit comes from support capacity, incomplete evidence, a contractual boundary, or the cost of recovery. Each reason suggests a different condition for expanding it.

Invite the person closest to the work to recommend a decision before you speak. This should be a supported exercise in judgment, not a ritual where they guess your preferred answer. If you disagree, make the disagreement useful by naming the evidence or consequence you weigh differently.

Make room for decisions you would not make

Delegation becomes fragile if every acceptable choice must match the leader’s preference. There may be several responsible approaches within the agreed constraints. Your colleague can choose one you would not have selected and still exercise sound judgment.

Decide in advance which differences justify intervention. A breach of an access boundary matters. An implementation preference may not. If you intervene, explain which boundary changed or was crossed. Repeated unexplained intervention teaches people that asking first is the safest use of their time.

This does not mean leaving someone alone with a difficult decision. Offer a way to consult without transferring ownership back to you. “Talk me through your recommendation” supports a different relationship from “send it to me for approval.” Be explicit about which conversation you are having.

Rehearse an ordinary absence

Before your next period away, choose a recurring decision the team usually brings to you. Agree on its purpose, constraints, evidence, decision-maker, and escalation route. Work through one plausible exception together. Let the responsible person handle the next instance while you are still available to observe and support.

Afterward, review what was missing. Perhaps a dependency owner was unreachable. Perhaps the criteria were clear but contradictory. Perhaps the person made a reasonable decision and only needed confirmation that you would stand behind it.

The useful result is a specific decision the team can now make responsibly. Keep the diary until you can see which requests genuinely require your role and which ones you can help remove from the queue.