How many teams in your organization are getting the support from peer teams at the right time, in the right format?
Not eventually. Not after the escalation. At the moment when the dependency actually matters — when one team's output becomes another team's input, when a decision in one business unit reshapes the constraints for three others, when a shift in timeline for one initiative silently invalidates the assumptions behind a dependent initiative.
In the organizations I have worked with, the answer to this question tends to reveal something uncomfortable. The most significant waste is not teams doing duplicate work, though that happens too. The deeper and far more costly problem is that dependent teams are not in sync. Their timelines drift apart. Their assumptions diverge. Their outputs arrive in the wrong format, at the wrong moment, or based on premises that have already changed. The result is an invisible tax that compounds across every layer of the organization.
Scale this pattern across industries and the global cost becomes staggering. Every large organization operates with hundreds of cross-team dependencies. When even a fraction of those dependencies are out of sync, the waste in rework, delayed launches, misallocated resources, and mid-execution course corrections accumulates to an enormous figure. Across economies, this represents one of the largest structural inefficiencies in how organizations operate — and one of the least visible.
Organizations are not machines
The dominant mental model I encounter in leadership conversations is mechanical: inputs, outputs, levers to pull, dials to turn. Set the strategy. Assign the work. Measure the results. When something breaks, find the broken part and fix it.
This mechanical model is useful for relatively simple, stable environments. The model becomes progressively less adequate as complexity grows.
Navigating Complexity (Monimutkaisuuden hallinta) starts with a different premise: organizations are better understood as complex adaptive systems — networks of interdependent people, teams, priorities, and incentives that interact in ways no org chart can fully capture. Dave Snowden and Mary Boone's Cynefin framework, published in Harvard Business Review, offers a useful lens for this: in complex systems, cause and effect can only be deduced in retrospect, and the same action may produce different results depending on context. Dependencies between teams remain invisible until those dependencies collide. Coordination failures look like execution failures, and execution failures get attributed to the wrong causes.
The mechanical model encourages leaders to decompose work cleanly: your team owns this, our team owns that. That decomposition is necessary for accountability — no one is arguing otherwise. But clean decomposition can create a misleading impression that the boundaries on the org chart correspond to boundaries in the actual work.
Those boundaries often do not match. Strategy crosses teams. Customers do not experience your internal structure. Technology dependencies do not respect reporting lines. When you treat a complex system like a machine, you risk optimizing the individual parts while degrading the performance of the whole. Individual teams hit their targets, and the organization still misses its goals. I have seen this gap between team-level success and organizational-level outcomes in enough organizations that I believe it is worth examining honestly, though the severity varies depending on organizational complexity and size.
When dependencies surface at the wrong moment
Consider what happens when a major enterprise undertakes a platform migration that touches every product line. The platform team sets a migration timeline. Three product teams plan their roadmaps around that timeline. But eight weeks into execution, the platform team shifts its sequencing to address a technical constraint they discovered during implementation. That sequencing change is communicated within the platform team's reporting structure, but it does not reach the product teams whose plans depend on the original order. Two of those product teams continue building against interfaces that will not be available when expected. The third team discovers the change through an informal conversation and scrambles to adjust, pulling engineers from another strategic initiative to compensate. By the time the full impact surfaces in a cross-functional review, three months of work across four teams needs to be partially redone or resequenced. The cost is not just the rework. It is the strategic initiatives that were deprioritized to absorb the disruption.
Or consider the pattern I have observed across multiple organizations running parallel go-to-market and product development cycles. A sales team commits to enterprise customer timelines based on a product roadmap shared at the beginning of the quarter. Meanwhile, the product team, responding to technical discoveries and shifting priorities, adjusts its delivery sequence. The sales team is not aware of the adjustment until the customer asks for a progress update. The gap between what was promised and what will be delivered is not a failure of either team. Both teams executed their work competently. The failure is that no mechanism existed to keep the dependency between their commitments synchronized as conditions changed.
These are not edge cases. In complex organizations, the most expensive discoveries tend to be the ones made during execution rather than during planning. By the time work is in flight, the cost of changing course has already multiplied. The dependency between the teams was always there — the dependency just was not visible to the people who needed to see it.
The art of stopping
There is a discipline that does not receive enough attention in leadership conversations: the discipline of deciding what to stop doing.
Finnish has a useful concept for this — Lopettamisen taito, the art of stopping. The concept recognizes that an organization has a finite capacity for coordinated action. Every initiative that probably should be stopped but continues to run consumes coordination bandwidth that could go toward something more important. Stopping is an act of strategic discipline, even though it rarely feels like one in the moment.
Strategic Discipline, in this sense, goes beyond prioritization. Strategic Discipline means actively removing work that no longer serves the strategy — including work that has become redundant or that exists only because the dependency it was meant to serve has already shifted.
The difficulty with stopping is often institutional. Ending an initiative feels like failure, even when ending it is the right decision. In my experience, organizations tend to celebrate launching but not stopping. And so out-of-sync work survives, continues to consume resources, and continues to generate coordination tax across every team it touches.
Alignment versus coherence
There is a distinction that often gets lost in conversations about organizational effectiveness, and the distinction is worth being precise about.
Alignment means everyone is pointed in the same direction. Alignment is achieved through communication — all-hands meetings, strategy documents, cascade briefings. Alignment is necessary. But alignment alone does not guarantee that the organization will execute well.
Coherence means the system is actually working together. Coherence means that when team A makes a decision, team B is not inadvertently undermined by that decision. Coherence means dependencies between initiatives are mapped and managed before those dependencies surface as surprises. Coherence means stopping one project has a visible effect on the capacity available for other projects. Coherence means that the organization's behavior — not just its stated intentions — is internally consistent.
Alignment is a communication challenge. Coherence is a design challenge.
I have seen organizations invest heavily in alignment while underinvesting in coherence. These organizations communicate the strategy clearly, and then create conditions that make coherent execution quite difficult — fragmented ownership, invisible dependencies, no mechanism for keeping dependent teams in sync, and cultural norms that reward launching over stopping.
The consequence is an organization that knows where it wants to go, but whose parts cannot quite move in concert. This disconnect between direction and coordination is frustrating for everyone involved, especially because the disconnect looks like an execution problem when it is more often a design problem.
Diagnosing the tax you are already paying
The invisible tax does not announce itself. But the tax leaves traces. Two questions can help you find them.
How many cross-team dependencies were discovered during execution rather than during planning? If the answer is most of them, the source is likely structural rather than individual. Your planning process may lack a mechanism for surfacing dependencies before work begins. The cost you are paying is the difference between mid-execution course correction and the coordination that planning-stage visibility would have made possible.
When a team changes its timeline or delivery sequence, how quickly do the teams that depend on that output learn about the change? If the answer is weeks, or only when the collision happens, the organization lacks a synchronization mechanism for its most critical interdependencies. That gap, multiplied across every active initiative, is where the invisible tax accumulates.
These are questions worth exploring honestly. The global cost of out-of-sync organizations is enormous — in wasted resources, in delayed products, in strategic investments that fail not because the strategy was wrong, but because the parts of the organization executing that strategy could not see each other clearly enough to move together. The first step toward coherence is visibility. You cannot synchronize what you cannot see.