The Three Decisions You Don’t Delegate

There’s a point in a growing company when capable people are carrying the work, and too much still waits on the founder. It looks like a delegation problem. The work has been handed off. The decisions haven’t.

A price needs approval. A draft needs sign-off. A customer exception needs a yes. Each request is small. Together they create a queue around one person’s attention.

Founders are right to be careful about giving up control. They are responsible for the company, and some decisions should stay theirs. But that caution can quietly turn too many decisions into return trips to the founder.

The team can research, prepare, recommend, and execute. But if every consequential judgment still needs one person’s approval, the company has delegated tasks without delegating decisions. The work moves, then stops. Moves, then stops again.

The team isn’t slow. The team is waiting.

There is a cost to this that rarely gets named. Every time a decision returns to the founder, the team has to rebuild the context and the founder has to re-enter work someone else was already carrying. Why is this customer different? Why does this promise matter? Why does the exception exist? Why does the last answer no longer hold? That repeated reconstruction is what we call a re-explanation tax, and the company pays that tax in repeated explanation, interrupted attention, and delay.

The goal is not for everyone to know everything. It is for the reasoning behind recurring decisions to live somewhere other than one person’s availability.

In a growing company, decisions rarely stay inside the lane where they begin. A sales promise becomes a delivery decision. A positioning choice changes the product roadmap. A vendor choice changes cost, timing, and customer experience. If every connection routes through the founder, the company begins organizing itself around the founder’s availability.

The instinct makes sense. The authority to make a decision feels more dangerous to hand over than the task itself. But a person who can recommend and execute without the authority to make a bounded decision can contribute a great deal and still leave too many consequential judgments with the founder. The company can move only after the founder re-enters the decision.

Holding every decision can feel like control. In practice, it keeps the company dependent on one person’s availability.

Delegating a decision does not mean disappearing from it. It means deciding in advance where another person’s authority begins, what should guide the call, and what condition brings it back to you.

The decisions you keep should not simply be the ones you care about most or have always made. Look for the decisions that define what the company is becoming, what it will refuse, and which commitments materially change its direction, ownership, risk, or identity. Those are more likely to require the founder than the routine calls the founder has grown accustomed to reviewing.

Start by writing down the three decisions you will not delegate. Three is not magic. It is simply small enough to force the distinction, and the list will differ by founder and company.

One founder may retain final decisions on senior leadership appointments. Another may retain which customer categories the company will refuse. A third may retain commitments that materially change ownership, risk, or the company’s direction.

The point is not to copy the examples. It is to make your list finite and let it reflect the company’s stage, governance, and the decisions your role or accountability still require you to make.

The list is only half the exercise. For every recurring decision outside it, define:

• The owner: who makes the call.
• The boundary: the information, standard, promise, budget, or limit the decision must stay inside.
• The escalation trigger: what condition brings the decision back to you.

Telling someone to “own it” is not delegation if they still need permission to make the call. They need the authority, context, and boundaries to decide responsibly.

Without those definitions, the team either guesses about its authority or returns every judgment to the founder. One creates uncertainty. The other recreates the bottleneck.

Then test the decisions you are tempted to keep. Does pricing require your final approval, or can someone decide within an agreed range? Which hires require your direct involvement, and which can be made by a leader working from an agreed standard? Does every launch date need your permission, or only one that crosses a budget, customer, or risk threshold?

The useful question is not “Can I delegate this?” It is “What would another person need in order to decide this responsibly without me?”

Three is a forcing exercise, not a substitute for governance. Decisions governed by law, fiduciary duty, safety, regulation, board authority, or other formal obligations still follow the review they require. The exercise is meant to expose what you hold from habit, not override what your role requires.

Write the three. Then give each recurring decision outside them an owner, a boundary, and an escalation trigger. Do it before the next decision returns to your inbox.