Review exceptions first
Share routine updates before the meeting. Use live time for signals outside range, risks and decisions.
← All toolkits
Performance rhythms
Weekly Operating Review
Run a focused review of signals, constraints, decisions and commitments without another round of status updates.
Use this when
Start with a live team problem.
- Weekly meetings are dominated by updates.
- Actions are discussed but not carried into the next week.
- Risks remain invisible until the founder intervenes.
How to use it
Move from context to one usable agreement.
Make the decision explicit
Record what was decided, who owns the action and when it will be reviewed.
Close the learning loop
Check last week’s commitments and capture one process improvement where the same issue repeats.
Worked example
45-minute leadership operating review
Use the example to understand the level of specificity. Replace the content with evidence from your own team.
WEEKLY OPERATING REVIEW 0-5 MINUTES: LAST WEEK - Confirm completed commitments - Move incomplete actions with a reason and new decision 5-15 MINUTES: SCORECARD EXCEPTIONS - Review only measures outside the healthy range - Confirm cause, owner and required action 15-30 MINUTES: CONSTRAINTS AND DECISIONS - Choose the two most material constraints - Make or assign each decision 30-40 MINUTES: CUSTOMER AND TEAM RISKS - Surface risks requiring cross-team support 40-45 MINUTES: COMMITMENTS - Read back owner, action and due date - Confirm what will be communicated after the meeting
Blank template
Weekly Operating Review
Copy this into Docs, Notion or your existing workspace, or print it for a team conversation.
WEEKLY OPERATING REVIEW Date: Facilitator: Decision recorder: 1. LAST WEEK'S COMMITMENTS - Completed: - Incomplete and why: 2. SCORECARD EXCEPTIONS - Signal: - Cause: - Decision or action: - Owner: 3. CONSTRAINTS AND DECISIONS - Constraint: - Decision required: - Decider: - Due: 4. CUSTOMER AND TEAM RISKS - 5. COMMITMENTS - Owner / action / due date: 6. COMMUNICATION REQUIRED -
The System Folks · Free founder resource · thesystemfolks.com/resources/weekly-operating-review
Common mistakes
Keep the tool connected to real work.
- 01
Reading information that could have been shared before the meeting.
- 02
Leaving actions without one owner and a due date.
- 03
Adding topics without removing lower-value discussion.
Why this works
Evidence behind the resource
The process approach uses evidence and continual improvement to manage performance as a system.
Read ISO process and improvement approachNeed help implementing it?
A template can reveal a bigger operating problem.
If meetings cannot improve because roles, scorecards or decision rights are missing, we can help install the full operating rhythm.
Contact us when one costly workflow or team bottleneck needs diagnosis, build support and adoption.
Get implementation support Use another toolkit