A Strategy Review Cadence: Monthly Check-Ins and Quarterly Resets

A strategic plan can be well written and still fail if nobody looks at it again until next year, by which point the market, the team and the numbers have all moved.

A review cadence fixes that. It is a fixed rhythm of short meetings, each with a clear purpose, that keeps your priorities connected to what is actually happening. For a small business, the whole system can take a few hours a month.

This guide describes a four-layer rhythm, gives an agenda for the monthly check-in and the quarterly reset, and borrows a compact set of review questions from wildland fire response.

Why plans need a rhythm

Lean management calls this the plan-do-check-act cycle. The Lean Enterprise Institute describes PDCA as an improvement cycle based on the scientific method: propose a change, implement it, measure the results and take appropriate action. In the "act" stage, a team either standardizes what worked or begins the cycle again.

A strategic plan is the "plan." Daily work is the "do." Without scheduled reviews, there is no "check" and no "act," and the plan becomes a document instead of a management tool.

The four layers

Each layer has a different job. Keep them separate so no single meeting tries to do everything.

1. Weekly (10 to 15 minutes, inside an existing team meeting): status of each quarterly priority and anything blocking it. No problem-solving beyond assigning who will handle a blocker.
2. Monthly (45 to 60 minutes): numbers, priority progress and decisions. This is where you adjust approach, shift resources or escalate.
3. Quarterly (half a day): grade the quarter, learn from it and choose next quarter's priorities.
4. Annually (one or two sessions): revisit the challenge, the direction and the one-page plan itself.

Google's re:Work guide to objectives and key results describes a similar layering at a larger scale: goals set annually and quarterly, a company-wide meeting each quarter to review results and set new goals, and a mid-quarter check-in at every level before final grading. The Kanban Guide (May 2025) likewise notes that teams commonly review active work "regularly," whether continuously, at intervals, or both.

The monthly check-in

The monthly session is the workhorse. A simple agenda:

1. Numbers first (10 minutes). Revenue, margin, cash and the few measures tied to your priorities. Prepare them before the meeting so time is spent discussing, not compiling.
2. Priority status (20 minutes). Each owner reports: on track, at risk or off track; what changed since last month; what they need.
3. Decisions (15 minutes). For anything at risk: keep going, change the approach, add help, or drop it. Write each decision down with an owner.
4. Look ahead (5 minutes). Anything coming in the next month that could affect priorities, such as a seasonal rush, a hire or a big customer renewal.

End by reading back the decisions. If the meeting produced none, ask whether you are really reviewing strategy or just sharing updates.

The quarterly reset

The quarterly session looks back and forward.

Start by scoring each priority. A simple scale works: done, partly done, not done. If you use OKRs, the re:Work guide describes grading key results from 0.0 to 1.0 and treating an average of about 0.6 to 0.7 as the "sweet spot" for ambitious stretch goals. The OKR site What Matters adds that committed goals, unlike aspirational ones, are expected to earn a passing grade, so judge each priority against the kind of goal it was meant to be.

Then run a short after-action review on the quarter as a whole, using the questions in the next section.

Finally, choose next quarter's priorities from the annual plan, update the not-doing list, and confirm the dates for the next three monthly check-ins.

Borrow the after-action review

Wildland firefighters use a compact review format after operations. The National Wildfire Coordinating Group's Incident Response Pocket Guide (PMS 461, January 2025) lists four questions:

• What was planned?
• What actually happened?
• Why did it happen?
• What can we do next time?

The guide adds that the next-time question is about correcting weaknesses and sustaining strengths. Its guidance on the meeting itself translates well to a business setting: perform the review as soon after the event as possible with the people involved, "Keep focused on the what, not the who," "Make sure everyone participates," and end on a positive note. It also stresses that respectful disagreement is okay.

These questions work for a whole quarter, a single priority that slipped, or a project that went unexpectedly well. Their value is in separating what happened from why, before anyone jumps to fixes.

Keep the records short

Long minutes rarely get read. For each review, keep:

• The scorecard: each priority's status and measure.
• A decision log: date, decision, owner, due date.
• For quarterly reviews only, three to five lessons from the after-action questions.

Store them in one place alongside your one-page plan. At the annual planning session, those logs become your look-back, already written.

A hypothetical example

Imagine a seven-person IT support company with three quarterly priorities. At the monthly check-in in its second month, the owner of the "cut response time" priority reports it is at risk because a technician is out. The team decides to pause the second priority for two weeks and lend that time to the first. The decision goes into the log. At the quarterly reset, the after-action review shows response time improved but the paused priority slipped; the team carries it into the next quarter and agrees to plan for absences when choosing priorities.

Nothing about that is complicated. The value comes from the decisions being made on schedule, written down and revisited.

Key takeaways

• Scheduled reviews supply the "check" and "act" that turn a plan into a management tool.
• Use four layers with distinct jobs: weekly status, monthly decisions, quarterly reset, annual direction.
• Put numbers first and end every monthly check-in with recorded decisions.
• Use the four after-action questions to learn from each quarter, focused on what happened rather than who.
• Keep a short scorecard and decision log; they become next year's look-back.

Sources

• Lean Enterprise Institute, Lexicon: Plan, Do, Check, Act (PDCA)
• National Wildfire Coordinating Group, Incident Response Pocket Guide, PMS 461 (January 2025)
• Google re:Work, Set goals with OKRs (originally published 2016)
• What Matters, What is an OKR? OKR Meaning, Definition & Examples
• John Coleman and Daniel Vacanti, The Kanban Guide (May 2025)