The team is capable and the business is growing, yet routine estimates, scheduling changes, and customer problems still return to the founder. As decisions wait and interruptions multiply, the founder’s strategic work is displaced by operational coordination.
For business owners and leadership teams, this is a signal to examine how decisions get made. A company can add people and management roles while still relying too much on one person to connect the work.
The warning sign is not simply a busy founder. It is the same kinds of decisions returning to the founder because the organization cannot resolve them consistently.
How involvement becomes dependency
In a smaller business, direct founder involvement has real advantages. Customers get quick answers, employees learn through close contact, and problems reach someone who understands the whole operation.
Growth makes that arrangement harder to sustain. More jobs compete for resources, decisions affect teams that do not share the same information, and customer commitments become harder to coordinate informally.
The founder often keeps things moving by filling the gaps. A project manager gets an answer, a customer gets reassurance, and a scheduling conflict gets resolved. The immediate problem disappears, but the reason it needed founder intervention remains.
Repeated rescues can create a self-reinforcing loop. Employees learn that escalation is the safest route, and the founder sees each escalation as further evidence that personal involvement is necessary. Capable people then wait for decisions they could make if expectations and authority were clearer.
Find what the repeated escalation is telling you
Not every decision that reaches the founder represents a problem. Major commitments, unusual risks, and decisions about ownership may properly require that involvement. The concern is routine work that repeatedly needs the same person’s judgment or approval.
Look for recurring decisions that wait despite having a responsible manager, customer commitments that only the founder can interpret, or meetings that revisit the same issue until the founder settles it. When the same category of decision repeatedly causes delay, changes hands, or cannot be explained without the founder, the problem is usually missing authority, information, or working standards rather than a one-off exception.
A useful test is whether the decision depends on ownership judgment or operating judgment. Decisions involving ownership rights or reserved approvals should remain with the appropriate owners or governing body. Recurring operating decisions should sit with the person closest to the work who has the information, capability, and authority to make them reliably.
Make judgment available to the team
Consider a marine services company whose founder still approves changes to repair schedules. Project managers understand their individual jobs, but only the founder knows which customer commitments take priority, when overtime is acceptable, and which specialist must be protected for urgent work.
Telling managers to “take more ownership” does little to resolve that gap. They remain accountable for outcomes without a shared basis for making the tradeoffs. Asking the founder is a rational response.
The useful work is to make those tradeoffs explicit. The team could agree on customer priority rules, a spending limit for schedule recovery, and the circumstances that require escalation. A named manager can then make routine changes within those boundaries and bring exceptions forward with a recommendation.
This turns experience that once lived in the founder’s head into guidance others can use. It also exposes disagreements about priorities that repeated intervention may have concealed.
Michael Gerber explores a business’s dependence on its founder in The E-Myth Revisited. His distinction between working in the business and working on it clarifies the choice at the center of this article: resolving today’s scheduling conflict keeps work moving, while building rules the team can use to resolve future conflicts reduces dependency on the founder.
Delegation needs a consistent response from leadership
Founders may hesitate to step back because their involvement protects quality, customer trust, and standards built over many years. Those concerns deserve a practical response. Agree on what a good decision must protect, give the responsible person access to the relevant information, and identify where coaching or experience is still needed.
Leadership teams also have a role in changing the pattern. Bring recommendations with escalations, make decisions within agreed limits, and surface conflicting instructions early. Where an individual lacks the capability for a decision, address that through support, training, or a change in responsibility.
The founder’s response matters just as much. If a decision made within agreed boundaries is routinely reopened or reversed without explanation, people will return to seeking approval. Review the reasoning and outcome, then clarify the rule if necessary. A different preference does not automatically mean the decision was wrong.
Some decisions will continue to require founder judgment. The aim is to reserve that attention for matters where it adds the most value, while building the team’s ability to handle ordinary work reliably.
Start by transferring one recurring decision
For one working week, record the operational decisions brought to the founder. Include what was being decided, who raised it, why it was escalated, whether work waited for an answer, what decision was made, and which principle or tradeoff shaped it. Use the record to understand the pattern together, without turning it into a scorecard against individuals.
Choose one recurring decision that creates meaningful delay or interruption and could reasonably sit with a manager. Avoid beginning with an unusually risky or irreversible commitment.
Define the decision. Describe exactly what the manager can decide. “Manage scheduling” is broad; “reschedule routine jobs within agreed customer commitments” gives both parties something concrete to discuss.
Set the boundaries. Agree on the outcomes to protect, the information required, and the financial or operational limits. Specify which exceptions still require approval and who provides it.
Transfer authority visibly. Name the person responsible and tell everyone affected where the decision now sits. If employees continue going directly to the founder, route the decision back through the agreed process.
Review and adjust. Trial the arrangement for two weeks, then examine a few actual decisions against three questions: Did work move faster? Were customer, cost, and quality outcomes protected? Could the manager decide without reconstructing the founder’s preferences? Use the findings to refine the boundaries and identify coaching needs.
If approvals have fallen but rework or customer problems have risen, investigate what information, capability, or guidance is still missing before expanding the arrangement.
Once the decision is working reliably, apply what the team has learned to the next recurring escalation. Progress comes from making specific decisions work at the right level, then sustaining that authority in everyday practice.
Founder experience remains valuable as the business grows, but its value is limited when every decision requires the founder’s presence. The business gains leverage when the team can apply the judgment behind that experience without waiting for intervention.
Which recurring decision will you move away from the founder first, and what boundary must be clear before someone else can make it well?