Organisations invest heavily in removing constraints from their operations.
Processes are redesigned. Systems are upgraded. Structures are reorganised.
And on paper, the bottlenecks disappear.
What looks like resolution is often something else entirely. The constraint has not been eliminated; it has moved.
The Illusion of Resolution
When a bottleneck is addressed in one part of a system, the immediate impact can feel like progress. Work moves faster, delays shrink, and performance appears to improve.
But these gains are often local, not systemic.
The underlying pressure — the imbalance between demand, capacity and coordination — does not vanish. It relocates. And it tends to resurface where work crosses boundaries: between teams, functions or systems.
This is where bottlenecks are most likely to reappear, and where they are most difficult to diagnose.
Where the Friction Goes
In many organisations, the most significant constraints are no longer found within execution itself. They emerge in the spaces between.
As work moves from one function to another, it encounters new forms of resistance. A receiving team may not have the capacity to absorb the volume or variability of incoming work. That capacity may already be consumed by rework — issues created upstream but only resolved downstream.
In other cases, the challenge is less about capacity and more about clarity. Work arrives without sufficient context. Priorities are unclear. Decisions slow, not because they are complex, but because ownership is diffused.
Even the mechanisms designed to hold the system together — the “horizontal glue” of coordination and planning — can become constraints in their own right. When these functions are overloaded or not operating effectively, they introduce delay rather than remove it.
Individually, these issues are manageable. Together, they recreate the very friction organisations believed they had eliminated.
Why Structural Fixes Don’t Hold
Most transformation efforts rely on structural interventions. Teams are reconfigured. New roles are introduced. Tools and workflows are implemented with the intention of improving efficiency.
These changes often deliver results — initially.
But structure alone does not determine how work behaves. Without a corresponding redesign of how work flows, pressure simply shifts to the next available point in the system.
What appears to be a fix is often just a redistribution.
This is why constraints can disappear from dashboards while continuing to affect delivery in practice. The system has changed shape, but not balance.
The Leadership Blind Spot
From a leadership perspective, it is natural to track where problems have been resolved. When a bottleneck no longer appears in a given function, it is often considered closed.
But operations tell a different story.
New queues begin to form elsewhere. Coordination effort increases. Delays become tied to decision-making rather than execution. Rework grows in areas that were previously unaffected.
Those closest to delivery tend to identify these shifts quickly — not because they are looking for them, but because they experience the consequences directly.
The gap, then, is not one of awareness. It is one of perspective. Movement is mistaken for resolution.
Rethinking Where Bottlenecks Live
Bottlenecks in modern delivery environments are less about individual productivity and more about system behaviour.
They are shaped by how work moves, how it is prioritised, and how decisions are made along the way.
This makes them less visible than traditional constraints, but no less impactful.
It also means they cannot be addressed in isolation. A bottleneck is rarely owned by a single team. It is produced by the interaction between multiple parts of the system.
From Relocation to Resolution
Addressing these constraints requires a shift in focus.
Not towards where the bottleneck is today, but towards how it forms and where it is likely to emerge next.
That means understanding how demand flows into each part of the system, whether capacity is aligned to handle it, and how much rework is being introduced before work crosses a boundary. It means bringing clarity to decision pathways and ensuring that coordination functions enable flow rather than constrain it.
In short, it requires designing the system with movement in mind.
Conclusion
Bottlenecks do not disappear simply because they are removed from one part of the organisation. They reappear where the system is least able to absorb them.
The organisations that outperform are not those that eliminate constraints fastest on paper. They are the ones that understand how constraints behave in practice — how they shift, how they accumulate, and how they can be prevented from reforming elsewhere.
Because real improvement is not about moving friction.
It is about removing it from the system entirely.
