The short version
- Ninety minutes of reading updates aloud is a status meeting with a better name. Convert it by making the updates a pre-read.
- Pre-reads fail unless the meeting genuinely does not repeat them. The first time someone summarises their update aloud, the format is gone.
- Agenda rule: only items that are off plan, contested, or need a decision. Everything on plan gets no airtime.
- Forty-five minutes, standing agenda, and cancelled when there is nothing off plan.
The weekly ops review is one of the most valuable slots in a company's week and one of the most commonly wasted. The waste has a signature: each function speaks in turn, most of what is said is on plan, and the decisions get made in the last ten minutes when everyone is tired.
"Ninety minutes of reading updates aloud."
Where the ninety minutes goes
Time a typical session and the split is consistent: roughly two thirds on updates, a fifth on clarifying questions about those updates, and the remainder on actual decisions. With eight attendees that is around eight hours of senior time to produce two or three decisions.
The updates portion is also the least useful way to deliver that information. It is spoken rather than written, so nothing is retrievable afterwards; it is sequential, so nobody can skip the parts that do not concern them; and it is performed, so it is smoother and less honest than the written version would be.
The pre-read, and why it usually fails
The standard fix is to circulate written updates beforehand. It works when two conditions hold and fails when either does not.
People read it. Which requires it to be short, to arrive with enough lead time for every time zone, and to be genuinely necessary because the meeting will not repeat it.
The meeting does not repeat it. This is the one that breaks. Someone asks a lead to "just quickly summarise", the lead does, and everyone learns that reading was optional. Within three weeks the pre-read is unread and the meeting is ninety minutes again.
The chair has to enforce this and it will feel rude twice. After that it is the norm.
The agenda rule
One rule, stated at the top of every agenda: items appear only if they are off plan, contested, or need a decision. Anything on plan gets zero airtime, and saying "nothing from me, it is in the pre-read" is a complete and welcome contribution.
That rule has a side effect worth mentioning. It requires that "on plan" is verifiable without the meeting, which means the state of each commitment has to be readable elsewhere. If the only way to know whether something is on plan is to hear its owner say so, the updates cannot be removed.
This is where the pre-read needs to be answerable rather than merely written. With StandIn, the briefs people confirm at the end of each day are what their StandIn answers from, so a lead preparing for the review can ask where a commitment stands and get an answer sourced to the person doing the work, at whatever hour they are preparing. It never guesses, so an unanswered question is itself a signal worth putting on the agenda.
The pre-read then stops being a document someone has to assemble and becomes something anyone can interrogate before the meeting. See StandIn for leadership teams.
The forty-five minute format
| Minutes | What happens |
|---|---|
| 0 to 5 | Chair lists what is off plan, from the pre-read. No commentary |
| 5 to 35 | The off-plan items, one at a time, each ending in a decision or an owner and a date |
| 35 to 42 | Anything anyone wants to raise that was not on the list |
| 42 to 45 | Chair reads back the decisions and owners. Written into the record |
The last three minutes are the most important and the first to be cut when the meeting overruns. Protect them: a decision that is not read back and recorded will be reopened, as covered in why decisions keep getting revisited.
Common Questions
How do you stop an ops review becoming a status meeting?
Move the status into a pre-read and refuse to repeat it in the room. Limit the agenda to items that are off plan, contested, or need a decision, and cancel the session when there are none.
How long should a weekly ops review be?
Forty-five minutes with eight or fewer people. If it needs ninety, it is either carrying status that should be written or it has too many attendees who are present in case something relevant comes up.
What if people do not read the pre-read?
Usually because the meeting repeats it, so reading has no value. Stop repeating it, twice, and attendance at the pre-read changes within a fortnight. Also check it is short enough and arrives early enough for every time zone.
Who should chair it?
Someone willing to interrupt a senior person who starts summarising their update. The format depends entirely on that enforcement, so the chair's authority matters more than their function.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.