A weekly review should help the team run the next week.
It should not become a long report of everything that happened.
The most useful version brings a small set of numbers, blocked work, and decisions into one conversation.
Prepare one page
Use the same page every week.
Include:
- new leads;
- confirmed orders;
- conversion rate;
- active orders;
- on-time delivery;
- cash due;
- open customer complaints;
- decisions waiting for the owner.
Add a short note beside any number that changed enough to need attention.
Review movement, not every number
The meeting should focus on four questions:
- What improved?
- What moved in the wrong direction?
- What is blocked?
- What decision must be made?
If a number stayed within its normal range, it may not need discussion.
Turn each issue into ownership
Every issue that leaves the meeting should have:
- one owner;
- one next action;
- one due date;
- one point of review.
"The team will look into it" is not an action.
"Ama will review the five open delivery exceptions by Tuesday and update the queue" is clear enough to check.
Keep problem-solving outside the meeting
Some issues need more work than the review can support.
Assign the owner, define the question, and schedule a separate discussion with the people who need to solve it. This keeps the weekly review short and protects everyone else's time.
Close the loop next week
Begin the next review with the previous actions.
Ask what was completed, what changed, and what remains blocked. If the same action returns for several weeks, the team may have an ownership, capacity, or process problem.
The review is not finished when the meeting ends. It is finished when decisions move.
Start before the dashboard is perfect
A spreadsheet is enough.
Use the process for four weeks before adding more metrics or software. The questions the team keeps asking will show what the next version needs.
A consistent weekly operating review gives the owner a clearer business without requiring constant interruption.