The operations meeting lists everything that happened, but the unresolved work stays unresolved. A weekly operations review should help the team decide what needs attention, who owns the next action and which commitment must change. Prepare the current work view before the conversation starts.
Photo by Ngital on Unsplash.
Choose a small set of operating questions
Which client work is waiting? Where is capacity constrained? What recurring failure needs investigation? Which decision needs the owner's authority? Use the measures and records that answer those questions. Do not add a metric simply because the software can display it.
Use a repeatable agenda
Changes in demand or commitments.
Overdue and blocked work, with causes.
Quality problems and recurring exceptions.
Capacity and ownership decisions.
Progress on the small number of active improvements.
Actions, owners and next checks.
Review exceptions to the normal flow rather than reading every completed task. Invite the people who can explain the evidence or make the decision. Send other updates in the shared record.
An illustrative discussion
A service team sees several incomplete client briefs. Instead of asking everyone to chase harder, the review identifies a missing acceptance rule at the sales handoff. The operations lead owns a checklist trial, and the managing director resolves which role must supply the agreed scope.
Keep decisions connected to work
Related guidance: practical process-mapping guide.
Record what changed, why, the owner and the date. At the next review, check whether the action happened and whether it addressed the problem. If the same item returns repeatedly, inspect authority, capacity and the chosen action rather than treating repetition as progress. Hili Consulting can help establish a practical review rhythm around the decisions your business needs.
