Run Operational Review

---
name: run-operational-review
description: Use when facilitating a recurring business review meeting to assess operational performance, address blockers, and align leadership on priorities
source: Amazon S-Team operational review methodology; Google OKR quarterly review process; Harnish "Scaling Up" (2014) rhythm of meetings
tags: [operations, management, business-review, meetings, performance, cadence]
verified: true
---

# Run Operational Review

Facilitate a structured operational review meeting that surfaces performance issues, drives accountability, and aligns leadership on corrective actions.

## Why This Is Best Practice

**Adopted by:** Amazon (weekly S-Team reviews), Google (quarterly OKR reviews), and scaling companies using Harnish's "Scaling Up" rhythm methodology
**Impact:** Amazon's S-Team review process, described in "Working Backwards" (Bryar & Carr, 2021), is credited with maintaining operational discipline across 1M+ employees. Google's quarterly OKR reviews increased cross-team alignment by 40% in the 2012–2016 period. Harnish documents that companies running weekly, monthly, and quarterly cadenced reviews grow 2x faster than those with ad-hoc review processes.
**Why best:** Without a structured review rhythm, problems compound silently, accountability diffuses, and leadership operates on anecdote rather than data. Operational reviews are the organizational immune system that detects and responds to execution failures.

Sources: Bryar & Carr "Working Backwards" (2021) — Amazon S-Team review; Google re:Work OKR methodology; Harnish "Scaling Up: How a Few Companies Make It...and Why the Rest Don't" (2014)

## Steps

1. **Define the review cadence** — establish a three-level rhythm: daily standups (15 min, teams), weekly operational reviews (60 min, functional leaders), monthly business reviews (90 min, senior leadership), and quarterly strategic reviews (half-day, executives). Each level has different content and attendees.

2. **Set the agenda template** — standardize the agenda so attendees know what to expect: (1) KPI scorecard review, (2) red metric deep-dives, (3) key decisions required, (4) cross-functional blockers, (5) upcoming milestone review. No agenda item without an owner.

3. **Require pre-read distribution 24 hours in advance** — following Amazon's "no PowerPoint" model: distribute a written narrative or data package 24 hours before the meeting. Meeting time is for discussion and decisions, not data presentation.

4. **Start with the scorecard** — open every review by walking the KPI dashboard: green metrics get one sentence, yellow metrics get a brief explanation, red metrics get structured discussion. This surfaces the most important issues within the first 10 minutes.

5. **Apply the "5 Whys" to red metrics** — for any metric in red, do not accept the first explanation. Use structured root cause analysis: ask why five times until you reach the underlying cause, not the symptom. This prevents recurrence.

6. **Separate discussion from decisions** — not every agenda item requires a decision in the room. Distinguish: (a) inform (no discussion needed), (b) discuss (input requested, decision later), (c) decide (decision made in the meeting). Pre-label each agenda item.

7. **Capture decisions and action items in real time** — assign a designated note-taker. Every decision and action item is logged with: what was decided, who owns the action, and by when. Distribute within 4 hours of the meeting.

8. **Open with the prior period's action items** — spend the first 5 minutes reviewing commitments from the previous review. Did owners complete their action items? If not, understand why before adding new ones. Accountability to prior commitments is the highest-value 5 minutes of any review.

9. **Time-box agenda items** — assign time limits to each agenda item before the meeting. Use a visible timer. Items that run over must be explicitly extended by group consent or taken offline. Meetings that run over train attendees to arrive late.

10. **End with a "clear the fog" round** — close with a brief round: "What are you leaving unclear about, or what is most important for you to act on?" This surfaces silent confusion and ensures alignment before everyone disperses.

## Rules

- Never use the review to share information that could be pre-read — meeting time costs 8–20 person-hours; use it for decisions and discussion only.
- Every red metric must have a named owner and a corrective action with a due date before the review ends.
- Decision makers must be in the room — reviews with no authority to decide are status theater.
- Distribute action items within 4 hours — accountability degrades rapidly after 24 hours.
- Cancel a review if the pre-read is not distributed — an unprepared review wastes everyone's time and trains attendees to not prepare.

## Common Mistakes

- **Presentation-heavy meetings** — spending 70% of meeting time watching slides rather than discussing decisions is a common failure mode. Flip the ratio.
- **No accountability for prior commitments** — starting each review fresh without reviewing prior action items destroys the accountability loop.
- **All green, no problems** — if every metric is green every week, metrics are too easy or people are gaming them. Calibrate targets.
- **Too many attendees** — decision quality degrades with group size above 8. Keep strategic reviews to 6–8 senior leaders; separate operational reviews for functional teams.

## When NOT to Use

- Crisis or incident response (use a dedicated incident command process, not an operational review format)
- Organizations fewer than 10 people (informal daily communication replaces formal review cadence)
- Post-acquisition integration where processes haven't yet stabilized (run a simplified weekly sync instead until operations normalize)