Operating Reviews

A team that acts as the CEO reviews its own business on a rhythm, the same way a company reviews its P&L. Two things pair at each level: a review (a meeting where you read the business off its own metrics) and a report (the written artifact that comes out of it). This page owns the review side; each report has its own home.

The QBR and the checkpoint are not the same thing#

The QBR is the review: every quarter you read the business off its metrics, exactly like the WBR and MBR, one zoom level up. What that read drives depends on when the quarter lands. At the mid-half QBR it produces a lightweight checkpoint: reallocate, kill, or add a Big Rock. At the half boundary it feeds a full Half Strategy cycle instead. So the checkpoint is the mid-half decision a QBR produces, not a separate meeting.

How WBR and MBR translate to a product team#

A classic business review reads a P&L. A product team’s “business” is its north star and its inputs, so that dashboard is your P&L, and the reviews are how you read it.

• WBR: a standing weekly read of the dashboard: north star + each input, week-over-week and against target, where you hunt variances (why did checkout completion dip two points?) and check that each Big Rock is moving the number it promised. It is a read, not a status meeting: narrate the numbers, dig into the misses, catch an anomaly before it becomes a missed rock. It complements the delivery-focused Weekly Product Call (on track / blockers / ad hocs); the WBR asks what are the numbers telling us?
• MBR: the zoom-out: the monthly trend of the north star, whether each bet is paying off against its narrative, and the deeper dives a weekly cadence runs too fast for. Its output is the monthly investor update: the MBR is where you actually face leadership with the month’s numbers.

Same discipline as an ops WBR/MBR; only the metrics differ: your north star and inputs instead of revenue and cost.

The monthly investor update#

The investor update is the artifact that most makes “act as the CEO” real: even when it is internal, you write it as though the people reading it had capital at stake. It is short and unsparing: the numbers that moved, the ones that did not, and the specific help you need:

# [Area]: Investor Update · [Month]

## TL;DR
One paragraph: how the month went, in plain terms. Good or bad, say it first.

## The numbers (vs. target)
North star + each input: where it is, where it should be, trend arrow.

## Wins
2-3 things that moved the business, with the metric behind each.

## Misses & risks
What didn't work or is off-track, and what you're doing about it.

## Asks
The specific decisions, hires, or unblocks you need from leadership this month.

Written honestly every month, it means the quarterly checkpoint and the year-in-review hold no surprises: the same no-surprises rule that governs performance conversations, applied to the business.

Related: The Framework, Weekly Report, Cadence, Half Strategy, Performance Review Cycle