The Power of Weekly Business Reviews (Most Don't Do This)

The weekly review that works is the one that produces decisions, not the one that produces information. The difference is format. A review meeting where five team leads each present their department's metrics for 10 minutes produces 50 minutes of data presentation and 10 minutes of decision discussion. A review meeting that starts with a pre-distributed data summary that everyone has read before the meeting, and that uses the 60 minutes entirely on the three to five decisions the data reveals are needed, produces 60 minutes of decision discussion and five minutes of summary at the end.The pre-distributed data summary is the key enabling condition. It requires the data infrastructure described in the data architecture article the connected dashboard that assembles each dimension's metrics automatically before the meeting rather than requiring each team lead to compile and present their data. When the data is available to every participant before the meeting begins, the meeting itself can focus entirely on interpretation and action rather than on presentation. The weekly review then becomes what it should be: a structured decision-making session rather than a reporting ceremony.

• Each weekly review should end with exactly three to five named actions not a list of observations or concerns, but specific actions with a named owner and a completion date before the next weekly review
• The opening question of every weekly review should be: 'What happened since last week's review that we did not anticipate?' this question surfaces the unexpected developments that the standard metrics may not have flagged but that team members have noticed in daily operations
• Track the completion rate of weekly review actions: the proportion of actions from the prior week that were completed before the current week's review a completion rate below 70% indicates that action items are not being scoped correctly or that the owner does not have the capacity or authority to complete them
• Keep the review at 60 minutes maximum a review that regularly runs over 90 minutes has too many dimensions being reviewed or is not operating from pre-read data; both are fixable structural problems, not reasons to extend the meeting time indefinitely
• The founder attends every weekly review without exception for the first six months of implementing this cadence the signal of consistent attendance builds the cultural habit; irregular attendance signals that the review is optional, which it is not