Three countries. Same problem. Three different explanations.
12 min read
Last year, I sat in three rooms in three countries, two weeks apart, listening to three leadership teams describe the same problem.
Different languages. Different industries. Different org structures. But the same pattern: a senior decision — made twelve to eighteen months earlier — that had quietly become unfalsifiable. Not because the decision was right, but because the cost of revisiting it had grown faster than the cost of keeping it.
In one room, it was a market-entry model. In another, a portfolio allocation. In the third, a leadership structure that had been designed for a different phase of growth.
Each team had an explanation for why things were not working as expected. And each explanation was accurate. That was the problem.
When the explanation is accurate enough to act on, nobody looks for the mechanism underneath it.
In the first room — a commercial leadership team in the Nordics — the explanation was execution. The strategy was sound, they said, but field teams were not implementing it with enough consistency. Two key hires had left. One which has already been applied in 20+ countries. A third market had launched late. The numbers reflected an execution gap.
They were right. There was an execution gap. And so they spent twelve weeks building better execution infrastructure — new dashboards, tighter review cadence, a more detailed launch playbook.
But underneath the execution gap was an assumption gap. The market-entry model had been designed for a competitive environment that no longer existed. The execution was failing because the model assumed two things about customer behaviour that had shifted nine months earlier. No amount of execution discipline would close a gap created by an outdated assumption.
In the second room — a portfolio committee in the US — the explanation was timing. The asset had underperformed because the market had moved later than expected. They were right. The market had moved later. And so they extended the timeline, reallocated resource to bridge the gap, and pushed the next decision point out by two quarters.
But the timing explanation obscured a structural one. The asset was competing in a segment that had consolidated around a different mechanism of action. The delay was not a market-timing problem. It was a market-structure problem. And extending the timeline only postponed the moment when the structural reality would become undeniable.
In the third room — a regional leadership team in APAC — the explanation was people. Two leaders were not aligned. One was blocking a decision the other needed to make. The tension was visible. The team had learned to route around it.
They were right. The two leaders were misaligned. And so they invested in alignment sessions, coaching, a facilitated offsite with a shared set of objectives and ritualised check-ins.
But the misalignment was not a relationship problem. It was a structural one. The two leaders had been given objectives that were mathematically incompatible. One was measured on growth, the other on margin. The system had created a conflict, then labelled it as a people problem.
Three countries. Three explanations. All three accurate. And all three incomplete in the same direction.
The pattern underneath was identical: an upstream decision had created a downstream constraint, and the explanation had settled one level below the actual cause.
This is not unusual. It is, in fact, the default mode of organisational sensemaking. When something is not working, the system generates an explanation that is close enough to be actionable but shallow enough to avoid reopening the decision that caused it.
I do not think this is deliberate. I think it is structural. The people in those rooms were smart, experienced, and well-intentioned. They were not avoiding the real problem — they could not see it, because the explanation they had was good enough to act on.
And that is what makes this pattern so durable. It does not require bad actors or political avoidance. It only requires an explanation that is accurate enough to absorb attention.
Execution problems are real. Timing problems are real. People problems are real. But sometimes they are the visible expression of a structural constraint that lives one level up — and the system will reliably generate the lower-level explanation first, because it is cheaper.
The Nordics team rebuilt their execution infrastructure. It did not close the gap. The US committee extended the timeline. The asset was deprioritised nine months later. The APAC team worked on alignment. One of the two leaders left within the year.
In each case, the explanation was not wrong. It was just not the one that mattered.
What changed in each case was not better analysis. It was a different vantage point.
In each room, when we mapped the upstream decision that had created the downstream constraint — and named it explicitly — the team could see it. Not because the information was new, but because the framing had shifted.
That is the Lever. Not more data. Not better execution. Not alignment coaching. A single structural reframe that makes the invisible mechanism visible to the people who have the authority to change it.
One Lever. Chosen carefully. Applied in the room where the original decision lives. And the pattern breaks — not because you forced it, but because the team can finally see what they were explaining around.
If your team has an explanation that is accurate, actionable, and has not closed the gap in two quarters — the pattern is probably sitting one level above the explanation.
That is where we work.