The Executive Operating Model · Part 1 of 6
Strategy Fails Where It Becomes Work
Most strategy is sound enough to succeed. It leaks in the untracked distance between the decision and the work, because executive teams have no operating model for their own execution.
Every year a leadership team sets a strategy it believes in. The direction gets debated at an offsite, refined into a deck, and communicated with real conviction. Twelve months later the results are disappointing, and the reflex is almost automatic: the team goes back to the strategy. It reopens the thesis, questions the market read, and starts drafting something sharper for the next cycle. In most of the cases I have watched up close across delivery and operating-model work, that reflex is aimed at the wrong place. The strategy was usually sound enough to succeed. What failed happened after it, in the long and largely undocumented distance between the decision and the work that actually shipped.
That distance is where strategy quietly leaks, and most organizations have no instrument pointed at it. A leadership team can tell you what it decided at the offsite and what the annual numbers eventually were. It usually cannot tell you what happened in between: which of its own commitments were carried through, which were silently dropped when the quarter got busy, and where the intended sequence of moves came apart. The strategy is documented at the top and the outcomes are visible at the bottom, and the mechanism that was supposed to connect them is mostly invisible. Reopening the strategy does nothing about this, because the break did not occur where the strategy was written. It occurred where the strategy was supposed to become work.
It helps to compare the executive team to the delivery organization it oversees, because the contrast exposes the gap precisely. A competent delivery team runs on an operating model built to convert intent into shipped outcomes on a cadence. It maintains a backlog, commits to time-bound pieces of work, tracks them against the commitment, holds regular checkpoints, and re-sequences openly when reality changes. None of that guarantees perfect delivery, but it means the work is operated rather than merely hoped for, and that drift becomes visible while there is still time to respond.
The executive team that owns the strategy has no equivalent. It has planning rituals and a calendar of meetings, but no operating model for its own execution. Its commitments are real and consequential, and they are also the least instrumented work in the company. A decision that has to be made, a capability that has to be funded and unlocked, a cross-functional dependency that only leaders can clear: these are the atomic units of executive execution, and they typically live in people’s heads and in the minutes of meetings that do not connect to one another. They are not written down as time-bound outcomes, not sequenced against each other, and not tracked with anything close to the rigor the same executives demand of the teams below them. When one of them slips, nothing surfaces it. The team simply arrives at the end of the year with a general sense that it was busy and somehow behind.
This is why the failure is structural rather than a matter of effort or intelligence. The leaders involved are usually capable and genuinely committed to the plan. They miss because the system they operate in gives them no way to carry an intent from strategy through to a delivered result, and no way to see it drifting in time to correct. Asking those same people to try harder, or to believe in the strategy more, does not supply the missing machinery. Neither does a better strategy. A stronger plan fed into the same untracked distance leaks in exactly the same way.
Why the usual answers do not close the gap
A leadership team reading this will reasonably object that it already runs annual planning, objectives and key results, and quarterly business reviews, and that execution is therefore already covered. Those mechanisms are useful, but they mostly measure the output of the delivery organization and the health of the numbers. They rarely track the executive team’s own commitments as work in their own right. A quarterly review that reads the scoreboard is a different thing from an operating model that runs the plays. It tells you the score changed; it does not tell you whether the decision that was supposed to be made in the first quarter was actually made, whether the dependency someone owned in February was ever resolved, or whether the team held the sequence it agreed to rather than quietly re-prioritizing under pressure and never saying so.
A different objection holds that execution belongs to the delivery organization rather than the leadership team. That is fair for the work that reaches a delivery backlog. A large share of executive execution never reaches one. It consists of decisions only executives can make, capabilities only they can fund, and dependencies only they can clear. That work is theirs to operate, and it is precisely the work that has no operating model around it. Handing execution wholesale to the teams below leaves the executive team’s own portion of it unmanaged, and that portion is often what the rest of the plan is waiting on.
There is also a practical concern that this amounts to more process, and most leadership teams already carry too much of it. The concern is legitimate, and the answer is not another ritual layered onto an overloaded calendar. An operating model for executive execution only works if it is deliberately kept light, which is a genuine design constraint rather than an afterthought, and a subject that deserves its own treatment later in this series. The point to settle first is that the absence of any such model is a real and specific problem, not a vague complaint about discipline.
An operating model for the executive team
The fix that follows from this diagnosis is to give the executive team the same kind of operating model it already expects of everyone it leads: a disciplined way to convert intent into outcomes on a cadence, and to make drift visible early enough to act on. Such a model has a few load-bearing parts. It nests planning horizons so that three-year direction stays tied to what the team commits to this month. It defines a clear atomic unit of execution, a time-bound and outcome-based commitment that the team actually tracks rather than a vague priority. It establishes a deliberate way to change direction on a cadence instead of reactively, so that agility comes from disciplined re-sequencing rather than constant churn. And it reads execution health through a small set of honest measures instead of a year-end impression.
The claim here is narrower than the design work those parts represent, and it comes before all of it: the executive team needs an operating model for its own execution in the first place, and the absence of one is why so much sound strategy dies after it is set. The practical consequence is that two leadership teams holding identical plans will get very different returns on them. The team that treats its own commitments as tracked work, sequenced and followed through, will convert more of the plan into outcomes than the team that leaves that work informal, and it will find out where it is slipping while it can still respond. That difference does not come from a better thesis or a more inspiring offsite. It comes from having an operating model for the one layer of the organization that has usually gone without one.
So the place to start is to stop treating a stalled strategy as evidence that the strategy was wrong, and to look instead at the machinery, or the absence of machinery, that was supposed to carry it into the work. Building that machinery is what the rest of this series takes up: the nested cadence that links the horizons, the commitment that serves as the unit of executive execution, and the measures that show whether follow-through is actually happening.