Execution Is a Structure Problem

I have sat in the room where a good strategy died.

Not a bad strategy — a good one. The analysis was sound. The slides were clean. Leadership nodded. Everyone left the offsite believing something would change. Six months later, nothing had. The plan was still sound; it had simply never moved. Three new priorities had arrived to compete with it, and the people who were meant to own it were no longer sure they did.

The instinct, when this happens, is to blame the thinking. Maybe the strategy was wrong. Maybe the market shifted. Maybe we need a refresh. So the cycle begins again — another planning effort, another round of genuine conviction, and the same quiet fade a few months on. It is an easy trap, because the response feels productive. It just doesn't address what actually went wrong.

But the thinking was almost never the problem. I have watched brilliant strategies fail and ordinary ones succeed, and the difference was never the quality of the idea. It was whether anyone had built the structure to carry it.

Strategy Is Not Structure

Strategy tells you what to do. It says nothing about how the work actually happens — who owns which decision, what gets sequenced before what, how progress gets seen, what happens when two priorities collide. Those are not strategy questions. They are structure questions. And most organizations pour enormous effort into the first set and almost none into the second.

Here is the pattern I have seen across twenty-five years, in banks and ratings agencies and global delivery organizations on three continents. The strategy review is rigorous — hours of debate, real scrutiny, senior attention. The execution review, if it happens at all, is a status update: green, yellow, red, next slide. We bring our hardest thinking to the plan and far less of it to the delivery. Then we are surprised when the plan delivers and the delivery doesn't.

The Unglamorous Work

Structure is unglamorous work. It is deciding that this initiative has one owner, not a committee. It is breaking a two-year ambition into ninety-day moves with a date attached to each. It is building a feedback loop that surfaces a problem in week three instead of month nine. It is removing the blocker nobody wanted to name. None of it makes a good slide. All of it is the difference between a strategy that moves and a strategy that gathers dust.

I learned this the first time in a back office in Gurgaon, years before I had language for it. We had a process to fix and a plan to fix it. The plan was fine. What made the savings hold was not the plan — it was that we took the old structure apart so completely that there was nothing left to drift back to. We didn't lay the new way on top of the old one. We removed the old one. The structure carried the change because we built it to.

Look Underneath the Strategy

Every time since, the lesson has held. When a transformation stalls, the people involved reach for a better strategy, because strategy is the thing they know how to produce. The harder, quieter answer is almost always that the strategy was fine and the structure was never built. Intent was never the missing piece. It rarely is.

So when someone tells me their strategy isn't landing, I have learned not to look at the strategy. I look underneath it. That is usually where the failure is — and it is always where the fix is.