A strategic review meeting should lead to choices about direction and resources. It loses value when it becomes a long recital of completed activities. Organise the discussion around assumptions, outcomes and decisions so leaders can determine what to continue, what to change and what to stop, with clear responsibilities after the meeting.
Separate strategic questions from routine status
An operational review asks whether current work is being delivered as intended. A strategic review also asks whether that work remains the right choice for achieving the organisation’s goals. Both are necessary, but combining every routine update with major decisions can crowd out the latter.
Select issues that could change priorities, resource allocation or a critical assumption. A missed milestone may need operational correction. Repeated evidence that the chosen customer segment is unattractive may require a strategic choice. Explain why each agenda item needs the decision makers in the room.
Build the agenda around decisions
Start with a short list of questions that cannot be resolved within the team’s everyday authority. Frame each item as a decision, such as whether to continue a service pilot or change the intended customer segment. Identify the proposal owner, information needed and suitable discussion time. Establish who has authority to approve the decision. Attendance alone does not confer authority to commit money or resources. Put updates that do not require a choice into advance reading, while allowing questions where needed.
Do not use presentation length as a measure of an initiative’s importance. A short item may need deeper discussion because it affects a long-term commitment or scarce resource. Order items by decision impact and timing, leaving room for questions and alternatives. If essential evidence is missing, explain the gap beforehand and identify whether the meeting needs a provisional decision or an instruction to obtain further analysis.
Agree what the comparison terms mean. One team may use “sales” for signed contract value while another means cash collected. A customer count may include free trials that do not represent paid demand. Clarify each measure’s definition, period and data source so participants do not make decisions from figures that look comparable but measure different things.
Send a short decision brief in advance
For each issue, state the decision required, the evidence, important uncertainty and feasible options. Include the consequence of doing nothing. Give readers enough context to challenge the recommendation without asking them to reconstruct the analysis during the meeting.
Keep activity, output and outcome distinct. Training the service team is an activity; making the service available is an output; repeat purchases are a possible outcome. Another outcome measure is contribution margin: service revenue less its variable costs. This is not net profit, because fixed costs still need to be covered. If results are not yet observable, state what early evidence can and cannot show. Do not describe an initiative as successful merely because its tasks are complete.
Revisit the assumptions behind the plan
An assumption is an estimate used in planning that later evidence may support or disprove. List the assumptions that made the original choice reasonable, such as customer demand, cost, available skills or partner capacity. Compare them with current evidence. Distinguish a weak assumption from poor execution; the remedies differ.
Invite relevant challenge and document uncertainty. One large customer enquiry is not necessarily evidence of a broad market. A short-term downturn may not invalidate a long-term priority. Use multiple relevant signals and identify what further evidence would change the decision.
Make the resource trade-off visible
A decision to add an initiative should state where the money, time and capability will come from. If everything remains a priority, the meeting has probably deferred the real choice. Consider dependencies and the effect on work already promised to customers or other teams.
Distinguish sunk costs, meaning money already spent that cannot be recovered, from future costs and benefits. Past spending alone does not justify continuing an unsuitable initiative. Equally, stopping has transition costs and obligations that need assessment. Evaluate the feasible options from the present decision point.
Test alternatives before accepting the recommendation
Ask the proposal owner why their preferred option is better and what evidence would change their view. Discuss another feasible option and the consequence of keeping the current approach. A complex model is not necessary for every issue. Sometimes a clear account of each option’s commitment, resource needs and potential outcome is sufficient. Participants should see the trade-off rather than approve a recommendation without knowing what it excludes.
When piloting a new service, alternatives may include raising the price, narrowing the scope, changing delivery or stopping the pilot. Each affects customers and the team differently. Check the organisation’s ability to implement the option and the information needed before commitment. If the comparison depends on forecasts, identify them as estimates and discuss how weaker-than-expected results could affect the choice.
Invite affected functions to explain constraints that a financial summary may not show. An apparently low-cost option may require substantial time from a team already committed elsewhere. A marketing decision may add complexity to support or operations. Making these dependencies explicit before approval is preferable to discovering them after the decision has been announced and work has begun.
Use three decisions with explicit conditions
| Decision | What must be recorded |
|---|---|
| Continue | Why the approach remains credible and when it will be reviewed |
| Change | What changes, who owns it and which result will be checked |
| Stop | How commitments will be settled, staff duties reassigned and records retained |
These are a practical discussion structure, not a formal scoring model. A fourth outcome may be a limited evidence-gathering step before a decision. Give that step an owner and deadline so “more analysis” does not become indefinite postponement.
Example: change the test, not the target retrospectively
In a hypothetical example for illustration, a business pilots a new service in 2 customer groups. Enquiries are strong but delivery effort is higher than expected. The review checks whether pricing, scope or the operating method explains the gap. It may narrow the service and run a time-limited second test.
The team records the new scope, maximum number of orders it can deliver and evidence required before expansion. It preserves the original results instead of rewriting the target to make the first test appear successful. The point is to improve the decision, not to protect a presentation.
Distinguish decision quality from a single outcome
A team may make a reasonable decision from the available evidence and then face changed conditions. Review what was known at the time, what emerged later and whether the agreed review conditions were followed. Do not use the outcome alone to rewrite the original reasoning, or use uncertainty as a reason to continue without examination. Preserve key assumptions so the difference between expectations and reality can inform learning.
During follow-up, examine implementation and impact together. Closing an action in a decision log does not establish that a strategic outcome has been achieved. If implementation is complete but the expected effect is absent, determine whether more time, different evidence or a revised choice is needed. The review remains a cycle of learning and decision-making rather than a recurring task-status update.
Turn the meeting into accountable follow-up
Keep a decision log containing the choice, rationale, owner, resources, deadline and next review trigger, such as exceeding the approved cost limit or a material change in demand. Confirm that affected teams understand the consequences. At the next meeting, review whether the decision was implemented and what changed, rather than reopening the same discussion without new evidence.
Set the review frequency to reflect how quickly the business changes and how long results take to emerge. Review earlier when a material trigger occurs, rather than waiting for the scheduled meeting. NIST’s self-assessment guidance supports examining processes and results and aligning resources with objectives. The meeting sequence proposed here is practical guidance, not a formal Baldrige requirement.
Continue an initiative when evidence still supports its rationale and the necessary resources remain available. Change it when its approach needs correction. Stop it when another option offers greater value after accounting for commitments. A meeting is complete when the choice has an implementation owner, resources and a date for reviewing its impact.
Use the strategic planning consultant brief when external support is needed to frame the choices. ATMACSS strategic planning and performance indicators can help connect priorities, measures and a practical review rhythm.