Run a Monthly Business Review That Leads to Action
A monthly review can become a collection of reports that nobody uses. Its purpose should be to make better choices about the next period. Keep the meeting centred on agreed goals, meaningful changes and the actions the team can take, rather than trying to discuss every activity completed during the month.
Prepare a consistent view of the month
Choose a few measures that relate to the work being reviewed, such as completed tasks, unresolved support issues or project milestones. Use the same definitions across periods and explain any change in how the data was collected. Combine numbers with relevant context. A delayed task means something different when an input was unavailable than when the agreed process was not followed.
Discuss exceptions and underlying causes
Ask what changed, why it matters and what evidence supports the explanation. Separate facts from working hypotheses. An illustrative review might show that several design jobs waited for copy approval, suggesting a need to move content review earlier. Do not assume that a visible increase or decrease proves the cause; identify what further information would confirm the explanation.
Choose a manageable set of next steps
Agree which practices to continue, which problems to address and which questions need investigation. Give each action an owner, a due date and a way to judge completion. Review the previous month’s actions before adding new ones. If the team cannot act on the list with its available capacity, reduce the list rather than carrying an unrealistic plan forward.
- Use measures tied to the agreed goals.
- Explain unusual results and changes in data definitions.
- Distinguish evidence from assumptions about causes.
- Record a small set of owned actions for the next month.
Take it into your working day
A useful monthly review ends with clear decisions and follow-through, not simply a more polished account of what happened.