The Critical Path Layers framework identifies four cross-cutting dynamics that accelerate or impede corporate innovation at every stage: political capital, clock speed, organisational immune response, and the narrative layer. The first three are constraints. The narrative layer is different — it's the medium through which the other three operate. Political capital is spent and earned through stories about the initiative. Clock speed mismatches become visible when the story stops evolving. The immune response deploys counter-narratives to neutralise change.

What makes the narrative layer structural rather than cosmetic is that it must evolve as the initiative progresses through the CPL's layers. Each layer produces a different story because the initiative's relationship to the organisation has changed.

“The law of floatation was not discovered by contemplating
the sinking of things, but by contemplating the floating of things which floated naturally, and then intelligently asking why they did so.” (Thomas Troward)

TLDR;-) Most innovation frameworks organise by domain. The problem is that domain-based thinking hides the only question that actually matters in early-stage work: what needs to be true before this can work? Critical Path Layers reorders the familiar themes of startup growth and corporate innovation into a dependency sequence. Each layer gates the next. It doesn't tell you what to do. It tells you what to solve first.

Every coaching and advisory framework I've encountered makes the same structural error. Strategy in one column, operations in another, fundraising somewhere else. Neat. Logical. And almost entirely unhelpful for sequencing decisions.

Domain-based organisation tells you what to think about. It says nothing about when. And in early-stage work, when is everything.

Critical Path Layers takes the same familiar themes and reorders them into a dependency sequence. Each layer gates the next. You can work on anything you like at any time, of course. But effort spent on downstream themes before upstream prerequisites are resolved is the single most common pattern of wasted founder and corporate innovator effort. I see it constantly. Strategy before problem clarity. Pricing architecture before product-market fit. Hiring plans before unit economics.

The framework doesn't prescribe. It sequences.

A follow-up to "Corporate Innovation in the Age of AI: Navigating the Hype, the Hypertail, and the Hard Limits"

In my previous piece, I explored how corporate innovation leaders face four key scenarios in the age of AI: the "hypertail" overload of point solutions, the slow burn of transformation, regulatory compliance pressures, and talent bottlenecks.
While these strategic frameworks help navigate the landscape, they miss a more fundamental truth that's becoming increasingly apparent in boardrooms and innovation labs alike.

The real bottleneck isn't AI adoption—it's organisational readiness.

The AI-Native Paradox presents significant challenges for startup founders and corporate innovators in today's rapidly evolving technological landscape. However, I find that Wardley Mapping offers a powerful strategic framework to navigate these challenges by providing situational awareness and enabling more informed decision-making (it is a kind of spatial "Where to play? How to win?" imho).