Management judgment
You hired capable people. You gave them titles, responsibility, and room to lead. Yet the meaningful decisions still come back to you.
The pattern is easy to label as hesitation or weak ownership. Usually, it deserves a more careful diagnosis.
The recurring pattern
A manager can have formal authority and still operate in a system that teaches them to wait.
The founder may say, “You own this,” while continuing to hold the customer context, financial assumptions, strategic tradeoffs, and final standard for what good looks like. The manager technically has the decision. The conditions required to make it well remain somewhere else.
This is one reason founder dependency survives delegation. Tasks move outward while judgment, information, and risk stay concentrated at the top.
Repeated escalation is not only a confidence problem. It is evidence about how authority, context, and consequences are actually distributed.
Why capable managers still escalate
The manager is accountable for the result, but the founder continues to approve the choices that produce it. Responsibility has moved. Control has not.
“Use your judgment” sounds empowering until the manager must guess which risks, costs, exceptions, or commitments remain outside their authority.
Managers receive the immediate question without the history, relationships, assumptions, and strategic priorities needed to resolve the tradeoff.
If an imperfect decision is corrected publicly while escalation is rarely penalized, the rational choice is to ask first.
The founder supplies the answer without examining how the manager framed the problem. The issue gets resolved, but the manager is no better prepared for the next one.
A manager may have acted within their role and then watched the decision get reopened. Formal permission means little when experience says the founder may still take the decision back.
Appropriate escalation
Strong judgment includes knowing when a decision exceeds the manager's authority, information, or ability to contain the consequences.
The goal is not to eliminate escalation. It is to make escalation deliberate rather than automatic.
A better diagnosis
When a decision comes back to you, pause before answering it. Use the moment to identify what is missing.
These questions separate a capability gap from an authority gap, an information gap, or a pattern the founder is unintentionally reinforcing.
Make authority usable
A useful decision envelope defines more than a list of approvals. It connects authority to the outcome the manager is expected to carry.
Name the business result the manager owns, not merely the tasks they perform.
Identify the recurring choices the manager can make without prior approval.
Define financial limits, policies, commitments, principles, and risks that bound the decision.
Ensure the manager can access the facts, assumptions, and context required to exercise judgment.
State what must come upward and what should remain with the manager even when the choice is difficult.
Decide when results and reasoning will be reviewed without turning every decision into a preapproval.
This is part of building operating clarity. Decision rights become useful when people can apply them in the actual flow of work.
Develop the reasoning
The fastest response is often to provide the answer. The more useful response is to make the manager's thinking visible.
If the decision sits inside the manager's envelope, keep it there. Ask the questions, surface the assumptions, and let the manager make the call.
A necessary discipline
Founders often have deeper context and faster pattern recognition. That does not mean every choice must match the one the founder would have made.
Evaluate whether the manager used the available information, stayed inside the agreed boundaries, considered the relevant tradeoffs, and learned from the result. A sound decision can produce a disappointing outcome. A weak decision can occasionally produce a good one.
If only founder-like decisions are accepted, managers learn to imitate the founder or wait for approval. Neither response builds organizational judgment.
A practical starting point
Select three recurring decisions that should no longer require the founder's routine involvement.
Name the outcome, decision owner, constraints, required context, and legitimate escalation conditions.
Let the manager make the decision while showing the reasoning behind it.
Examine the quality of the reasoning and the result after the decision, not before every decision.
Widen the envelope as judgment and trust become more reliable.
The founder's role
Distributing decisions does not require the founder to withdraw from the business. It requires a different contribution.
The founder clarifies direction, supplies context, defines risk, develops leaders, and reviews the system. The manager carries the decisions inside that system.
When the company needs one executive to integrate decisions across several functions, the issue may be broader than manager development. In that case, examine whether the business needs a COO or a different operating intervention.
When outside perspective helps
Repeated escalation can look like a collection of isolated personnel problems. Often, the decisions reveal a shared constraint in authority, context, management rhythm, or founder behavior.
Akhada helps founders and executives map where decisions are getting stuck, determine why they keep moving upward, and redesign the conditions under which capable managers can carry them.
Explore Akhada's leadership and management advisory.
Frequently asked questions
Managers should have room to make decisions whose downside is understood and containable. The decision envelope should narrow where the financial, legal, ethical, or reputational exposure is material. Development does not require unmanaged risk.
First confirm that the outcome, authority, information, and standards are clear. Then review the manager's reasoning across several decisions. A repeated inability to frame problems, weigh tradeoffs, or learn from results may indicate a development or role-fit issue.
No. Written rights create clarity, but behavior makes them real. Managers must have access to context, experience the founder honoring the boundary, and receive useful review after they act.
There is no fixed timetable. Development accelerates when managers repeatedly make real decisions, explain their reasoning, receive timely feedback, and carry consequences within a well-defined range.
No. It replaces constant approval with clearer boundaries, visibility, and accountability. The founder retains the decisions that genuinely require founder judgment while the organization becomes more capable of carrying the rest.
A practical next step
Let’s talk through where those decisions are getting stuck, why your managers continue bringing them upward, and what would need to change for the right people to carry them confidently.
