Quarterly Business Reviews (QBRs) are the rhythm by which engineering leaders communicate progress and priorities to executives. Done well, they get your team resources and air cover. Done poorly, they signal lack of clarity and erode trust. Senior EMs are increasingly graded on this skill.
What QBRs are for
From the executive perspective:
- Did you deliver on what you said you would?
- What did you learn?
- What is next quarter’s commitment?
- What support do you need?
- What risks should I know about?
Not for: deep technical exploration, project status updates, fishing for compliments.
The standard format
Slide deck or written doc:
- Headline metrics (1 slide)
- Last quarter’s commitments and what shipped
- Outcomes vs goals (with red/yellow/green)
- Key learnings
- Next quarter’s commitments
- Risks and asks
Length: 10–15 slides, or 4–6 page memo. Plus 30–60 minutes of discussion.
The headline metric
One number that captures whether the quarter was good. Examples:
- Engineering velocity (story points, deploys/week)
- Reliability (uptime, incident count)
- User-facing outcomes (activation %, conversion)
- Business outcomes (ARR contribution, deals shipped)
Pick one, anchor on it across quarters so trends are visible.
Outcomes vs goals
For each Q-goal:
- What was the goal?
- What was the actual outcome?
- Color: green (hit/exceeded), yellow (partial), red (missed)
- Brief note on why
Be honest. Yellow and red on goals is normal; faking green is detected and trust-eroding.
The “what we learned” section
Strong EMs use this to show judgment:
- What surprised us?
- What assumption was wrong?
- What is the team going to do differently?
This is where you demonstrate you have a learning organization, not just an executing organization.
Next quarter’s commitments
Specific. Measurable. Realistic. Examples:
- “Activation rate from 35% to 50% by quarter end”
- “Reduce p99 latency below 200ms”
- “Ship feature X to 100% of users by week 8”
Don’t commit to what you cannot deliver. Calibrate to roughly 70% confidence.
Risks and asks
The most-skipped section by weak EMs. Strong EMs surface:
- Risks: what could blow up
- Asks: what you need from leadership (headcount, resources, scope decisions)
If you do not raise risks, leadership thinks everything is fine. When it is not fine 6 weeks later, you are blamed for hiding.
Common antipatterns
- Storytelling without metrics (“a great quarter” without numbers)
- Hiding bad news in dense text
- Goal padding (set easy goals, hit them, claim greatness)
- Skipping the asks (leadership cannot help if you do not ask)
- Reusing slides without reflecting on actual progress
The “executive perspective” lens
Frame each section in terms executives care about:
- Revenue impact
- Customer satisfaction
- Team health and retention
- Strategic positioning vs competitors
- Risk to business
Don’t lecture them on technical details. They have specialists for that.
The QBR as forcing function
Even if your company does not formalize QBRs, write one for yourself quarterly:
- Forces honest reflection
- Surfaces what you have actually learned
- Documents your team’s trajectory
- Becomes input for promotion packets and resumes
Frequently Asked Questions
How long should preparing a QBR take?
Half a day for a senior EM. Full day for a director with multiple sub-teams. The thinking is the work; the slides are the byproduct.
Should I include detailed metrics or stay high-level?
High-level for the deck. Detailed appendix for executives who want to dig in. Most will not.
What if I missed all my goals?
Be honest about it. Strong EMs can lose a quarter and still rebuild trust by demonstrating learning. Hiding always loses.