How to Run a Monthly Business Review That Generates Decisions
Most monthly business reviews produce summaries, not decisions. Here is a structure that turns your MBR into the most action-generating meeting of the month.
The monthly business review is the single most important meeting in most small and growing companies. It is the one moment each month when the whole leadership team looks at the same numbers at the same time and — in theory — makes the decisions that will shape the next thirty days. In practice, most MBRs are elaborate ceremonies of reporting: one person presents, others nod, everyone leaves with a summary but without a decision.
The fix is structural. A meeting that generates decisions needs to be designed to generate decisions — which means most of the reporting happens before the meeting, and the meeting itself is almost entirely discussion and resolution. Here is the structure that makes that happen.
The pre-read rule: no numbers in the meeting for the first time
The single highest-leverage change you can make to your MBR is requiring that all data be shared at least twenty-four hours before the meeting. Every metric, every slide, every chart — circulated in advance. The meeting itself then starts with the assumption that everyone has seen the numbers. No presenting. No walking through slides. Discussion only.
This rule feels uncomfortable at first because it disrupts the performance aspect of the MBR — the CFO presenting revenue, the head of sales presenting pipeline, the product lead presenting engagement. That performance is precisely what makes most MBRs useless. Presenting data takes time and produces passive listeners. Discussing pre-read data takes the same time and produces active decision-makers.
A meeting that generates decisions needs to be designed to generate decisions. Most of the reporting should happen before the room convenes — the meeting itself should be almost entirely discussion and resolution.
The agenda that works
The "decisions needed" section is the most important part
Most MBRs spend 80% of their time on sections 1 and 2 and skip sections 3, 4, and 5 when they run over. This is exactly backwards. The financial snapshot and metrics review are context — they tell you what happened. The decisions needed section is where the meeting earns its place in the calendar.
The decisions section works only if it is pre-populated. Decisions that surface for the first time in the meeting rarely get resolved in the meeting — there is not enough context shared, not enough time, and the right people may not be prepared. Require that anyone who wants a decision made in the MBR submits the decision, its context, and their recommendation with the pre-read. The meeting then moves quickly through each one because everyone arrived with enough context to engage.
Section 3 is the most frequently skipped in practice, and it is where some of the highest-value discussions happen. The discipline of sharing one genuine learning — not a summary, not a win, but a specific insight that changed how someone thinks — builds the organizational muscle for learning from failure as well as success. Over twelve months of consistent MBRs, the "what we learned" record becomes one of the most valuable institutional knowledge assets a growing company has.
What to do about decisions that do not get resolved
Some decisions are bigger than ninety minutes. If a decision requires more analysis, more stakeholder input, or a longer discussion than the time-box allows, park it — explicitly, with a named owner and a deadline for async resolution — and move on. The failure mode is to keep discussing past the time-box and let the whole meeting run over, which produces a rushed and unsatisfying end to sections 4 and 5.
The willingness to park a decision and resolve it async is a sign of meeting discipline, not indecision. Not every decision belongs in the MBR. Some belong in a dedicated working session with the right subset of people. The MBR is for decisions that require the whole leadership team's alignment — not for every decision the leadership team is tangentially involved in.
The most common way MBRs degrade over time is that the "decisions needed" section shrinks as teams get more comfortable with async communication and start reserving the MBR for reporting. This is a slow death for a useful meeting. Every quarter, audit your MBR: count the decisions made in the last three meetings. If the average is below two per meeting, the MBR has become a status update and needs a reset — either in format, in who attends, or in whether it should continue at all.
In FabricLoop, MBR-driven teams typically maintain a recurring monthly note in their leadership group — the pre-read document that consolidates all the data before the meeting, and the running record of decisions made afterward. Tasks created in the "decisions needed" section are assigned directly from the note, so the owner and deadline are captured in the moment of resolution rather than reconstructed from memory afterward. The "what we learned" entries accumulate in the note over time, building an institutional knowledge base that new leadership team members can read to understand how the company's thinking has evolved.