The weekly numbers meeting in 15 minutes
Most of a results meeting is people reading numbers out loud and arguing about which spreadsheet is right. How to cut that and spend the time on what only humans do: decide.
Time your next results meeting and split it into three buckets: building the number, reading the number out loud, and deciding what to do. In most companies the third bucket is the smallest — and it is the only one that requires people in the same room.
A long results meeting is almost never a sign of a complex subject. It is a sign the number was not ready when the meeting started.
The three wastes
- Assembly: someone spent hours consolidating a spreadsheet the day before. That work never shows up in the minutes, and it is the most expensive part.
- Reading: half the meeting is people saying out loud what is written on the slide. That is an email.
- Version fights: two different numbers for the same thing turn the discussion into a debate about the source, not the decision.
The 15-minute format
- 01The results page exists before the meeting and reads the base live. Nobody assembles anything — whoever opens it sees the number now.
- 02Everyone reads it alone first. Five minutes of asynchronous reading replaces twenty of reading aloud.
- 03The meeting starts with what fell outside the expected range. What is normal is not reviewed.
- 04Any doubt that comes up is resolved right there by asking the assistant. The point does not become next week homework.
- 05It ends with a decision and an owner. Only that goes into the minutes.
Step 4 is what shortens the meeting most in practice. The classic open item — "nobody knows why that number dropped, someone look into it and bring it next week" — is what makes the meeting repeat. When checking costs seconds, it happens live and the topic dies there.
What the results page needs
| Element | Why | Common mistake |
|---|---|---|
| Comparison next to the number | A number alone does not say whether it is good or bad | Showing only the period value |
| Expected range | Defines what deserves discussion | Letting everyone judge by intuition |
| Data freshness | A lagging source disappears from the radar | Not saying how far the data goes |
| Breakdown by owner | A decision needs someone responsible | Only company-level aggregates |
If a meeting can be replaced by a document, it should be. What remains is short on purpose — and worth gathering people for.