Example of a product QBR presentation for leadership must answer three questions that executives will always ask, whether or not they say them out loud: Are we on track? Do we know why things are the way they are? Do we know what to do next?
A QBR that cannot answer these three questions will prompt executive intervention in the product roadmap — which is what you are trying to prevent by presenting well.
What a Product QBR Is For
The quarterly business review is not a sprint demo and not a status update. It is a structured executive conversation about whether the product strategy is working and what adjustments are required.
The QBR has two outputs:
- Leadership alignment on the state of the product
- Specific decisions or approvals that the product team needs to move forward
If your QBR doesn't produce at least one decision, it was a status update, not a business review.
The QBR Slide Structure
H3: Slide 1 — Executive Summary (one slide)
Three bullets only:
- Headline: The most important thing that happened this quarter in one sentence
- Status: Are we on track against the quarter's goals? (Green / Yellow / Red)
- Asks: What do you need from this audience today?
The executive summary is read before you present. Executives who can answer all three from this slide before you start are predisposed to listen.
H3: Slides 2–3 — Quarterly Goals vs. Actuals
For each goal set at the beginning of the quarter:
- The goal (as stated at the start of Q)
- The actual result
- Green / Yellow / Red status
- One sentence explaining the variance (if any)
Format example: | Goal | Target | Actual | Status | Note | |---|---|---|---|---| | D30 retention | 35% | 31% | 🔴 | New user cohorts onboarded faster than expected; activation rate improvement offset the gap | | Feature adoption (new dashboard) | 40% of WAU | 47% | 🟢 | — |
According to Lenny Rachitsky on his newsletter, the product QBRs that generate the most executive trust are the ones with transparent variance explanations — executives who see red status without explanation become worried; executives who see red status with a clear cause and clear response become informed partners.
H3: Slides 4–5 — What We Learned
Top 3 learnings from the quarter:
- What we believed at the start of Q vs. what we learned
- What changed as a result
- What we're carrying forward
This is the most important section for senior PMs. It demonstrates intellectual honesty and learning velocity — two things leadership is evaluating whether they say so or not.
According to Shreyas Doshi on Lenny's Podcast, the product leaders who receive the most executive latitude are the ones who can clearly articulate what they got wrong in a quarter and why — this signals the judgment that comes from treating product bets as hypotheses rather than commitments.
H3: Slides 6–7 — Next Quarter Plan
For each goal being set for next quarter:
- The goal with specific metric target
- The key bets being made to achieve it
- The kill criterion — what would cause us to change course
- Resources needed (if any)
H3: Slide 8 — Asks and Decisions
List every specific decision or resource you need from leadership:
- Decision: "Do we expand to SMB or continue enterprise focus for Q3?"
- Approval: "We need to hire a senior data engineer — requesting approval of HC"
- Alignment: "We're proposing to deprecate Feature X — does leadership support this?"
Coming to a QBR without asks is a missed opportunity. Executives in a QBR are the most available they'll be all quarter to make decisions.
According to Annie Pearl on Lenny's Podcast, the product leaders who advance fastest are the ones who use QBRs as a decision-making forum rather than a reporting occasion — every QBR should have at least one ask that requires executive input, and the PM should leave with a clear answer.
FAQ
Q: What should a product QBR presentation include? A: Executive summary, quarterly goals vs. actuals with variance explanations, top 3 learnings from the quarter, next quarter plan with specific goals and bets, and explicit asks for decisions or approvals from leadership.
Q: How long should a product QBR be? A: 45–60 minutes for the full presentation and discussion. Executive summary and goals vs. actuals should take 15 minutes; learnings and next quarter plan take 20 minutes; Q&A and decisions take 15 minutes.
Q: How do you present red metrics in a QBR without losing credibility? A: Lead with the cause, not the number. "D30 retention came in at 31% against our 35% target because X — here's what we learned and what we're doing about it." Executives trust leaders who explain variances, not those who apologize for them.
Q: What decisions should a PM bring to a QBR? A: Decisions that require executive alignment — resource allocation, strategic trade-offs, deprecation of existing features, expansion to new segments, or any decision that is above the PM's unilateral authority level.
Q: How do you prepare for executive questions in a QBR? A: Prepare for three questions: Why is X metric below target? What is the biggest risk to next quarter's plan? Why are we prioritizing this over that? These three cover 80% of executive QBR questions.
HowTo: Create a Product QBR Presentation for Leadership
- Open with a one-slide executive summary containing a headline, overall status in green yellow or red, and your specific asks from the audience
- Present quarterly goals versus actuals in a table format with explicit variance explanations for every metric that missed its target
- Dedicate two slides to what you learned this quarter — what you believed at the start versus what the data showed and what changed as a result
- Present next quarter goals with specific metric targets, key bets, and kill criteria for each goal
- Close with an explicit asks and decisions slide listing every decision or approval you need from leadership in the room
- Prepare specific answers to three executive questions before the meeting: why is X below target, what is the biggest risk next quarter, and why this priority over that one