TL;DR
Weekly business review (WBR) is the canonical Amazon-popularized operating cadence: a 60-90 minute weekly meeting where leadership reviews 50-200 core metrics against plan, identifies anomalies, and drives root-cause discussion. Originated as Amazon's S-Team weekly cadence (Jeff Bezos). Distinct from a status meeting: pre-read documents, narrative format, documented decisions. The fastest single operating-cadence upgrade for most growth-stage companies.
What is a weekly business review?
Weekly business review (WBR) is the canonical operating cadence introduced and popularized by Amazon. The format: a 60-90 minute weekly meeting where leadership reviews 50-200 core metrics against plan, anomalies are surfaced, and root-cause discussion is documented. The structure was codified in Colin Bryar and Bill Carr's "Working Backwards" — both former Amazon S-Team leaders.
The WBR is the canonical variant of an operating review. Two traits distinguish it from generic weekly meetings: (1) the pre-read document — a multi-page metrics narrative distributed 24+ hours ahead, and (2) the narrative format — no slides, prose explanations of variance with cross-functional accountability for the answer.
Why the WBR matters
Amazon's operating efficiency at scale is widely attributed to the WBR discipline. The mechanism: weekly variance surfacing means problems get identified in 7 days, not 30; cross-functional leadership in one room means decisions don't wait for next month's all-hands; documented decisions create owner accountability across meetings.
For growth-stage companies, adopting a WBR is the fastest single operating-cadence upgrade available. Bain's 2025 operating cadence study shows growth-stage companies that adopt a disciplined WBR see 18-30% faster decision velocity within 90 days, measured as time-from-signal-to-action on variance.
WBR structure
- Pre-read document. 5-15 page narrative distributed 24+ hours in advance. Cover sheet of metrics + variance commentary + recommendations.
- Silent reading. First 15-20 minutes of the meeting is silent reading of the pre-read. Eliminates "did you read it?" friction.
- Variance-first discussion. Each function presents the metrics that are off plan, in narrative format. On-plan metrics get a one-line callout.
- Cross-functional accountability. Why is marketing pipeline down 18%? Marketing answers, sales corroborates, RevOps validates the data. No blame, but no hiding.
- Documented decisions. Every intervention has an owner, a deadline, and a follow-up at next week's WBR.
- Time-boxed. 60-90 minutes. Hard stop.
Common WBR mistakes
- Slides instead of narrative. Slides hide thinking; narrative exposes it. Bezos famously banned PowerPoint from S-Team meetings for this reason.
- No pre-read. Without 24-hour pre-read, the first 30 minutes get consumed by "what does this number mean?" rather than "why did this happen?"
- Too many metrics, no narrative. A 200-metric dashboard with no variance commentary becomes a spreadsheet review. Aim for 50-100 core metrics with prose explanation for variance.
- No follow-up tracking. Decisions made and never tracked = decisions never executed. Open action items must roll forward to next WBR.
- Skipping weeks. Discipline matters. A WBR cancelled twice in a quarter signals the org doesn't care about cadence, which permission-gives the cancellation of other operating disciplines.
Related concepts
WBR is the canonical variant of operating review. Connects to operating cadence, operating intelligence, decision velocity, metric tree, single source of truth, and north star tree.
At a glance
- Category
- Category Creation
- Related
- 5 terms
Frequently asked questions
What is a weekly business review?
Weekly business review (WBR) is a 60-90 minute weekly meeting where leadership reviews 50-200 core metrics against plan, identifies anomalies, and drives root-cause discussion. Originated at Amazon (Jeff Bezos, S-Team cadence). Distinct from a status meeting: pre-read documents, narrative format, documented decisions.
Why did Amazon ban slides in business reviews?
Jeff Bezos famously banned PowerPoint in favor of narrative documents because slides hide thinking — bullets and graphics let presenters skim over weak reasoning. Narrative prose forces clear explanations of variance and recommendations. The format spread from Amazon to most operationally rigorous companies.
How many metrics should a WBR review?
50-200 core metrics is the typical range for a $20M-$500M ARR business. Below 50, the WBR misses variance signal; above 200, it becomes a spreadsheet review. The right number is whatever the leadership team can review with narrative context in 60-90 minutes.
What's the difference between a WBR and a board meeting?
Board meetings happen quarterly, focus on strategy and major decisions, and report to external stakeholders. WBRs happen weekly, focus on operational variance, and drive internal cross-functional decisions. WBRs feed the operating discipline; board meetings communicate the outcome.
How do you start a WBR cadence?
Three steps: (1) identify 50-100 core metrics aligned to a metric tree, (2) build the pre-read template with variance commentary structure, (3) commit to weekly cadence and protect the meeting from cancellation. Most companies improve dramatically by week 6-8 once the cadence sticks.
Sources
- Colin Bryar, Bill Carr. Working Backwards: Insights, Stories, and Secrets from Inside Amazon, 2021.
- Bain & Company. 2025 Operating Cadence Study, 2025. bain.com
- Andy Grove. High Output Management, Vintage, 1983 (revised 2015).
Fairview supports WBR cadence with single-source-of-truth metric trees and variance-first surfacing in real time.
Definitions reviewed by Siddharth Gangal, Founder, Fairview.
See it in Fairview
Track Weekly Business Review automatically.
14-day free trial. No credit card. First data source connected in 5 minutes.