Bring a shared view of the work
Prepare the same small set of records each week: due customer commitments, overdue invoices, open sales decisions and team capacity. Define the reporting period and check that the numbers use it consistently. Send routine status information beforehand so the meeting can focus on exceptions. Do not build a new report just to make the meeting look sophisticated.
Start with last week's decisions
Review the actions agreed at the previous meeting. Ask whether each is done, blocked or no longer relevant. A blocked action needs a decision, not another optimistic due date. Repeated unfinished actions may signal insufficient capacity, an unclear owner or a task that was never truly important.
- What changed since the last review?
- Which customer promise is most at risk?
- What requires a decision from the owner?
- What can we stop doing this week?
Worked example: capacity before new sales
Imagine a studio with three projects due next week and a promising new enquiry. The review identifies a missing customer approval that could bunch all three deliveries together. Instead of celebrating the pipeline in isolation, the team assigns the approval follow-up and offers the new prospect a start date that the delivery team can actually support.
Keep metrics connected to an action
A rising overdue-invoice balance should lead to specific follow-ups or a credit-control decision. A growing queue should lead to reassignment, revised commitments or a scope discussion. If nobody can describe what they would do differently when a number changes, it may not belong in the weekly review. Keep definitions stable so week-to-week comparisons mean something.
Close with a small decision log
Record the decision, owner, due date and evidence needed to call it done. Share that record with anyone affected but absent. Avoid assigning ten urgent priorities to one person. At the next review, start with this log again; that loop is what makes the meeting a management practice rather than a recurring conversation.