The Finding
Nelson Repenning and John Sterman of MIT Sloan School of Management, studying why process improvement so often fails to spread or hold, identified a pattern they called the capability trap: under sustained pressure, organisations default to effort-based responses over structural ones, and — critically for this article — the people and teams who develop genuine improvements receive no visible credit for problems that, because of their improvement, never happen elsewhere. Their research suggests this is a major reason good local improvements often fail to spread across an organisation, even when everyone agrees, in principle, that they should.
What It Means in Practice
Consider an organisation where one team develops a method that reduces a task’s time by a third. The method is written up and shared. Other teams read it. Eighteen months later, no other team has adopted it.
The easy explanations are resistance to change or poor internal communication — and the response those explanations invite is usually more communication: another presentation, another reminder, a renewed push to get the method adopted elsewhere.
Looked at more closely, communication was not the constraint. Adopting the method requires roughly two days of disruption to a team’s existing workflow, and no other team currently has the slack to absorb that disruption. Each team, examining its own situation, has correctly judged that it cannot afford the transition right now — not because the improvement isn’t valuable, but because the short-term cost of adopting it exceeds what any individual team’s current capacity allows, even though the long-term gain would clearly outweigh it.
This is complexity hiding inside ordinary, sensible, individually-rational decisions. No single team is behaving irrationally by declining to adopt the improvement. The organisation as a whole, however, has no mechanism for absorbing the short-term cost of a long-term structural gain — which means improvements stay wherever they happen to originate, regardless of how much value they would create if they spread. The complexity is not visible in any one team’s decision. It is visible only at the level of the organisation, in the gap between what individually rational local choices add up to and what the organisation as a whole would gain if it could coordinate around the transition cost.
The consequence compounds across the whole organisation, not just around this single improvement. Every team that has independently developed a genuinely useful local method represents an instance of value the organisation is not capturing at scale — and because each instance looks, from the outside, like a small, isolated success story rather than a symptom of a structural gap, the aggregate scale of the missed value rarely gets tallied anywhere. An organisation could, in principle, be sitting on a substantial amount of proven, low-risk improvement it already possesses, simply because it has no mechanism for moving that improvement across the internal boundaries between teams.
Where It Varies
By organisational slack. Organisations running close to capacity everywhere will see this pattern more consistently than those with some genuine spare capacity somewhere to absorb transition costs.
By how improvement is measured. Where teams are measured purely on their own output, absorbing a short-term hit to adopt someone else’s improvement is actively penalised by the measurement system, regardless of its long-term value.
By visibility of the originating team’s success. The team that developed the improvement is usually visible and credited. The teams that could have adopted it and didn’t are rarely asked why, which means the barrier itself often stays undiagnosed.
By the size of the transition cost relative to normal variation. Improvements requiring a small, easily absorbed transition spread far more easily than ones requiring a substantial, visible disruption — regardless of the relative size of the underlying benefit.
There is a further pattern worth noting: the organisations most affected by this dynamic are often the ones that pride themselves most on local team autonomy. Autonomy that lets a team develop a genuinely useful local improvement is the same autonomy that lets every other team independently, and rationally, decline to adopt it. The dynamic is not a failure of autonomy as a principle — it is a gap in what autonomy alone can coordinate, which is specifically the kind of cross-team resource reallocation this pattern requires and which no single team, acting independently within its own remit, is positioned to arrange on its own.
Looking for your own sector? The Other Sectors page points to the closest match.
Questions worth considering
- What genuine improvements have been developed somewhere in the organisation but never spread beyond where they originated?
- Who currently bears the short-term cost of adopting an improvement, and who receives the long-term benefit — and are they the same people?
- Does any part of the organisation currently have the capacity to absorb a transition cost on behalf of a wider improvement, or is capacity fully committed everywhere?
- Who bears the cost of an improvement, and who receives the benefit?
More on this topic: Operations.
Your team is facing similar challenges?
Subscribe to The Riddle Ledger
Perspectives are sent as they are published, with no promotional email, and you can unsubscribe at any time.