How to Run a Quarterly Business Review With an HTML Slide Deck

Bottom line

A quarterly business review should explain what changed, why it changed, what the team learned, and which decisions or commitments follow. It is not a performance scrapbook. Use a stable metric dictionary and recurring structure so trends remain comparable, while allowing the narrative to focus on the quarter’s most consequential variance.

Define the review contract

Name the audience, business scope, calendar, data cutoff, and decisions expected. Decide whether the meeting is an executive operating review, a customer QBR, or a team retrospective; combining all three produces a deck that satisfies none. Publish the metric definitions and owners before the quarter ends.

Separate review from blame. Atlassian’s retrospective play recommends creating a safe space, gathering observations, grouping themes, discussing, and assigning actions. A QBR can use the same learning posture while still holding owners accountable for commitments.

Use a decision-oriented structure

1. Executive readout: outcomes, largest variance, and decisions needed.
2. Prior commitments: delivered, missed, changed, or cancelled—with reasons.
3. Scorecard: a small set of stable outcome and health metrics.
4. Customer evidence: retention, quality, research, and material feedback.
5. Financial and operating drivers: what caused the result.
6. Experiments and lessons: hypothesis, observation, and consequence.
7. Risks and dependencies: probability, impact, owner, and mitigation.
8. Next-quarter commitments: outcome, measure, owner, and due date.
9. Decision log: what leaders approved or deferred.

Put functional detail and raw tables in appendices. The main narrative should make the cross-functional system legible.

Build a trustworthy scorecard

Keep metric names, formulas, segments, time zones, currencies, and cutoffs consistent. Show target, actual, prior period, and trend where relevant. Mark incomplete data and restatements. Do not silently replace a difficult metric with an easier proxy midyear.

Pair lagging outcomes such as revenue or retention with leading indicators such as qualified pipeline, activation, reliability, or hiring capacity. Limit the scorecard to measures that can change a decision. A metric without an owner or response threshold is decoration.

Explain variance causally

For each material miss or beat, separate observation from explanation. “Conversion fell 12%” is an observation. “Pricing caused the fall” is a hypothesis until supported by segments, experiments, or customer evidence. Show alternative explanations and what would falsify the preferred one.

OpenStax’s outline guidance emphasizes purpose, audience, claims, evidence, and a natural spoken flow. Use that model instead of arranging slides by department. Organize around the few business questions leaders must resolve.

Design the deck for comparison

Keep metric positions, scales, colors, and definitions stable quarter to quarter. Use claim titles and annotate the event that changed the line. Directly label series; avoid legends when possible. Display sources and data cutoffs. Status colors must include text or symbols so color is never the only signal.

Follow the W3C presentation guidance for readable contrast, descriptions, captions, and accessible supporting material. A QBR often becomes an asynchronous record, so headings and chart explanations must stand without live narration.

Run the session

Send the deck early and reserve meeting time for variance, risk, and decisions. Time-box each topic. Record the decision, dissent, owner, and review date while participants are present. Unresolved questions become assigned actions, not vague parking-lot items.

HTML is useful when the scorecard needs controlled interaction or a web-native archive. Keep data snapshots immutable, secure access, and test any hosted link privately. Use a static PDF for archival or restricted recipients when interactivity adds little.

Quality check

Compare this quarter’s claims with the source systems, prior deck, and decision log. Ask whether every red item has an owner and every green item has evidence. Remove slides that celebrate activity without showing an outcome. Check dates, units, denominators, permissions, and appendix links one final time, then archive the approved snapshot alongside its decisions. A good QBR creates a shorter, clearer list of commitments than the one the team entered with.