The weekly operating review: 45 minutes that replace the hallway decisions
“Got a minute?” It is the most expensive question in a growing business. It arrives at the founder’s door many times a day, and each time it carries a decision: whether to approve the credit, which order ships first, what to tell the customer whose job slipped.
The founder answers, and the work moves. Then the same question comes back next week from someone else, and gets answered again, sometimes differently. Nothing was wrong with the answer. It just was never written anywhere.
Why the same questions keep coming back
A decision made in a hallway reaches the one person who asked. Everyone else learns it secondhand or not at all. Three people end up following three versions of the same rule, and the founder becomes the only reliable place to find out which one is right.
That is how a capable team ends up waiting on one person. A business can’t scale if the founder is the only one who knows how it runs, and decisions that live only in conversations are a large part of what the founder alone knows.
The interruptions are not the real problem. They are a symptom of a business with no standing place to make decisions.
The shape of a weekly operating review
The fix is one recurring meeting with a fixed shape. Same day, same time, same people, same agenda, every week, whether the week was calm or chaotic.
- The scorecard. Start with your operational scorecard: the handful of numbers that show whether the business is on track. Read them, do not debate them. Any number that is off track goes to the issues list.
- Last week’s commitments. Each person reports on what they said they would do: done or not done. No stories. Anything not done either gets a new date or goes to the issues list.
- The issues list. Work the list from the most important item down. Each issue ends with a decision, one named owner and a due date, written down before the meeting moves on.
- The read-back. Close by reading the decisions and owners aloud, so everyone leaves with the same version.
Hold it to 45 minutes and end on time. If an issue cannot be settled in the room, the decision is who will bring back what is missing, and by when.
The rules that make it hold
- One issues list, open all week. Anyone can add to it at any time. “Put it on the list” becomes the answer to most hallway questions, and the founder’s door gets quieter.
- One owner per issue. A name, not a department. When everyone owns a problem, nobody does.
- Decisions are written in one place. The same document every week, so anyone can look up what was decided and why.
- The meeting happens even when it feels unnecessary. A calm week is a short meeting. Skipping it is how the rhythm dies.
Why the decisions compound
The meeting itself is useful. The record it leaves behind is worth more.
After a few months of weekly reviews, the business has something most founder-operated companies never build: a written history of what it decided, who owns what, and why. A new manager can read it and understand how the business actually runs. A question settled in March does not need to be settled again in June, because the answer is on the page. The operational scorecard shows whether last month’s decisions actually moved the numbers.
That is knowledge compounding. Each week starts from everything the earlier weeks settled, instead of from whatever people happen to remember. The hallway version of the same business makes every decision fresh and keeps none of them.
It also changes the founder’s job. Instead of being the answer desk, the founder runs the room where answers get made and recorded. The team learns to bring issues to the list instead of to the door, and more of them get solved before they ever reach the meeting.
Start next week
Pick the day and the time. Choose the numbers you already track and trust, even if there are only a few. Open one shared issues list and tell the team it exists. Run the first review with the four-part agenda above, and write every decision down.
The first few will feel stiff. Keep going. The habit matters more than the format, and the format gets better every time it runs.