The first serious buyer of Mariana and Ivan Polić’s aerospace manufacturing company did not question whether the business had procedures.
The company operated in a highly regulated industry. Its processes were documented. Its quality systems were audited regularly.
The buyer still reached a difficult conclusion.
“You know how to run this business, and this price may be good if you keep running it, but we cannot pay this.”
The problem was not that the company could not perform its routine work.
The buyer was not convinced the company could interpret, decide, and lead without its founders.
Mariana and Ivan responded by building leaders, transferring marketplace trust, and reducing their involvement from approximately 80 hours a week to two.
The change improved the company’s transferability.
It also forced the founders to confront a quieter question.
Could the company be capable even if it no longer operated exactly the way they would operate it?
That distinction sits near the center of many founder transitions.
Founders often believe they are protecting capacity when they are actually protecting control.
The Founder Has More Evidence
This problem does not begin with arrogance.
It begins with experience.
The founder has seen more cycles, survived more crises, absorbed more consequences, and made more decisions than almost anyone else in the company.
They know which customer concern is harmless and which one signals a relationship at risk.
They recognize when a promising opportunity will become an expensive distraction.
They can often sense that a decision is wrong before the available information fully explains why.
That judgment is real.
So is the gap between the founder and the developing leader.
The mistake is assuming the gap proves that no one else can become capable.
A successor will not begin with the founder’s accumulated evidence. They must acquire judgment through exposure, decisions, mistakes, consequences, and reflection.
The founder developed capacity by carrying responsibility.
The successor cannot develop comparable capacity while being protected from it.
The Rescue Usually Works
When I asked exited agency founder Carrie Kerpen which founder behaviors make a company more difficult to transfer, she pointed to one belief:
“Thinking that only they can save the day.”
The belief survives because the founder frequently can save the day.
A customer becomes upset.
A team member escalates a difficult decision.
A deadline begins slipping.
The founder enters, recognizes the pattern, and resolves the problem.
The immediate outcome improves.
The company experiences relief.
The founder receives more evidence that intervention was necessary.
But the rescue creates a second outcome that is harder to see.
The leader who escalated does not experience the full decision.
They do not test their recommendation, communicate it under pressure, absorb the response, or learn whether their judgment was sound.
The founder gets another repetition.
The developing leader loses one.
The rescue that protects today’s result can quietly weaken tomorrow’s capacity.
Activity Can Move While Authority Stays Put
A founder may delegate many tasks without transferring meaningful control.
Reports are prepared by someone else.
Meetings are facilitated by someone else.
Projects are managed by someone else.
The founder still reserves the right to reinterpret the information, reverse the recommendation, reassure the customer, or make the final consequential decision.
From the founder’s perspective, the company appears increasingly independent.
From the team’s perspective, the safest strategy may still be to wait.
An anonymized Founder Observatory diagnostic exposed this divide.
Routine operations could continue without the founder. The company could serve clients, complete projects, and manage ordinary activity.
When belief dropped, however, the organization still looked to the founder to restore it.
The company had distributed work.
It had not distributed confidence.
This is why operational independence can be misleading.
A business may function without the founder when conditions are stable and still become founder dependent the moment ambiguity, fear, conflict, or opportunity enters the room.
Capacity is not demonstrated by what happens when the process works.
It is demonstrated by what happens when the process stops being enough.
Control Often Hides Inside Standards
Founders rarely describe themselves as unwilling to release control.
They say they are protecting the customer.
Preserving the culture.
Maintaining quality.
Avoiding an unnecessary mistake.
Those concerns may be legitimate.
The founder may genuinely see risks that the team has not learned to detect.
But a standard can become a hiding place when the founder cannot explain what another person would need to demonstrate before authority is transferred.
If every imperfect decision proves that the leader is not ready, readiness becomes impossible.
The founder’s early decisions were not flawless.
They became useful because the founder stayed close enough to the consequences to learn from them.
A successor who must produce founder-level judgment before receiving founder-level authority is trapped in a locked classroom.
They cannot graduate because they are never allowed to take the test.
The Company Learns Where the Real Authority Lives
Teams do not learn authority from organization charts.
They learn it by watching what happens when decisions become uncomfortable.
- Who does the customer ask for when confidence falls.
- Whose reaction does the room study before committing?
- Which recommendation moves forward without another layer of approval?
- Who can make a mistake without losing the right to make the next decision?
The answers reveal where authority actually lives.
A founder may announce that a leader has full responsibility and then routinely revise that leader’s consequential decisions.
The formal message says, “You own this.”
The behavioral message says, “You own this until I become uncomfortable.”
Teams are exquisitely sensitive to that contradiction.
They quickly learn whether the successor has authority or merely access to it.
The Founder Is Also Losing Something
The difficulty is not confined to the company.
Decision requests provide the founder with more than interruptions.
They provide structure.
Stimulation.
Usefulness.
Evidence of mastery.
Proof that the founder can solve what others cannot.
When those requests decline, the founder may experience the transfer as an erosion of relevance rather than evidence of success.
That is where capacity and control become tangled.
The founder may sincerely want the team to become independent while continuing to need the company to confirm that their judgment matters.
This is one expression of Reciprocal Reliance.
The enterprise relies on the founder for decision agency.
The founder relies on the enterprise for challenge, competence, structure, or significance.
Each escalation reinforces both sides.
The company concludes that the founder remains necessary.
The founder concludes that stepping away would be irresponsible.
Neither conclusion has to be consciously manufactured.
The system generates the evidence.
What Happens When the Founder Stops Answering?
The most useful test of capacity is not asking whether someone is ready.
It is temporarily interrupting access.
What happens when the founder does not attend the meeting?
What happens when a decision arrives and the founder asks the leader for a recommendation rather than supplying an answer?
What happens when the team must explain the reasoning, risk, threshold, and likely consequences behind its choice?
What happens when the leader’s decision is different from the founder’s but still defensible?
A founder who intervenes at the first sign of discomfort never learns whether the organization could have recovered.
The team never learns whether it could either.
A controlled absence produces better evidence than another conversation about empowerment.
But the absence must be designed.
The founder should not disappear from a fragile system and call the resulting damage a leadership lesson.
The team needs clear decision rights, escalation thresholds, available information, and consequences it can safely absorb.
Capacity grows when responsibility expands slightly faster than comfort, not dramatically faster than competence.
Different Does Not Mean Incapable
This may be the hardest lesson for a founder to accept.
A capable leader may not make the same decision.
They may use a different process.
They may communicate with less intensity.
They may tolerate a risk the founder would avoid.
They may reject an opportunity the founder would pursue.
Some of those differences will produce worse outcomes.
Others may produce better ones.
The purpose of authority transfer is not to create a replica of the founder.
It is to create an institution that can interpret reality and act without requiring compulsory access to the founder’s mind.
That means the standard cannot be:
Did they do what I would have done?
The stronger questions are:
- Did they understand the objective?
- Did they identify the material risks?
- Did they use the available information responsibly?
- Did they act within their authority?
- Can they explain their reasoning?
- Did they learn from the result?
A leader can fail the first test and pass all six of the others.
That may be evidence of emerging capacity rather than evidence that control should return to the founder.
Control Can Preserve the Risk It Claims to Prevent
Founder intervention is often defended as temporary.
Just until the new leader gains confidence.
Just until the customer becomes comfortable.
Just until the company gets through this growth period.
Just until the transaction is complete.
The danger is that the intervention prevents the evidence required to end it.
The customer never learns to trust another leader because the founder keeps appearing.
The team never learns to restore confidence because the founder keeps regulating the room.
The successor never becomes legitimate because the founder remains the most credible source of authority.
The founder then points to the absence of trust, confidence, and legitimacy as proof that continued control is necessary.
The risk becomes self-preserving.
What Advisers Should Diagnose
The question is not whether the founder is controlling.
That label is usually too blunt to be useful.
The better questions are:
- What capacity does the founder believe is missing?
- What observable evidence would demonstrate that the capacity exists?
- Has the developing leader been given enough authority and exposure to produce that evidence?
- What consequences can the company safely allow the leader to experience?
- Which interventions protect the enterprise, and which ones protect the founder from discomfort?
- What does the founder receive each time the decision returns to them?
- What would need another home before the founder could allow the transfer to hold?
These questions separate an enterprise problem from an emotional accusation.
Sometimes the founder is right.
The leader may not yet possess the judgment, trust, or resilience the role requires.
That should lead to development, role redesign, or a different successor.
It should not lead to indefinite ambiguity in which responsibility is transferred but authority remains hidden in the founder’s pocket.
From Founder Judgment to Enterprise Judgment
The goal is not to remove the founder’s wisdom.
It is to turn individual judgment into institutional capacity.
That requires more than procedure.
The founder must expose the reasoning beneath decisions.
What information matters most?
Which risks are tolerable?
What thresholds require escalation?
What principles govern exceptions?
How does the founder distinguish a temporary problem from a strategic threat?
The developing leader must then be allowed to use that reasoning without being required to imitate the founder.
Over time, authority becomes credible when other people repeatedly see the leader interpret uncertainty, make decisions, absorb consequences, and remain accountable.
The founder’s contribution can still matter.
It simply stops being the only place where judgment lives.
A company is not independent because the founder has fewer tasks.
It is independent when the organization can think, decide, recover, and move without waiting for the founder to make uncertainty disappear.
Control preserves the founder’s answer. Capacity creates another credible source of answers.
