The QBR structure, slide by slide
Borrowed from the Jurassic Park board meeting structure (KPIs vs plan, incident, decisions). Each beat is one slide, three at most.
- 01 Cover and agendaThe company, the meeting, the one-line truth, and the agenda. Send it as a pre-read.
- 02 TL;DRThe quarter in three lines: what happened, where we are, what we need.
- 03 ScorecardLast meeting's priorities, each with its target and an honest red, yellow or green.
- 04 KPIs vs planEvery key metric against plan, with the variance and a status, bad ones included.
- 05 What happenedA neutral, timestamped summary of the quarter's defining event. Facts, no adjectives.
- 06 The metric that brokeOne operational chart, annotated with the events from the timeline.
- 07 Root causesTwo or three causes, not symptoms, each with a concrete fix. Blame the system, not the person.
- 08 Lowlights, then highlightsBad news first and longer. It buys trust for the good news.
- 09 Financials and runwayRevenue, burn by line, cash, and months of runway, stated plainly.
- 10 Decisions neededTwo or three motions with cost and recommendation, for the board to approve or defer.
- 11 Next quarterThree priorities with a target and one owner each. They become the next scorecard.
- 12 CloseQuestions, closed session, and the date of the next meeting. No thank-you slide.
- Use it when
- Reviewing the quarter with a customer's owners and executive sponsor, or with an internal team.
- Typical length
- 8 to 12 slides.
- Format
- Presented live to agree next quarter's plan, then sent as the record.
See it in a real deck
Jurassic Park, The board meeting after the storm, 1993. Revenue: zero. Visitors: zero. Containment: below plan. Every slide opens our playable rebuild right where it is.
-
01Opening weekend: below plan. -
02The quarter in three lines. Line three is the ask. -
03Five priorities, two green. One was the gift shop. -
04Every KPI against plan. Every KPI is red. -
05One storm, one switch, one long night. -
06Uptime held at 100%. Then it held at zero. -
07Root cause: one person could switch off the island. -
08Lowlights first. The highlights are shorter. -
09Revenue stopped. The animals still eat. -
10Three decisions we need today. -
11Three priorities for Q4. None of them is opening. -
12Next meeting: on the mainland.
What good QBR decks do
- Open with the outcomes the customer bought you for, scored against the goals you agreed last quarter.
- Use their numbers and their words, not your product's usage stats.
- Name what is behind before they do, with the fix and an owner.
- Bring one or two recommendations they can act on next quarter.
- End with next quarter's plan and the decisions you need from them.
Where QBR decks usually fail
- A tour of your feature releases
- Usage stats with no link to their goals
- Hiding the misses
- No ask of the customer
Common questions about the QBR
What should a QBR include?
The goals you agreed last quarter, results against each, what is working and what is not, the plan for next quarter, and the decisions or help you need from the customer.
Who should attend a QBR?
The people who own the outcome on the customer side, ideally including the executive sponsor, and the account team on yours. If only day-to-day users come, it becomes a status call.
How do you make a QBR useful for the customer?
Report their results in their terms, admit what is behind before they raise it, and bring one or two recommendations they can act on.
Make yours with this structure
Type your site and we'll write the prompt for your deck, in your brand, built on the Jurassic Park board meeting structure (KPIs vs plan, incident, decisions).
Building it with AI? Compare the ways to make it with Claude, or add Pitch Unfairly to ChatGPT or Codex.