A Weekly Business Review Agenda Runs on Exceptions
A weekly business review built as a round of reports uses its hour on what the team could have read. The agenda that works is built from exceptions, ordered by the cost of waiting, with one decision given protected time.
A weekly review fails when it is built as a round of reports.
Ask a leadership team what its weekly business review is for and the answer is usually a description of its format. Each function reports in turn, the numbers go on a screen, someone asks a question, and the hour ends. The format is familiar enough that nobody asks whether it produces anything the team could not have had from a shared document.
The round of reports
A typical version gives each of eight leaders a standing slot of seven or eight minutes. The first six slots consume the hour. The one issue that needs two functions to agree, say a change to a payment step that risk and product read differently, arrives in the seventh slot and is carried into the following week, where the same thing happens again. The agenda is organised by who sits in the room, and the decisions have to find a place inside that structure.
The structure also teaches the room how to behave. A leader who knows a slot is coming prepares a summary rather than a request. Good news fills the time without effort, and a problem, which takes longer to describe, is softened to fit the slot it is given. The review becomes a place where status is performed.
The agenda belongs to the exceptions, and the numbers are read beforehand.
A weekly review earns its hour by dealing with what has moved away from plan, and with nothing else. What is on plan needs no discussion, and what can be read needs no one to read it aloud. That gives the agenda a different source: it is assembled from exceptions collected before the meeting, not from the organisation chart.
The pre-read replaces the read-out
A single page goes out the evening before. It carries the few numbers the team has agreed to watch, each set against its plan, and a line from each owner on anything that is off. Attendees read it before they arrive, and the meeting does not present it. Whatever can be understood by reading is taken out of the room, which leaves the room with what needs people talking to one another.
What qualifies as an exception
Not every deviation earns airtime. Three kinds do:
- A commitment from last week that did not land, named by its owner, with the new date and the reason it moved.
- A dependency between two functions that will slip unless someone outside the owning team acts this week.
- A decision that only this group can take, and that costs more with every week it waits.
Everything else is a line on the page. A metric that is off plan but already has an owner and a recovery date is information, not an agenda item, and the room hears about it only if the date is missed. The wider case for narrowing the weekly in this way is made in the note on setting up a weekly rhythm.
The order of the hour follows the cost of delay.
Once the agenda is reduced to exceptions, the order matters more than the topics. The sequence that holds up in the teams we see puts the quick, factual items first and gives the hardest decision protected time, instead of whatever is left after the others have run over. Dependencies come before the decision because they are short and each day of delay is paid by a team outside the room.
A sixty-minute shape
The minutes below suit one hour with around eight people. A longer slot adds time to the decision and leaves the other segments alone.
- Commitments, ten minutes. Last week's commitments are read as kept or not kept. There is no explanation unless the miss moves another team.
- Dependencies, fifteen minutes. Each cross-function item gets a yes, a no, or a named person and a date.
- One decision, twenty-five minutes. The item with the highest cost of waiting, prepared in advance and run in the order described in the note on decision meeting structure.
- Close, ten minutes. Decisions are read back, owners and dates confirmed, and exceptions for the following week requested.
Why one decision and not three
Most weekly reviews try to settle several decisions in an hour and settle none, because each is given a quarter of the time it needs. One decision with protected time is finished more often than three with fifteen minutes each. The queue behind it stays visible on the page, which makes the choice for the next week easy and removes the feeling that anything has been dropped.
A short agenda holds only if something decides what is left off.
The pressure on a short agenda is constant. Each function has something it wants the team to hear, and a leader who is not on the agenda treats it as a slight.
A short agenda is only as good as the rule for what is left off.
The rule has to be applied by someone other than the person it displeases, and in practice that is the facilitator, working from the three tests above.
Parking with a date
An item that does not qualify is not refused. It is parked with a date, either on the page for the following week or in a smaller forum that already exists, and the owner is told where it went. The cost is low. The benefit is that the review stays about exceptions and does not become the place where everything waits for airtime.
The facilitator's three refusals
The facilitator holds three lines: no read-outs of material already on the page, no positions stated during the dependencies segment, and no new decision opened after the fiftieth minute. Each protects one segment of the hour. They feel abrupt in the first month and ordinary by the third, once the team sees that the hour ends with something decided.
How the weekly sits among the other forums is a separate question. It has the narrowest remit, and trends and strategy belong to rooms with a longer view, as the weekly, monthly and quarterly tiers are laid out elsewhere.
Where this thinking becomes work.
The first piece of work is an audit of the agenda the team runs now. Take the last six weekly reviews and mark every item as a read-out, an exception or a decision. The share of the hour that belonged to read-outs is usually larger than the team expected, and it is the figure that makes the case for the change. The next steps are to write the pre-read page, agree the three exception tests, and run the new order for four weeks before judging it.
Our consulting practice builds the pre-read and the segment order with the leadership team inside the operating cadence pillar, and our training programmes cover the facilitation habits that keep the hour intact. A weekly review is working when the team leaves knowing what changed, who owns it and by when.
Continue