The weekly operations review that keeps a lean team on track

Key takeaways

A weekly operations review meeting is a fixed 30 minutes in which the people running day-to-day work look at the same few numbers, agree what is off track and assign actions. For a lean team with outside capacity it is the main control. Five numbers and a fixed agenda are enough.

• 30 minutes, same time each week, same agenda.
• Five numbers: volume, turnaround, backlog, quality, capacity.
• Every action has one owner and a date.
• In-house and outsourced leads both attend.

What is a weekly operations review?

A weekly operations review is a short, regular meeting that compares last week's operational results with targets and decides what to change. It is not a status round-table. It looks at numbers first, discusses only the exceptions and ends with a short list of actions.

• How outsourcing helps small businesses scale without hiring
• Managing in-house and outsourced teams as one operation

Why weekly, not monthly?

Weekly because problems in operations compound quickly. A backlog that starts on Monday is a complaint by the following week. Monthly reviews arrive too late to adjust staffing or fix a process. A weekly rhythm catches a drift while it is still small and cheap to correct.

• BPO scorecard and KPIs

Which five numbers should you review?

Review five numbers for each main process. Keep the definitions fixed so that week-to-week changes mean something.

• Volume: how much work arrived.
• Turnaround: how quickly it was completed.
• Backlog: what is still open and how old.
• Quality: errors or failed checks from the sample.
• Capacity: hours available against hours needed next week.

• The KPIs that show whether your business is really scaling
• Demand forecasting for small teams: plan capacity ahead

What is a good agenda?

A good agenda is the same every week. Five minutes on last week's actions. Ten on the numbers, exceptions only. Ten on the one or two issues that need a decision. Five on next week's capacity and any changes the team should know about. Anything longer belongs in a separate session.

• 1. Actions from last week: done or not.
• 2. The numbers: what is off target.
• 3. Issues: decide and assign.
• 4. Next week: volume, capacity, changes.

Who should attend?

Attendance should be small: the internal process owner, the provider's team leader if work is outsourced, and whoever can make decisions about staffing and priorities. The business owner need not attend every week. A one-page summary keeps them informed.

• Who should own the outsourcing relationship in a small firm?

When does the review stop working?

The review stops working when it turns into a discussion without numbers, when actions have no owner, or when it is cancelled in busy weeks, which are the weeks it matters most. It also fails if the numbers are used to blame people. The purpose is to find and fix causes.

• Scaling mistakes small businesses make and how to avoid them

What does this look like in practice?

A pattern we see in UK firms without a review: the first sign of a problem is a customer complaint or a month-end surprise. After a few weeks of a fixed 30-minute review, the same firms spot rising backlogs on a Tuesday and add hours on a Wednesday, and month end becomes uneventful.

• See client work
• BPO Solutions for UK businesses

Weekly review checklist

Set these up before the first meeting.

• A fixed day and time in the diary.
• A one-page scorecard with five numbers per process.
• Written definitions for each number.
• A standing four-part agenda.
• An action log with owner and date.
• A one-page summary for the business owner.

• A simple BPO governance model
• A 90-day plan to scale without adding headcount

Next step

Tell us your main processes and what you currently measure. We will suggest five numbers for each and a review format that fits in half an hour.