How to run a weekly review in a small company without a meeting
Somewhere around the sixth or seventh person, a small company grows a weekly meeting. Nobody decides to. It arrives because two or three things fell through the week before and a meeting is the obvious shape for making sure they do not fall through again.
A year later it is still on the calendar, it takes an hour, and the honest summary of it is that four people said something useful and the other six waited.
What the weekly meeting was actually for
Before replacing it, it is worth being precise about what it produced, because most of the arguments about meetings are arguments between people who want different things out of the same hour.
A weekly review, stripped of ceremony, produces four things. It surfaces what somebody promised last week and has not delivered. It surfaces what is stuck and who it is stuck on. It puts the next few days’ dates in front of the people who have to plan around them. And it reminds everyone what the quarter is supposed to be about, so that this week’s work can be checked against it.
That is the whole product. Everything else in the hour is either social, which is fine but should be honest about being social, or it is one person’s status update being read aloud to nine people who did not need it.
The cost of an hour in a ten-person company
Ten people for one hour is ten hours. That is more than a day of the company’s week, and it is the expensive part of the week, because it is scheduled into the middle of the day and takes the edges off the two hours on either side of it.
Against that, count what the hour returns. If the meeting surfaces two things that would otherwise have been missed, and each of those would have cost half a day to unwind later, the meeting broke even. Some weeks it does. Most weeks, in a company small enough that everyone already sees most of what is happening, it does not.
The failure mode is not that the meeting is useless. It is that the meeting is the only place the four things above happen, so cancelling it removes the review as well as the hour. The fix is to separate them: keep the review, drop the room.
The four things worth looking at
A weekly review without a meeting is a short list of questions, asked by each person, about their own work.
What did I say I would do last week that is not done? Not “what is still open” but specifically what somebody else heard me promise. Those are the items with a second person’s plans attached to them, and they are the ones worth naming first.
What is stuck, and who is it stuck on? A todo that has not moved in seven days is either not actually a priority, in which case say so and move the date, or it is waiting on somebody. Waiting on somebody is a message, not a status.
What is due in the next week? This is the forward-looking question, and it is the one the calendar answers: deadlines laid out by due date, so that a week that is quietly overloaded looks overloaded before it starts rather than on Thursday afternoon.
Where are the quarterly goals? The company has a small number of things it said this quarter was for. Every week, once, look at this week’s work next to them and notice whether the two are related. Usually they are. When they are not, that is the most useful thing the review will tell you all week.
Each person does it, in the same order
The reason this works without a meeting is that the four questions are answerable alone. Nobody needs a room to know which of their own promises are outstanding.
The order matters more than the timing. Promises first, because they are other people’s plans. Then stuck items, because those need a message today rather than a note. Then next week’s dates. Then the goals, which are the only part that is allowed to change your mind about the first three.
Fifteen minutes is enough. It works best at a fixed point in the week, because a review whose time floats is a review that stops happening in the third busy week.
A chief of staff can draft this rather than leave you to assemble it: it has read the week’s messages, it can follow up your todos and their deadlines, and it can put the four answers in front of you so the fifteen minutes is spent deciding rather than collecting. What it should not do is decide anything. Whether a slipping date matters, whether the stuck item needs a nudge or a different plan, whether this week was on the quarter or off it: those are judgements about people, and they belong to the person who has to live with them.
Write the conclusions back
A review that ends in a document is a review you will not read again. A review that ends in changed todos is a review that changed the week.
So the last step is mechanical. Every date that turned out to be wrong gets moved on the item itself, now, while you are looking at it. Every stuck item gets one message to the person it is stuck on, sent today. Every promise you are not going to keep gets said out loud to the person you made it to, which is unpleasant for a minute and much less unpleasant than the alternative. And anything you noticed about the quarter goes to whoever manages the goals.
None of that needs a meeting. All of it needs somebody to actually do it in the twenty minutes after the review rather than the following Tuesday.
When you should still call a meeting
The argument here is against the standing weekly meeting, not against meetings.
Call one when a decision needs several people to change their minds in the same conversation. Written threads are good at conveying positions and bad at changing them; a decision where two people disagree and both are reasonable is worth a room.
Call one when something is genuinely wrong and the company needs to hear it from a person rather than read it. Call one when you are planning the next quarter, because that is a conversation, not a status check.
Do not call one to find out what happened. That question has a better answer now, and it does not cost ten hours.
Where Opitor fits
Opitor is an AI-native operating system for small companies, where every person gets their own AI chief of staff. The four questions above have somewhere to live in one product: messages, direct and group; a Todo List with deadlines, which the calendar lays out by due date; and the company’s quarterly goals, managed by administrators. Each person’s chief of staff reads along, follows up their todos and deadlines and drafts the messages the review turns up, and then it stops there. It drafts, you send, and everything it writes is signed in purple. More on what that division of labour means is on what is an AI chief of staff and on the questions and answers page.