The most frequently identified stack across 75+ diagnostics. It appears in mature ecosystems and emerging ones, in ecosystems with strong university anchors and in those with corporate anchors. Geography, sector, and maturity level do not predict its presence. Something else does.
Understanding why this stack is so prevalent requires tracing the mechanism, not just naming the pattern. Two stalls. Each rational on its own. Together, they form a configuration that is exceptionally good at demonstrating vitality while deferring the learning that would force change.
The reinforcement loop. Neither component requires outcomes to sustain the other.
Each stall, individually, is vulnerable. Narrative without activity starts to look thin. Activity without narrative looks undirected. Together, they protect each other.
Narrative makes activity legible. A new programme or cohort is not just a cost — it is evidence of strategic momentum. The narrative frames the activity, gives it meaning, and makes it fundable. Without the narrative, the programme would need to justify itself on outcomes. With it, participation is enough.
Activity supplies narrative with fresh material. Every launch, every cohort, every partnership is a new entry in the progress story. The narrative can develop continuously because the activity continuously generates inputs. Without the activity, the narrative would be forced to recycle earlier claims — which becomes visible over time. With it, the story always has new material.
No actor needs to intend this outcome. Each move is locally rational. The stack persists because dismantling either component would reintroduce scrutiny without protection.
Ecosystem Stewardship · Chapter 5The result: outcome pressure is absorbed at both ends. When funders ask for evidence of progress, narrative provides the frame. When the frame looks thin, activity provides the evidence. The loop is closed. The system is never forced to produce the one thing neither stall requires: conversion.
This is the central argument for stack analysis. If you identify S8 and try to shift the system from activity metrics to conversion metrics — without addressing the narrative regime — the intervention fails. The stack compensates.
The narrative explains why conversion metrics are unfair, premature, or inappropriate to the stage of development. The activity continues. The system absorbs the intervention without learning from it.
If instead you try to challenge the narrative — introducing external benchmarks, requiring falsifiable claims — the activity continues to supply fresh material, and the narrative adapts to incorporate it. The story changes form but not function.
The leverage point for this stack is not to attack either component directly. It is to introduce a condition that both components struggle to satisfy simultaneously: one high-status artefact that requires downstream conversion data to be reported alongside activity counts. Not as a critique. As a condition of continuation. The narrative can still frame the activity — but it can no longer frame the activity as a substitute for outcomes.
Cambridge is cited in the book not as a failure but as a precise illustration of what this stack produces in a high-functioning ecosystem. Programmes, spaces, and initiatives expanded reliably. What was harder to trace was how much converted into durable outcomes. Many firms remained small relative to effort invested. Category-defining exits were rare relative to the density of activity.
The point is not that Cambridge was stuck. Parts of the system eventually did learn to narrow. The point is that its stabilisation logic made activity the default response to pressure — and throughput the capability that required sustained effort to develop. The stack absorbed scrutiny without forcing discrimination.
Stack confidence is higher than individual stall confidence because the reinforcement mechanism is visible: narrative output and activity output can both be observed, and the relationship between them — each supplying the other — can be traced through programme reporting cycles, funding renewal documents, and the temporal relationship between narrative claims and activity expansion.
What requires care is the claim about displacement. High activity and high narrative output do not confirm that conversion is being displaced — they raise the question. Confidence in the stack increases when conversion data is structurally absent from reporting (not just unflattering), and when the narrative-activity loop appears to activate specifically in response to outcome pressure.
The 75-diagnostic frequency reflects identification of the pattern, not causal attribution. This stack being present does not mean the ecosystem cannot produce outcomes — it means the conditions for compounding are harder to sustain than the conditions for continuation.
The Narrative × Activity stack appears across every geography and sector we have diagnosed. The question is whether it is operating in yours — and what it is paired with.
Request a Diagnostic →