Why Most Strategy Dies Between the Boardroom and the Shop Floor

Picture a scene that probably feels familiar. The senior leadership team spends two days off-site. A consultant facilitates. Post-its cover every wall. By the end of day two, there's a clear strategic direction: three priorities, five initiatives, a compelling narrative about where the organization is heading. The energy in the room is real.

Six months later, the same leadership team sits down for a quarterly review. The strategy deck is on the screen. And one by one, the status updates roll in: delayed, pending, in progress, blocked. The initiatives that felt so clear in that off-site room have somehow dissolved into the fog of everyday operations.

This is not an unusual story. Research by the Harvard Business Review consistently finds that fewer than 10% of well-formulated strategies are successfully executed. McKinsey estimates that up to 70% of large-scale change programs fail to achieve their goals. These aren't failure-to-plan statistics. These are failure-to-translate statistics.

Why do most strategy implementations fail?

The conventional diagnosis blames execution discipline, middle management buy-in, or a lack of accountability. Fix those, the thinking goes, and strategy follows. So organizations invest in better project management software, more rigorous KPI tracking, and more frequent performance reviews. And then the same thing happens again.

The real problem isn't discipline or buy-in. It's structural. Strategy and operations speak entirely different languages. Strategy operates in horizons of quarters and years, uses language like "market position" and "competitive advantage," and lives in slide decks reviewed monthly. Operations runs on days and weeks, uses the language of capacity, throughput, and blockers, and lives in team standups and work queues.

Between those two worlds — the boardroom and the shop floor — there is almost never a functioning translation layer. No shared mechanism that takes a strategic priority and turns it into a daily decision. No forum where a frontline team's unresolved blocker gets elevated to a strategic risk before it becomes a catastrophe.

This isn't a people failure. It's a system failure. And it won't be solved by trying harder.

What is the "translation layer" — and why is it missing?

The translation layer is the mechanism that converts strategic intent into daily prioritization. It answers a deceptively simple question: how does a team on the floor know, on any given Tuesday, that what they're working on is the right thing — given the strategy the leadership team agreed on six months ago?

In most organizations, the honest answer is: they don't. They work on what was agreed in the last team meeting, or what the loudest request was, or what's been on the backlog the longest. Strategic priority rarely reaches them in a form they can act on.

The translation layer is missing for three interconnected reasons. First, strategy is typically formulated in a context of abstraction — the off-site, the slide deck — and communicated through a cascade of meetings that systematically lose nuance at every level. By the time a strategic priority reaches a frontline team, it may have been paraphrased five times and lost its original intent entirely.

Second, there is usually no mechanism for information to flow upward. Strategic leaders make decisions based on assumptions about what's happening in operations. If those assumptions are wrong — if a key process is struggling, if a dependency is blocked, if capacity is constrained — there's no regular channel to surface it before it becomes a crisis.

Third, strategy and operations review on different rhythms. Leadership reviews strategy quarterly. Operations runs weekly or daily. There is almost never a cadence that bridges those two clocks — a regular moment where the strategic picture and the operational reality are held in the same room at the same time.

What are the signs your organization has this problem?

The strategy-execution gap rarely announces itself. It tends to show up as a persistent, low-grade friction that leaders attribute to culture, capability, or individual performance. Here are four signals that the real issue is structural:

If two or more of these resonate, the issue isn't execution discipline. It's the absence of a system that makes strategy visible and operational across the organization.

Why don't dashboards and more reporting fix this?

The default response to the strategy-execution gap is to improve visibility: build a better dashboard, introduce OKRs, create a strategy map, track more metrics. These interventions share a common assumption — that the problem is information, and that more information will solve it.

It doesn't. Data visibility is not the same as shared understanding. A dashboard tells you what the numbers are. It doesn't tell you why the numbers are what they are, what decision is needed, who needs to make it, or what it means for the three other things the team is working on. A dashboard is a report. The translation layer is a practice.

The gap between those two things — report versus practice — is where most improvement initiatives fall short. Organizations that add more reporting often find themselves with more data and the same strategic stagnation. Sometimes more data actually makes things worse, because it creates the illusion of alignment without the substance of it.

How does Obeya close the strategy-execution gap?

The Leading with Obeya method was developed precisely to solve this problem. At its core, Obeya is not a visualization tool — it's a leadership operating rhythm. A structured, recurring practice in which strategic direction and operational reality are brought into the same room, at the same time, by the same team.

The method organizes information across five integrated boards, each answering a different layer of the management question:

• →Strategic Direction — Where are we headed, and what capabilities do we need to get there? Sets the framework for everything else.
• →Performance — The indicators and key results that show how well the team is doing — and what to prioritize next.
• →Tough Problems — Structured root-cause problem solving for challenges the team doesn't yet have a clear solution to.
• →Plan to Value — Milestones, key steps, and resource allocation that show how the team will deliver value to customers and the organization.
• →Act & Respond — The team flexibly addresses emerging problems, requests, and decisions — keeping the plan on track while absorbing daily reality.

These five boards, reviewed together on a structured cadence, create something that no dashboard can: a living, shared understanding of the relationship between strategic intent and operational reality. The discussion that happens in front of them is not a status report — it's a conversation about decisions. What needs to change? What needs to escalate? What priority needs to shift?

Obeya originated at Toyota in the 1990s, where it was used to coordinate the development of the Prius — a project of extraordinary complexity, delivered on time, at twice the original fuel-efficiency target. The method has since been formalized by Tim Wiegel into the Leading with Obeya system, now used by leadership teams in manufacturing, healthcare, financial services, and technology organizations worldwide.

What does this look like in practice?

de Volksbank is one of the clearer examples of Obeya working at scale. Joris Verheij, director of Customer Integrity & Customer Administration, introduced Obeya across all levels of his department — from the board of directors to teams on the shop floor — while managing a team of over 500 people.

When he started, the same patterns he sees in most organizations were present: teams didn't know each other's goals, who was responsible for what, or how their work connected to the broader strategy. Every department was operating as an island. Within a few months of introducing Obeya, those patterns began to change.

Each department now has its own Obeya room. One wall holds the strategy and performance indicators. The other holds the roadmap of initiatives. Critically, those two walls correspond — any improvement initiative must visibly connect back to a strategic priority. If it doesn't, it doesn't belong on the wall.

Verheij holds a bi-weekly Obeya, blocking a full morning for four focused sessions of 45 minutes each. The result: no more surprises. He knows exactly how his teams are doing and has the clarity to focus his attention where it matters most. "You feel like you're holding the steering wheel yourself," he says, "rather than being constantly caught off guard."

Tim Wiegel, who developed the Leading with Obeya method, often points to a related pattern he sees across the organizations he works with: management teams routinely can't answer basic questions about their own strategic priorities. Half the indicators on a new Obeya are often empty at first — not because the data doesn't exist, but because teams had never identified what they actually needed to see. Obeya surfaces that gap and creates the discipline to fill it.

Having worked inside de Volksbank during that period, I saw this firsthand. The shift isn't about getting better data on the wall — it's about what happens when people stand in front of it together. As I put it then: "It is a communication board, not an information board."

Where do you start?

The strategy-execution gap is structural, but that also means it's fixable. The path forward isn't to try harder at the things that aren't working — more meetings, more reporting, more accountability frameworks. It's to introduce a practice that bridges the two worlds.

A practical first step is an honest conversation with your leadership team: can everyone in this room, right now, describe the current strategic priorities and explain what the operational status of each one is? If that conversation surfaces uncertainty or inconsistency, you have identified the gap. And you have a starting point.

If you want to explore what a structured approach looks like for your organization, the Leading with Obeya training programs offer both foundational understanding and practical implementation support. Or explore the resources section for videos, frameworks, and case studies that go deeper on how the method works in practice.

The distance between your boardroom and your shop floor doesn't have to be a gap. With the right operating rhythm, it becomes a connection.