← Essays Essay · Founder Transition

When the Founder Becomes the Problem

By Stan Tscherenkow · Published September 2025 · 12 min read

Quick Answers

How does a founder become the problem? The transition from asset to liability is structural, not a failure of character or intent. Every company is built on the founder's operating mode: the speed, the judgment calls, the willingness to hold contradictory things simultaneously. In the early stages this is the company's primary competitive advantage. At some point, typically between $8M and $25M in revenue, the company's size requires a different operating mode than the one that built it. The founder's involvement in daily decisions, which was functional at $3M, becomes a bottleneck at $15M. The transition is not a single event. It is a gradual accumulation of decisions that made sense individually and produced a structural problem collectively.

What are the early signals the founder has become the constraint? The problem manifests in organizational behavior before it appears in P&L data. Decisions route to the founder that should not, because the organization has learned that founder involvement changes outcomes. Senior leaders stop initiating because acting and having the founder modify or reverse the action is costlier than waiting for direction. The founder becomes a bottleneck in meeting cadence, the organization's pace becomes a function of founder availability. High-capability hires do not stay, because the operating structure does not allow the talent to actually operate. By the time the financials make it legible, the organization has been absorbing the cost for twelve to thirty-six months.

Why are capable founders the hardest cases? The most straightforward cases, founders who become the problem through incompetence or dysfunction, are the easiest to address. The problem is visible. The hardest cases are the capable founders. The ones who are genuinely good at what they do, who are right more often than the people around them, and who have built something substantial on the strength of that capability. An organization that routes decisions to the founder because the founder is right 80% of the time never develops the capacity to make decisions itself. The 80% becomes the ceiling of the organization's performance, determined by the founder's bandwidth, not by the organization's potential.

What does resolution actually require? Resolution is not about reducing the founder's involvement as a general matter. It is about changing the nature of the involvement, from operational to structural, from decision-making to decision-enabling. Three specific changes: explicit authority transfer, documented and deliberate, not assumed or gradual. Tolerance for worse decisions in the short term, because the organization will make worse decisions than the founder would have made. And a redefined founder role with its own domain (typically strategic direction, capital decisions, key external relationships) that does not overlap with the domains being transferred. Most founders who navigate this successfully did not do it voluntarily. They did it because a trusted external source named it plainly.

The instincts that build a company to $5M are structural liabilities at $20M. This is not a character flaw. It is a predictable consequence of a founder whose operating mode has not changed at the rate the business has.

How the transition from asset to liability happens

Every company is built on the founder's operating mode. The speed, the judgment calls, the willingness to hold contradictory things simultaneously while the organization finds its footing. In the early stages, this is not a risk. It is the company's primary competitive advantage.

At some point, typically between $8M and $25M in revenue, though the threshold varies by industry and structure, the company's size requires a different operating mode than the one that built it. The founder's involvement in daily decisions, which was functional at $3M, becomes a bottleneck at $15M. The founder's instinct to hold authority closely, which protected the company when it was fragile, begins to prevent the organization from developing the leadership capacity it needs to scale.

The transition from asset to liability is not a single event. It is a gradual accumulation of decisions that made sense individually and produced a structural problem collectively. The founder who built the business through direct involvement finds it difficult to stop doing the things that worked. They remain in the operational detail not because they distrust their team. Often they do trust them. But involvement is the behavior that produced success, and changing a successful behavior requires overriding a strong feedback loop.

What it looks like before it becomes visible

The problem manifests in organizational behavior before it appears in P&L data. The P&L shows it eventually, in growth rate deceleration, in senior talent attrition, in margin pressure from operational inefficiency. But by the time the financials make it legible, the organization has been absorbing the cost for twelve to thirty-six months.

Four early organizational signals

Decisions route to the founder that should not. Not because the founder insists on it. Because the organization has learned that the founder's involvement changes outcomes, so they seek it. The routing becomes habitual on both sides.
Senior leaders stop initiating. In an organization where the founder's involvement is pervasive, senior leaders learn to wait rather than act. Acting and having the founder modify or reverse the action is costlier than waiting for direction. The organization becomes passive at the leadership level.
The founder becomes a bottleneck in meeting cadence. Decisions that require the founder's presence stall when the founder is unavailable. Projects wait. The organization's pace becomes a function of founder availability rather than organizational capacity.
High-capability hires do not stay. The talent that a $15M or $20M company needs to scale requires genuine authority to do their work. Founders who have difficulty transferring authority do not retain this talent. Not because the culture is bad, but because the operating structure does not allow the talent to actually operate.

For founders willing to look, the organizational signals are readable before the financial consequences arrive. Diagnostic questions that reveal the transition: How many significant decisions were made in the last ninety days without your direct involvement? If you struggle to name more than two or three in a $15M+ business, the organization is not operating independently. When you are unavailable for a week, traveling, ill, genuinely offline, does the pace of the business change? It will change somewhat in any healthy organization. If it changes materially, the dependency is structural. How often in the last six months have you modified or reversed a decision made by a senior leader? Each reversal is a data point. More than one or two per quarter in a domain you have nominally delegated is a signal. How many senior leaders have left in the last two years, and what is the gap between the reason they gave and the reason you believe? The gap is frequently the location of the problem.

Why capable founders are the hardest cases

The most straightforward cases, the founders who become the problem through incompetence or dysfunction, are actually the easiest to address. The problem is visible. The board sees it. The team sees it. The founder often sees it.

The hardest cases are the capable founders. The ones who are genuinely good at what they do, who are right more often than the people around them, and who have built something substantial on the strength of that capability. These founders have the hardest time recognizing the transition because their competence is the evidence against it.

The founder who is right 80% of the time will destroy the organization's decision-making capacity at scale. Even though they are right 80% of the time.

Why? Because an organization that routes decisions to the founder because the founder is right 80% of the time never develops the capacity to make decisions itself. The 80% becomes the ceiling of the organization's performance. Determined by the founder's bandwidth, not by the organization's potential. And as the company scales, the founder's bandwidth becomes a progressively smaller fraction of the decision-making the organization requires. The 80% accuracy starts constraining more and more of the business. The capable founder becomes the bottleneck precisely because of the capability that made them valuable. The documented case of this pattern lives in the founder who couldn't let go.

What resolution actually requires

Resolution is not about reducing the founder's involvement as a general matter. It is about changing the nature of the involvement. From operational to structural, from decision-making to decision-enabling, from the person who makes the call to the person who ensures the organization has what it needs to make the call itself. The related argument on why this matters structurally sits in why your company only works when you are in the room.

Three changes that are easy to describe and difficult to execute

Explicit authority transfer. Not assumed, not gradual. Documented and deliberate. The founder identifies the specific decisions they are transferring, assigns them to specific roles, and holds the line when the organization tests whether the transfer is real. The testing is inevitable. The founder's behavior during the test determines whether the transfer sticks.
Tolerance for worse decisions in the short term. The organization will make worse decisions than the founder would have made. This is unavoidable in the short term. Founders who cannot tolerate this, who re-insert themselves every time they see a decision they would have made differently, are not actually transferring authority. They are conducting a continuous performance review with real consequences.
A redefined founder role. The founder needs a new operating model with its own domain. Typically strategic direction, capital decisions, key external relationships. That is genuinely the founder's and that does not overlap with the domains being transferred. Without a clear positive role, the founder will fill the vacuum with what they know how to do: operational involvement.

Most founders who successfully navigate this transition did not do it because they recognized the problem themselves and self-corrected. They did it because someone they trusted named it plainly. A board member, an advisor, a co-founder who stayed long enough to say the thing that needed to be said.

The internal naming of this problem is structurally difficult. The people closest to the founder, the senior team, the direct reports, carry real professional risk in raising it. They have watched what happens to people who challenge the founder. Even in organizations with genuinely good cultures, the feedback loop that would surface this problem is compromised by the founder's authority over the people giving the feedback.

This is not a moral failure. It is a structural one. It is why this essay exists. Not to flatter founders with a problem well-named, but to give the naming itself enough clarity that a founder reading it can do the uncomfortable work of applying it to themselves.

The question is not whether this applies to you. At a certain scale, it applies to every founder. The question is whether it has reached the threshold where addressing it is more valuable than the cost of addressing it. In most cases I have seen, founders who address it earlier than they had to, before the financial signals arrived, before the senior talent left, came out materially better than those who waited for the evidence to become undeniable. The operational companion to this essay is how do you transition from founder to CEO.

Stan Tscherenkow Private Business Advisor Two decades operating across Europe, Russia, Asia, and the United States.

About Stan →