McKinsey research shows that 78% of companies with proven products fail to scale. Not companies with bad ideas or weak technology — companies that found something that works and then could not grow it.
This is the Product Leadership Chasm. Borrowing from Geoffrey Moore's Crossing the Chasm — the gap between early adopters and the mainstream market — this is the organisational equivalent. The strategies, working methods, and decision-making structures that brought you product-market fit will not be sufficient to take you from 20 people to 200. Getting across requires a fundamentally different approach to how product decisions get made.
The uncomfortable truth is that the chasm is not a failure of execution. It is a structural inevitability. Every company that succeeds at the early stage will face it. The question is whether you recognise it in time and respond correctly.
How the Chasm Opens
In the early days, the CEO guides the product directly. You are in every conversation with customers. You make the prioritisation calls. You review the designs. You know what the development team is building and why. This works brilliantly at 10 or 15 people because the founder's accumulated context — their deep understanding of the customer, the market, and the technology — is the competitive advantage.
Then the company expands. More customers. More features to maintain. More teams to coordinate. The CEO simply runs out of time. Product decisions start getting delayed. Teams wait for sign-off that doesn't come. The bottleneck becomes visible to everyone.
So the company does what seems logical: it hires product people and tells them to take ownership. But without the founder's context, these new product managers start doing the only thing they can — they go around the organisation gathering requirements. Sales wants this. Marketing needs that. Operations is asking for something else. The product team collects these requests and "prioritises" them.
This is how the feature factory is born. Not through incompetence, but through a structural information gap. The product team is responding rationally to the incentives in front of them. They just don't have what they need to make strategic product decisions.
The Symptoms
The chasm doesn't announce itself with a single dramatic failure. It shows up as a pattern of escalating frustrations:
- Features take forever. What used to ship in weeks now takes months. Teams are busy, but the output doesn't match the effort.
- Innovation has slowed. The product was once the company's differentiator. Now it feels like the team is playing catch-up with competitors.
- Outages increase. As the codebase grows and technical debt compounds, stability problems start affecting customers.
- Tech debt compounds. Quick fixes from the early days become structural problems. Every new feature is harder to build than the last.
If you are experiencing three or more of these symptoms simultaneously, you are likely in the chasm.
Three Converging Problems
The Product Leadership Chasm is not a single issue. It is three problems converging at the same time, and they reinforce each other.
1. The Founder Bottleneck
At 10 people, having a single decision-maker was an asset. Every product call was fast, consistent, and informed by deep customer understanding. At 50 people, that same dynamic becomes a liability. The organisation produces work that will get past the CEO rather than work that solves customer problems. Teams learn to wait for direction instead of exercising judgement. The founder becomes the constraint on the company's own growth.
2. The Empowerment Paradox
The standard advice is to delegate. Empower the team. Trust your hires. But delegation without guardrails fails predictably. Teams lack the accumulated context the founder has built over years of direct customer exposure. Without that context, empowered teams produce three types of failure: local optimisation (each team optimises for their own metric at the expense of the whole), low-impact features (work that is easy to build but doesn't move the needle), and wasted resources (multiple teams unknowingly working on overlapping problems).
3. The Information Gap
What feels obvious to the founder is the product of years of direct customer exposure. The reasoning behind product decisions, the trade-offs that were considered and rejected, the market dynamics that shaped the strategy — none of this is written down. The team hasn't had that experience. This is a structural information problem, not a talent gap. You could hire the most experienced product leaders in the world and they would still struggle if the context transfer doesn't happen.
Why Product Transformations Fail
Many companies recognise the chasm and attempt to cross it. Most fail. Here are the four most common reasons:
1. Progress is perceived as too slow
A genuine product transformation takes 18–24 months. Boards and leadership teams accustomed to quarterly results lose patience. They pull the plug after six months, just when the early changes are beginning to take hold. The irony is that the transformation was working — it just wasn't visible yet.
2. Stakeholder pushback
Product transformation changes how decisions get made. People who previously had direct influence over the roadmap — sales leaders, marketing heads, individual executives — find themselves going through a new process. Some will resist, and if senior leadership doesn't visibly back the new approach, the transformation stalls.
3. Leading strategy while building the team
The incoming product leader is expected to simultaneously define and execute the product strategy while hiring, onboarding, and coaching a team that doesn't exist yet. These are two full-time jobs. Without support, the leader either burns out or defaults to the path of least resistance — which usually means becoming a project manager for stakeholder requests.
4. The distressed tech stack
Years of feature-factory output have left the codebase in a fragile state. Even if the product team makes better decisions, the engineering team cannot execute them quickly because every change is risky and slow. The best product strategy in the world means nothing if the tech stack can't deliver it.
Case Study
When Companial, the world's largest Microsoft Dynamics distributor, found themselves without product management capability, they started with assessment — not restructuring.
A thorough assessment of the current state, stakeholder interviews, and capability gap analysis provided the foundation for a target operating model that the entire leadership team could support. The result was a clear roadmap from where they were to where they needed to be.
Read the full case studyThe Competitive Pressure
The chasm doesn't just create internal dysfunction. It creates competitive vulnerability. Borrowing from Geoffrey Moore's Inside the Tornado framework, companies in the early majority phase face a narrow window where market position is won or lost. If your product organisation is paralysed by the chasm while competitors are executing, you don't just fall behind — you lose the window entirely.
This is what makes the chasm so dangerous. It hits precisely when the competitive stakes are highest. You've proven the product works. The market is ready to scale. But the internal machinery — the decision-making, the team structure, the way product strategy gets set and executed — hasn't kept pace with the external opportunity.
Pivot Residue
There's a hidden factor that makes the chasm wider for certain companies: pivot residue. Every pivot your company went through left behind layers of abandoned architecture, orphaned features, and institutional confusion about what the product actually is. The team that survived the pivots carries mental models from previous iterations. The codebase carries technical debt from abandoned directions. The customers carry expectations set by earlier versions of the product.
Pivot residue explains why two companies at the same revenue stage can face very different versions of the chasm. A company that found product-market fit on the first attempt has a cleaner foundation. A company that pivoted three times is carrying the accumulated weight of all three previous directions — in its code, its culture, and its customer base.
Why This Matters Now
The chasm has always existed, but three forces are making it wider and more dangerous in 2026:
- AI is accelerating the pace of competition. Companies that cross the chasm can now ship 40% faster with AI-augmented teams. Companies stuck in the chasm fall further behind with every quarter.
- Team structures are being disrupted. The traditional product trio (PM, Designer, Engineer) is converging into hybrid roles. Companies in the chasm can't adapt because they haven't solved the basic organisational problems yet.
- Product transformations take 18–24 months. That means the companies that recognise the chasm today and begin crossing it will be two years ahead of those that wait. The cost of delay is not linear — it compounds.
The 78% failure rate McKinsey identified is not destiny. It is the default outcome for companies that don't recognise the structural nature of the problem. The chasm is crossable — but only if you understand what you're dealing with and have a systematic approach to the transition.