How to run a weekly business review (WBR): a practical operating guide

A weekly business review (WBR) is a short, recurring meeting where a team looks at a fixed set of core metrics against plan and prior weeks, notices what changed, and assigns follow-ups. The point is not to admire the numbers. It is to catch a problem or an opportunity while there is still a week to act on it, and to keep the whole team looking at the same reality.

This guide is for founders, operators, and team leads who want to install a weekly metrics rhythm without turning it into a status meeting or a two-hour slog. It covers what a WBR is, how it differs from monthly and board reviews, which metrics belong on it, how to structure the meeting, the mistakes that kill it, and how to instrument it so the data is ready every Monday.

What is a weekly business review?

A weekly business review is a standing meeting, usually 30 to 60 minutes, built around a consistent dashboard or deck of metrics. The same charts appear every week in the same order. Owners speak to the metrics that moved, and everything within normal range gets skipped.

The format is most closely associated with Amazon, where it is one of several recurring mechanisms in the company’s operating cadence. In Working Backwards, former Amazon executives Colin Bryar and Bill Carr describe a WBR that covers 200 to 300 metrics in a single hour, reviewed only where there is a notable variance, using a standard “6-12” chart that plots the trailing 6 weeks alongside the trailing 12 months so the eye can spot a real change quickly. The broader cadence pairs the weekly review with a monthly or quarterly business review and an annual planning process.

Most teams are not Amazon and should not try to review 250 metrics. But the core idea travels well: one consistent set of numbers, reviewed every week, focused on changes rather than levels, with a named owner for each line.

Weekly business review vs monthly and board reviews

These reviews sit at different altitudes and answer different questions. Running them as if they were the same meeting is a common way to waste everyone’s time.

The weekly review feeds the ones above it. If your WBR is healthy, the monthly management report and the executive dashboard become summaries of things the team already understands, not fire drills assembled the night before.

When a team is ready for a WBR (and when it is not)

A WBR earns its place once you have metrics that actually move on a weekly timescale and people who can influence them.

Use a WBR when:

• You have a repeatable business with signups, activations, orders, tickets, or revenue events happening every week.
• Each core metric has an owner who can explain a change and act on it.
• Decisions are currently slow because problems are discovered a month late.

Hold off, or keep it very light, when:

• You are pre-product-market-fit and weekly numbers are too noisy to read. A biweekly or monthly check-in is often better.
• Your metrics only move on a monthly cycle, such as enterprise contracts that close a few times a quarter.
• Nobody owns the numbers yet. A WBR without owners becomes a reporting ritual, not a decision meeting.

Which metrics belong on a WBR

The fastest way to ruin a weekly review is to put every metric on it. Use a simple test. A metric belongs on the WBR only if it passes all three:

1. Someone can move it within a week. If no action taken this week could change the number by next week, it belongs on a monthly or quarterly review instead.
2. It moves week to week. A metric that is flat for a month gives you nothing to discuss weekly. Watching it weekly just trains people to ignore the deck.
3. It has an owner who can explain a change. Every line needs one person who can say why it moved and what they are doing about it.

Balance leading and lagging indicators. Lagging output metrics such as revenue, gross margin, or net new customers tell you the result. Leading input metrics such as demo bookings, activation rate, time to first value, or support backlog tell you what is about to happen and are usually controllable within the week. Amazon’s version leans heavily on controllable input metrics for exactly this reason. A good weekly deck for a lean team is closer to 10 to 20 metrics than 200, split across acquisition, activation, revenue, and operational health. If you are unsure whether something is a headline number or supporting detail, our note on KPIs vs metrics is a useful filter.

How to structure the meeting

The meeting should be boring in a good way: same order, same charts, same rhythm every week. Boring structure is what lets people focus on the content.

1. Open with the scorecard. One screen of headline numbers against plan and against last week. Thirty seconds, no discussion yet.
2. Walk the deck in a fixed order. Group metrics by the customer journey or by function, and keep that order stable week to week so people build muscle memory.
3. Speak only to variances. If a metric is within its normal range, the owner says one line and moves on. Time goes to the things that moved.
4. Ask why, not just what. For anything off-trend, the owner explains the cause and whether it is a one-week blip or a trend. This is where a live dashboard earns its keep, because you can drill in on the spot.
5. Capture actions, not decisions. The WBR surfaces problems and assigns owners and due dates. It is not the room to redesign strategy. Big questions become their own working session.
6. End on time. A predictable end time is what keeps attendance and attention high.

A useful default: 45 minutes, one facilitator who keeps pace, metric owners who speak to their own lines, and a running action log that gets reviewed at the top of next week’s meeting.

Common mistakes

• Too many metrics. A deck nobody can read in the time allotted gets skimmed and then ignored. Cut aggressively.
• Reviewing levels instead of changes. “Revenue is 1.2 million” means little on its own. “Revenue is down 6 percent week over week, driven by a drop in trial conversions” is a WBR.
• No owner per metric. Orphan metrics get narrated by whoever is loudest and acted on by no one.
• No action items. If nothing leaves the room with an owner and a date, you held a reporting meeting, not a review.
• The Monday scramble. When someone spends Sunday copy-pasting numbers into slides, the data is stale, error-prone, and impossible to drill into. Automate the assembly.
• Letting it drift into a status update. A WBR is about metrics and what they imply. Project updates belong in a different meeting.

How to instrument a WBR

The mechanics of getting the numbers on screen decide whether the meeting is sharp or painful. There are three common setups.

The single biggest upgrade is moving from a static deck to a live dashboard. When the numbers are queried live, you stop debating whether the data is current, and you can answer the inevitable “why did that drop?” question during the meeting instead of assigning it as homework. If you want the Amazon-style 6-12 chart specifically, Bryar and Carr released a free, open-source WBR App on GitHub that generates the format from your data.

This is where a tool like Basedash fits a lean team’s WBR. It connects to your production database or warehouse, so the dashboard you review is live rather than a snapshot, and a non-technical teammate can ask a follow-up question in plain language and drill into the underlying rows during the meeting instead of waiting a week for an answer. The goal is not a fancier deck; it is a review where the data is trustworthy and the follow-ups get resolved on the spot. For more on making dashboards that actually change what people do, see our guide to dashboards that drive decisions.

FAQ

How long should a weekly business review be?

For most teams, 30 to 60 minutes. Amazon runs its full-company WBR in about an hour despite covering hundreds of metrics, because owners speak only to variances and skip anything within normal range. Smaller teams with a tighter deck can often do it in 30 to 45 minutes. If it regularly runs long, you have too many metrics or you are debating decisions that belong in a separate session.

What is the difference between a weekly and a monthly business review?

The weekly review answers “what changed this week?” using fast-moving operational and input metrics, and produces action items. The monthly review answers “are we on plan?” using summarized financials and KPIs, and produces decisions and reforecasts. The weekly meeting is granular and verbal; the monthly one is higher level and usually backed by a written pack.

How many metrics should a WBR include?

Fewer than you think. Amazon reviews 200 to 300, but it has the scale and tooling to support that. A startup or single team is usually better with 10 to 20 metrics that pass three tests: someone can move it within a week, it moves week to week, and it has an owner who can explain a change.

Who should own the weekly business review?

One facilitator owns the meeting itself, keeping pace and enforcing the format, often a founder, chief of staff, or ops lead. Each metric has its own owner who speaks to that line and is accountable for the follow-ups. Splitting these roles keeps the meeting moving while preserving accountability for the numbers.

Is a WBR the same as a standup or status meeting?

No. A standup is about what people are working on. A WBR is about what the metrics are doing and what that implies. Keep project updates out of the WBR, or it turns into a status meeting where the numbers become background noise.