Design a Weekly Review That Leads to Action
A weekly review can become an expensive reading of status reports. Each person describes what happened, the group acknowledges it, and the meeting ends with roughly the same priorities it began with. Activity is visible, but judgment is postponed.
A useful review has a different purpose: notice what changed, identify where a decision is required, and protect the next action most likely to improve the result. It is a control point for the work, not a ceremony for proving that everyone was busy.
Prepare asynchronously
Ask each owner to update four fields before the review: outcome moved, evidence learned, blockage requiring help, and next commitment. Limit each field to a few lines. The format should be quick enough that people complete it without turning preparation into a second report.
Stable information belongs in the project record. The live review should focus on changes, contradictions, risks, and choices that benefit from shared attention.
Begin with the intended result
Read the result statement from the current brief. Then ask whether new evidence has changed the team’s understanding of the problem or audience. This prevents the plan from becoming the goal simply because tasks have already been scheduled.
If the result has changed, update the two-column brief explicitly. Do not let the team quietly work toward a new destination while stakeholders continue to judge the old one.
Review movement, not volume
Look at work in four states: completed and verified, active, blocked, and next. A long completed list is less important than the movement of the few items that unlock learning or delivery. Ask what became possible this week that was not possible last week.
Separate waiting from blocked. Waiting on an agreed external event may be healthy. Blocked work requires a decision, missing input, or intervention. Combining the two hides avoidable delay.
Make uncertainty discussable
Invite each owner to name one uncertainty, even when the work appears on track. This can be a weak assumption, ambiguous feedback, dependency, or concern about the selected approach. Early uncertainty is cheap to explore; hidden uncertainty returns later as rework.
The review leader should reward precision rather than confidence theatre. “We do not yet know whether the service team can support this step” is more useful than a green status with no evidence.
Turn problems into decisions
When a blockage appears, state the decision required, the owner, the options, and the latest responsible date. If the decision can be made in the room with the available evidence, make it. If not, define exactly what must be learned.
Use the framing process from Write the Decision Down Before the Meeting Begins for issues that need a separate session. Do not leave them as vague actions such as “align with leadership”.
Choose the next commitment deliberately
End each workstream with one commitment that advances the result or reduces important uncertainty. Name the owner and review point. Smaller supporting tasks can remain in the team’s system, but the shared review should protect the action that matters most.
Check capacity before accepting commitments. A review that adds priorities without removing or sequencing work creates the appearance of urgency and the reality of fragmentation.
Close loops from previous weeks
Revisit decisions, risks, and actions that reached their review date. Confirm whether the expected consequence occurred. If a decision remains valid, close the item. If the trigger for reconsideration has been reached, reopen it with the new evidence.
Record important outcomes in the decision log. Weekly notes are chronological; a decision log is organised for future retrieval.
Keep the rhythm humane
Use a consistent day, time box, and sequence. Cancel when there are no meaningful changes or decisions. Invite only people who contribute evidence, own a choice, or depend on the outcome. Others can read the concise summary.
A good weekly review makes the following week quieter. People know which result matters, which uncertainty is being explored, and where help is expected. The meeting earns its place by reducing ambiguity after it ends.
