Most weekly operations meetings start with good intentions and drift towards an hour. Everyone reports what they did, a problem is discussed without the person who could solve it, and the meeting ends with a feeling that something was agreed, though nobody could say what.
This article is for a head of operations or a managing director who wants a short, repeatable weekly meeting. It describes the format: the agenda, the time boxes, who prepares what, and how the meeting ends. It is not about which metrics to track; for that, see a one-page monthly operations review with five numbers.
What the meeting is for
A weekly meeting has one job: to find out what needs a decision or a joint effort this week, and to assign it. Status updates can be read. Long analysis can be done by two people afterwards. If an item does not need several people in the same room, it does not belong here.
Keep the group small. Those who own the main areas (for example sales handover, delivery, support and finance) are enough. Others read the note afterwards.
The fixed agenda
The same four blocks every week, with the time written next to them.
| Block | Time | Purpose |
|---|---|---|
| 1. Three numbers | 4 min | See what changed since last week |
| 2. Problems | 7 min | Pick the one or two that need joint effort |
| 3. Decisions | 6 min | Decide what was prepared in advance |
| 4. Closing note | 3 min | Read back owners and dates |
The time boxes are not strict rules; they are a way to notice when you are drifting. The chair says "we are at ten minutes, still on problems" and the group decides what to cut.
1. Three numbers (4 minutes)
Show three numbers on one screen, each with last week's value beside it. Do not explain them in detail. Ask only: "Is anything here unexpected?" If not, move on in a minute. If yes, note it and put it under problems.
Which three numbers is your choice and can change over time. Use ones that someone in the room can influence within a week, such as open requests older than five days, orders delayed, or unanswered customer messages. Avoid numbers that move only once a quarter. If you need ideas for how to show them, the operations dashboard is one example.
2. Problems (7 minutes)
Each owner brings at most one problem, written as one sentence in the shared document before the meeting. The chair picks one or two. For each, the group answers three questions: what is the effect, who can solve it, and what do they need from the others. Discussion of causes in depth is moved out of the meeting to the people involved.
3. Decisions (6 minutes)
These are items prepared in advance, with the options and a recommendation written down. The meeting chooses; it does not design. If a decision arrives without preparation, the owner prepares it for next week or for a short separate call. This keeps the meeting from turning into a workshop.
4. Closing note (3 minutes)
The chair reads back each action: what, who, by when. Anything without an owner and a date is either dropped or given one now. Nothing is left as "we should". If meeting notes are taken with an AI tool, check consent, accuracy and retention first.
Who prepares what
- The chair (usually the head of operations) keeps the time, picks the problems, and sends the note on the same day.
- Each owner writes one line for the problem list and updates their number by the evening before.
- One person keeps the shared document and the three numbers. Rotate the role every few weeks so it does not become one person's chore.
Preparation should take each owner about ten minutes. If it takes longer, the numbers are probably too hard to collect and should be replaced.
The closing note
Send it within the same day, in a form that fits in a mail without scrolling:
- Three numbers with last week's values
- Problems discussed and the agreed next step for each
- Decisions made
- Actions: what, owner, date
Start the next meeting by looking at last week's actions only if they are overdue. Done items need no applause and no time.
When the meeting runs over
Do not extend the time. Remove or shorten something instead:
- Drop the problem block to one item.
- Move prepared decisions to a short separate call.
- Cut the number block to a single question: "what surprised you?"
If the meeting runs over several weeks in a row, the group is usually too large or the problems are not being prepared. Fix those two things first.
Common mistakes
- Round-the-table updates. They take most of the time and rarely lead to action.
- No time boxes written down. Without them, nobody notices the drift.
- Problems without the person who can solve them. The discussion repeats next week.
- Notes sent days later. By then, the actions are already forgotten.
- Changing the format every month. A stable agenda is the main benefit.
Checklist
- Set a fixed time, 20 minutes, with the same four blocks
- Choose three numbers that can move within a week
- Ask each owner for one written problem line before the meeting
- Prepare decisions with options and a recommendation
- Read back every action with an owner and a date
- Send the note the same day
- Review the format after a month and remove, not add
Sources
- Our related article linked above.
- The agenda and time boxes are a working practice, not a standard; adjust them to your team. No client results or market figures are claimed in this article.
