strategyplaybook.aiSqwyz
Sign in
← All 124 tools
Monitor · Plan, Review

Strategy review cadence

Designs who looks at what, how often, and what they can change without escalating. Most businesses have plenty of meetings and no cadence, which is not the same thing.

The printable canvas and the handoff into Claude Code are part of a paid plan. See what a plan includes. It needs the Claude desktop app on this machine, and your team and the prompt library already installed in that project — we cannot see your disk, so open it there.

Stage
04 Plan, 05 Review
Works at
Corporate, Business
Maturity
Scaling → Large organisation
Time
Half a day

What it is

The designed rhythm by which a strategy is reviewed: which forums exist, what each looks at, how often, and what each may decide. Distinct from a meeting schedule, which most organisations have instead.

Monthly — delivery
Are the moves progressing? Operational, corrective, focused on execution against plan.
Quarterly — effectiveness
Is the strategy working? Reviews leading indicators, assumption status and whether the moves are producing the intended effect.
Annual — validity
Is this still the right strategy? Revisits the diagnosis itself, which is the review almost nobody actually runs.
Decision rights
What each forum can change without escalating. The element that determines whether a cadence functions or simply reports.
Inputs
What each forum sees. Different horizons need genuinely different information; using the same pack collapses them into one conversation.
What stops
The existing meetings this replaces. Additive governance is how organisations end up reviewing constantly and deciding nothing.
The mistake people makeAdding a strategy review to a business already drowning in forums makes things worse. The design work is as much about abolishing meetings as creating them, and that half is usually skipped.
What it’s forYou need to design who looks at what, how often, and what they can change without escalating.
What it’s not forYou already have a functioning rhythm. Do not add a forum to a business drowning in forums.

How you run it

  1. Inventory what already existsEvery recurring forum, its attendees, its length and what it actually decides. This alone is usually uncomfortable reading.
  2. Separate the three horizons of reviewMonthly reviews delivery, quarterly reviews whether the strategy is working, annually reviews whether it is still the right strategy. Most organisations only do the first and call it strategy.
  3. Define decision rights per forumWhat can this group change without escalating — spend thresholds, scope, sequencing, stopping. Undefined rights mean everything escalates and nothing is decided.
  4. Give each forum different inputsThe quarterly needs leading indicators and assumption status, not the monthly's delivery report. Same pack, same conversation.
  5. Abolish somethingA new cadence added to an existing calendar is more meetings, not better governance. Name what stops.

The prompt

Two ways to run it

Run this tool in your own Claude

The short prompt starts your partner against the library on your disk. The long one carries everything with it and needs nothing installed.

🔒 Prompt locked

Everything above is free — what this tool is, what it is for, what it is not for, and how to run it as a workshop. Three tool prompts a month are free with an account; beyond three, and for the printable canvas, it is the paid part.

See plans — from £19 a month

Your playbook

It lands in the earliest stage this tool suits. Move it on the Playbook page.

You’ll need

  • An honest inventory of existing forums
  • The decisions that actually need making regularly
  • Willingness to abolish something

You’ll end up with

  • A rhythm across monthly, quarterly and annual
  • Decision rights at each forum
  • A list of meetings being stopped

Runs well with

AI operating model optionsAI risk classification and governanceAlliance and partnership designAssumption mapping