Back to articles

Strategy & Execution

Status reports tell you a story. They rarely tell you the truth.

Most strategies do not fail in the boardroom. They fail in the gap between what was decided and what teams actually do, and that gap stays invisible until the post-mortem.

Halison TeamJune 3, 20266 min read
Charts and analytics on a screen

Every quarter, leaders are asked the same question: are we on track? And every quarter, the honest answer is some version of we think so.

Strategy is not usually the weak link. Execution is. The research on this is unusually consistent across two decades, and it points in one direction.

The numbers are brutal, and consistent

Roughly 67% of well-formulated strategies fail because of poor execution rather than poor design.[1] Kaplan and Norton, who created the Balanced Scorecard, estimated that as many as 90% of strategies are never executed successfully at all.[1] Different studies land between 40% and 80%, but the theme never changes: the plan was fine, the doing was not.[3]

It shows up in project data too. Recent PMI research found that only about half of projects today meet a modern definition of success, with 13% failing outright and a further 37% only partially delivering what was expected.[2]

The cost is not abstract

Organizations with weak execution lose close to 40% of their strategy's potential value, simply leaking it through misalignment and drift.[3] The flip side is just as stark: teams that close the execution gap are meaningfully more likely to report above-average growth and profitability.[3] The difference between the two is rarely talent. It is visibility.

Why status reports cannot catch it

Alignment meetings produce opinions and slide decks, not data. Everyone interprets progress differently, and decisions end up resting on confidence in whoever is presenting rather than on the quality of the underlying work. By the time a strategy review catches misalignment, months of effort have already gone the wrong way, and you find it in the post-mortem instead of the planning cycle.

Measure the work, not the wording

The alternative is to stop asking people to self-report and start reading the work itself. The execution tools your teams already use, the issue trackers, the code repositories, the pipelines, are a record of what is actually being built. Scored against your stated objectives, they answer are we on track with evidence rather than optimism.

  • Evidence over assertion. Tie each objective to observable activity, not a self-reported percentage.
  • Confidence, stated honestly. A score is only as good as the data behind it; surface how much to trust each one.
  • Drift caught early. The point is to see misalignment in week two, not quarter three.

The reframe

Strategy without execution evidence is a wish list. Closing the gap does not require a better plan or a louder meeting. It requires connecting the decision to the work, so the next time someone asks are we on track, the answer is a report instead of a gut feeling.

The short version

The failure rate of strategy is well documented and it is overwhelmingly an execution problem, not an idea problem. Status meetings measure confidence in the presenter, not alignment of the work. To close the gap, measure execution against intent with evidence from the tools where work actually happens.
Related product
BAS Trustdesk

For leaders who need more than a status update. Strategy scored against the work.

See BAS Trustdesk

When we ship, you'll hear it first.

No productivity tips. No engagement drip. Product news when there is something to answer for.

No spam. Unsubscribe anytime.