Most organisations have a rhythm for reviewing strategy. Quarterly reviews. Annual planning sessions. Executive off-sites. Steering committee meetings. On paper, these are important moments. They provide an opportunity to assess progress, challenge assumptions, and adjust course. Yet, across many organisations, remarkably little changes after the meeting ends.

The presentation is delivered. Progress is discussed. Risks are acknowledged. Actions are noted. Then everyone returns to business as usual. Across our work with leadership teams, we’ve found that strategy reviews rarely fail because the discussion is poor. They frequently fail because the purpose of the review is misunderstood.

Too often, strategy reviews become reporting exercises rather than decision-making forums. This distinction matters. Reporting looks backwards. It explains what has happened. Strategy reviews should look forwards. They should determine what needs to happen next.

When this distinction is blurred, leadership teams spend their time reviewing information rather than making decisions that change outcomes. Several patterns appear repeatedly:

  • progress updates dominate the agenda, leaving little time to discuss the strategic implications of what has been presented.
  • issues are identified but not resolved because decisions are deferred to future meetings.
  • underperforming initiatives continue without challenge because stopping them feels more difficult than continuing them.
  • new priorities are introduced without removing existing ones, increasing organisational complexity rather than reducing it.
  • success is measured by whether initiatives are “on track” rather than whether they are still strategically relevant.

None of these practices are intentional. They emerge because strategy reviews gradually evolve into governance routines instead of leadership conversations.

The highest-performing leadership teams approach strategy reviews differently. They begin with a simple assumption: every strategy review should result in decisions. Those decisions may include reallocating resources, accelerating delivery, pausing initiatives, changing priorities, or revisiting strategic assumptions. Sometimes the right decision is to stay the course. But that, too, should be an active decision rather than the default outcome of an uneventful meeting.

These leadership teams also spend less time reviewing every initiative in detail. Instead, they focus on the handful of questions most likely to improve execution:

  • what has changed in our internal or external environment since the last review?
  • which strategic assumptions are proving to be incorrect?
  • where are we losing momentum, and why?
  • what should we stop, start, or change before the next review?
  • which decisions cannot wait until the next reporting cycle?

Notice that none of these questions ask for more information. They ask leaders to exercise judgement. This is the real purpose of a strategy review.

A useful strategy review should create movement. People should leave the room with greater clarity than when they entered. Priorities should be sharper. Decisions should be clearer. Resources should be better aligned. If nothing changes after the review, it is worth asking whether the organisation held a strategy review at all, or simply reviewed its strategy. There is an important difference.

The most effective organisations recognise that strategy is not something reviewed every quarter. It is something actively managed between reviews. The review itself is simply an opportunity to make better decisions based on what has been learned.

Strategy succeeds because leadership teams are willing to adapt. The organisations that create lasting momentum are not those with the most comprehensive review processes. They are the ones that consistently turn insight into action.