The one-page review structure
Open with the outcome metrics and a short statement of what changed. Then review the few drivers that explain the movement, current customer or operational exceptions, previous commitments, and decisions required. Keep background material in an appendix.
Use consistent comparisons: target, prior week, rolling trend, and a relevant cohort or segment. Mark data quality issues rather than discussing uncertain numbers as facts.
- Outcome and guardrail scorecard
- Driver commentary: what changed and why
- Customer, quality, delivery, or risk exceptions
- Previous actions: done, delayed, or disproven
- Decisions, new owners, and due dates
Write commentary that supports a decision
Good commentary distinguishes observation, explanation, and action. “Conversion fell 1.2 points” is an observation. “Mobile payment failures explain half the decline” is a claim requiring evidence. “Payments owner will isolate affected methods by Wednesday” is an accountable action.
Avoid adjectives such as strong or weak without a threshold. Quantify materiality and state confidence in the proposed driver.
Run the meeting by exception
Distribute the scorecard before the meeting and expect owners to correct definitions or data issues in advance. Spend live time on material deviations, cross-functional dependencies, decisions, and risks. Stable metrics need acknowledgment, not a presentation.
Keep a decision and commitment log. Repeatedly carrying the same action without escalation is a governance failure, not an update.
Maintain the review system
Audit the meeting monthly. Remove metrics that never trigger action, add missing guardrails, and confirm that owners still control the relevant levers. Track whether decisions produce the expected movement.
The purpose of a weekly review is not reporting completeness. It is faster detection, clearer explanation, and reliable follow-through.