A small team's guide to a weekly operations review

Wed, 11 Nov 2026 08:40:04 +0000

Most small teams skip the weekly operations review because it sounds like corporate theatre. Done properly it takes thirty minutes and saves hours of firefighting.

Start with three numbers only: orders or tickets opened, orders or tickets closed, and the oldest item still waiting. If the oldest item is older than your promise to customers, that is the agenda.

Next, ask each person for one blocker, not a status report. A blocker is something that cannot move without another person’s decision. Write the owner’s name next to it and a date. Nothing else goes on the page.

Close the meeting by deleting one recurring task. Teams that only ever add work eventually stop finishing it. If nobody objects to removing a task for a month, it was probably not needed.

Tools matter less than rhythm. A shared spreadsheet and a calendar reminder beat an expensive dashboard nobody opens. If you want a broader view of how other small companies structure their operations, the Operations Management overview on Wikipedia is a decent starting map, and for promotion and visibility experiments there are practical write-ups at PromoPilot.

Try it for four weeks and keep the notes in one place. The pattern of repeated blockers usually shows where the process, not the people, needs fixing.

notes on The Operations Desk

A small team's guide to a weekly operations review