A CXO team spends a full quarter getting a decision right. They pressure-test it, argue over it, bring in outside data, and finally align. Six months later, the decision is half-implemented, quietly altered, or sitting untouched in a deck nobody opens any more. The team didn’t get the decision wrong. They fell into the decision execution gap — and if you lead a business, you have almost certainly watched it happen inside your own leadership team.
Two Different Jobs, One Team
We tend to talk about “leadership” as a single skill. It isn’t. Deciding well and implementing well draw on nearly opposite mental habits, and the same group of Founders, CEOs and Business Leaders is expected to switch between them without ever being told the switch is happening.
To decide well, a CXO has to stay open-minded. Dissent has to be welcome in the room. Judgement has to hold off until the marginal information is separated from the noise. To implement well, that same CXO needs the opposite posture: closed, focused, unwilling to keep reopening a settled question. This isn’t a metaphor Coach borrowed from sport. It’s documented in decision psychology going back to the 1980s. Heckhausen and Gollwitzer’s Rubicon Model of Action Phases names two distinct cognitive states — the deliberative mindset, marked by open, balanced weighing of pros and cons, and the implemental mindset, marked by focus, commitment, and active filtering out of anything that doesn’t serve the chosen goal. The line between them is the “Rubicon” — once crossed, going back and forth is costly, not free.
A CXO team that never marks that line asks its own people to run both mindsets simultaneously, in the same meeting, on the same decision. That’s where the trouble starts.
Why the Same People Struggle with Both
This isn’t a fringe problem. Research from Harvard Business Review, based on a multi-year study spanning more than 250 companies, found that two-thirds to three-quarters of large organisations struggle to implement the strategies they’ve already agreed on — and the cause usually isn’t a lack of alignment between strategy and activity, which is what most executives assume. The real culprit is coordination: people and functions that can’t be relied on once the decision leaves the boardroom (Sull, Homkes and Sull, Harvard Business Review, 2015).
I have seen this play out inside CXO teams directly. A decision gets agreed unanimously in the room. Weeks later, someone on that same team is quietly slow-walking their part of it — not out of malice, but because the decision touches their function’s headcount, their budget, or their standing, and nobody addressed that at the point of closure. The mistake isn’t in the decision. It’s in assuming that agreeing a decision and committing to it are the same act.
What Happens Without a Marked Line
Without a deliberate boundary between deciding and implementing, a leadership team ends up with one of three outcomes: partial implementation, where the parts that suit individual CXOs get done and the rest drifts; quiet alteration, where the decision is reshaped in execution to look more like what the losing argument wanted; or, in the worst cases, passive sabotage, where a CXO who never truly accepted the call lets it fail without ever openly opposing it.
None of this shows up as an obvious problem. It shows up as slipping timelines, review meetings that keep “re-discussing” a decision that was supposedly final, and a Board that can’t tell whether the strategy failed or was never really tried.
Five Disciplines for the Decision Phase
- Protect dissent structurally, not informally. Assign a named challenger role for major decisions, or use a formal Agree step where designated people can veto and must offer an alternative rather than simply object (this is the discipline behind Bain’s RAPID framework, first published by Rogers and Blenko in Harvard Business Review, 2006).
- Separate the evidence-gathering from the judgement call. Bring outside data and outside voices in before anyone in the CXO team stakes a public position — early positioning kills genuine dissent.
- Name who actually decides. Input, recommendation and decision are different roles. A CXO team that treats every voice as a decider ends up with a decision nobody owns.
- Test the decision against shared vision, not only against the numbers. Where interests genuinely diverge across the team, a shared long-term vision and shared upside does more to secure future commitment than the analysis itself.
- Mark the Rubicon visibly. A documented decision, dated and named, with a single accountable Owner — not a general sense in the room that “we’re aligned.”
Five Disciplines for the Implementation Phase
- One named Owner, no shared accountability. The moment implementation starts, the CXO team’s job changes from deciding together to enabling one accountable person to deliver.
- Convert the decision into a small number of measurable priorities. A decision translated into twelve initiatives is a decision nobody will finish.
- Review outcomes, not activity. Status meetings that report what was done are theatre. Reviews should track the few indicators that tell you whether the decision is actually working.
- Address the implementers’ interests explicitly. If a function stands to lose from a decision, that has to be named and worked through, not assumed away by seniority.
- Close the door on reopening — except through one formal gate. A decision can be revisited if conditions genuinely change, but only through a scheduled review, never through informal foot-dragging by a CXO who quietly disagrees.
The Insight
The teams that get this right treat decisioning and implementation as two different disciplines that happen to be run by the same people, not as one continuous conversation. A good decision and a committed decision are not the same thing — and a CXO team’s job is to manufacture both, deliberately, in that order.
Curious where your own leadership team’s Decision-to-Delivery gap actually lives? Start with a free consultation.
Book your FREE Business Diagnostic today. Limited slots available: ….