Why Smart Leaders Keep Making the Same Strategy Mistake
The knowing-doing gap is real — and more costly than most executives admit
There is a conversation I have had too many times to count.
A leadership team sits around a table. They have just completed a rigorous strategy review. The deck is polished, the market logic is sound, the targets are ambitious but grounded. Everyone nods. The CEO declares alignment. The offsite ends.
Six months later, execution has stalled. Priorities have quietly shifted. Middle management is running a different agenda from what was agreed. And the leadership team, privately, knows exactly why — because they have been here before.
This is the knowing-doing gap. And it is one of the most persistent, underacknowledged problems in organisational life.
We Know What Good Looks Like
Most experienced leaders can articulate the principles of effective strategy execution. Focus on a small number of priorities. Translate strategic intent into clear behaviours. Ensure accountability is real, not just declared. Invest in the human side of change.
Ask any senior executive to diagnose a struggling organisation, and they will identify these failure modes within minutes. The analysis is almost never wrong. What I have found, however, is that the same leaders who diagnose these problems in others reproduce them in their own organisations — sometimes within the same year.
I have done it myself. Early in my career as a general manager, I knew that fragmented priorities were undermining our performance. I could see it clearly. I even named it in leadership meetings. And then, under pressure to demonstrate progress across multiple fronts, I added three new workstreams to an already overloaded agenda.
Knowing was not enough.
Why Knowledge Doesn't Prevent Repetition
The gap between knowing and doing is not a knowledge problem. It is a pressure problem.
When organisations face performance challenges, the instinct is to act — to add initiatives, accelerate timelines, demonstrate visible effort. The leaders who do this are not naive. They know, at some level, that more activity rarely produces more results. But inaction, or deliberate subtraction, feels like a failure of leadership in the moment.
There is also a social dimension. Strategy discussions in senior teams involve status, relationships, and political capital. Eliminating a priority that a colleague championed is not simply a rational decision — it is a signal. It costs something. And so compromises are made. The agenda stays crowded. The knowing-doing gap widens.
What Breaking the Pattern Actually Requires
In my experience, closing the gap requires three things that feel uncomfortable in practice, even if they sound sensible in theory.
The first is the willingness to subtract publicly. Not quietly deprioritising things, but explicitly naming what the organisation will not do this year — in a town hall, not just a leadership memo. This creates real accountability, because it can be checked.
The second is protecting focus under pressure. The hardest moment in strategy execution is not the launch. It is month four, when results are slower than hoped and the temptation to pivot or add is strongest. The leaders who resist that temptation, and reinforce the original focus instead, tend to be the ones who break through.
The third is honest retrospection. Most organisations conduct post-mortems on failed projects. Very few conduct honest reviews of why they keep repeating the same execution failures. Building that practice — genuinely, not performatively — is one of the highest-return investments a leadership team can make.
A Final Reflection
I no longer believe that leaders fail because they lack insight. Most of the ones I have worked with are perceptive, experienced, and genuinely motivated to get things right.
What trips them up, repeatedly, is the gap between what they know and what the system — the pressure, the politics, the instinct to act — pushes them to do.
Closing that gap is not an intellectual challenge. It is a leadership discipline. And like any discipline, it requires practice, discomfort, and a willingness to do the harder thing when the easier one is available.
he Day I Stopped Trusting My Dashboard
On the gap between what the numbers tell you and what is actually happening on the ground
The numbers looked good. Not great — but solid. Utilisation was tracking above target, revenue per unit was holding, and the weekly operations report showed no major flags.
I remember sitting in my office, reviewing the dashboard on a Wednesday morning, and feeling reasonably confident. Then I walked the floor.
What I found did not match what I had just read.
The Gap No Metric Captures
I will not name the specifics, because the details are less important than the pattern. What I observed that morning was a team that was technically hitting its numbers by doing things that were quietly unsustainable — cutting corners on process, deferring maintenance decisions, and absorbing pressure in ways that were not visible in any report I received.
The staff knew. The frontline supervisors knew. The data did not know, because data captures outputs, not the conditions under which those outputs are produced.
I had been managing the organisation through a layer of abstraction. The dashboard was accurate. It just was not telling me the whole truth.
What I Got Wrong
My mistake was not a failure of analysis. It was a failure of presence.
In the months leading up to that moment, I had been spending the majority of my time in leadership meetings, investor calls, and strategic planning sessions. These are legitimate demands on a general manager's time. But I had allowed them to crowd out something equally important: unstructured time with the people doing the actual work.
I had assumed that the reporting structure would surface anything I needed to know. What I had not accounted for was that people filter information as it travels upward. Not out of bad faith — simply because they want to solve problems before escalating them, or because they are not sure what leadership actually wants to hear.
The dashboard reflected the organisation's best performance of itself. What I needed to see was the organisation as it actually was.
The Shift That Followed
I made two changes after that morning.
The first was structural: I blocked two hours each week in my calendar as non-negotiable floor time. No agenda, no prepared briefings. Just presence — conversations with frontline staff, observation of how work actually got done, and listening without the filter of formal reporting.
The second was cultural: I started being more explicit in leadership meetings about valuing early, unpolished information over clean, curated updates. I wanted my team to tell me about problems when they were still small, not after they had been contained.
Neither of these changes was dramatic. But together, they meaningfully changed what I knew and when I knew it.
The Broader Lesson
Dashboards are powerful tools. I still use them and I still believe in data-driven management. But data reflects the past, and it reflects what was measured. It cannot capture morale, discretionary effort, or the small behavioural adjustments that teams make under sustained pressure.
The leaders I have seen navigate complexity most effectively are not the ones with the best reporting infrastructure. They are the ones who combine rigorous data with genuine proximity to the organisation — who treat walking the floor not as a symbolic gesture, but as a source of real intelligence.
The day I stopped trusting my dashboard was not the day I stopped using it. It was the day I understood what it could not tell me.