One of the most useful questions in strategy execution is not “which team failed?” Sometimes a strategic outcome is missed for exactly that reason: a critical team was late, a sales target was missed, or a product delivery slipped.
But there is another pattern I have seen often enough to name. Many local decisions are reasonable, even successful, and still the organization does not move as one system.
Sales optimizes for commitments it can win. Product optimizes for a roadmap it can ship. Operations optimizes for efficiency. Finance optimizes for control. Each decision can make sense locally. The strategic problem appears when the decisions are not synchronized around the same causal path to the outcome.
Understanding direction is not the same as acting together
The word “alignment” can be slippery, especially for non-native English readers. I use it carefully.
By alignment, I mean that people understand the direction. They know the priority, the message, and the broad intent.
By coherence, I mean that the organization can act together in that direction. Dependencies are visible. Sequencing is synchronized. Handoffs have owners. Conflicts are surfaced. Work that no longer fits can be stopped.
So the difference is simple: alignment is shared understanding. Coherence is coordinated action.
A company can have the first without the second. Everyone may agree on the strategic priority while different teams make reasonable local decisions that create friction for each other.
The hidden cost sits between teams
The most expensive execution problems often sit in the spaces between teams.
A platform team changes sequencing after discovering a technical constraint. The change is clear inside the platform team, but not visible to product teams that planned around the original order. A sales team commits to a customer timeline based on a roadmap that product has since adjusted. A function deprioritizes a dependency that another team still treats as critical.
No single decision is irrational. The problem is that the system does not keep related decisions synchronized as conditions change.
By the time the collision becomes visible, the cost is no longer only coordination. It is rework, delayed launches, frustrated customers, and strategic work that gets paused to absorb disruption.
The bias for action has a shadow side
Most management cultures reward action. A problem is surfaced, so an action is started. A risk appears, so a workstream is created. A customer complains, so an initiative begins. Bias for action is often useful. It prevents analysis paralysis.
But in a complex portfolio, every new action consumes attention, coordination, and leadership bandwidth. If every issue becomes a new initiative, the organization may look responsive while becoming less coherent.
This is why acting coherently is not only about starting the right work. It is also about deciding which work should not start, which work should be merged, and which work should end.
The art of stopping
Many organizations are better at launching initiatives than ending them. Work continues because it has an owner, a budget, a steering group, or a history. But if the strategic rationale has weakened, the initiative still consumes coordination capacity.
The Finnish phrase Lopettamisen taito, the art of stopping, captures an underrated leadership discipline. Stopping is not proof that the previous decision was foolish. It can be evidence that the organization is learning and reallocating attention to the work that now matters most.
Without this discipline, the portfolio accumulates strategic debt: work that made sense once, but no longer clearly supports the current intent.
What to notice
In your next portfolio discussion, do not only ask whether teams are progressing. Ask whether the work is synchronized. Which dependencies were discovered only after execution began? Which initiatives depend on assumptions another team has already changed? Which work continues because it is easier to continue than to stop?
That is where coherence becomes visible. Not in whether each team is busy, but in whether the parts can move together.