Quarterly Business Reviews That Change The Plan

Most quarterly business reviews are reporting exercises. The team assembles metrics, builds slides, presents to leadership, receives nods and questions, and returns to doing the work they were planning to do anyway. The QBR is a ceremony that marks the quarter's close without actually influencing the next quarter's plan. Everyone knows this and nobody says it, because the alternative (a QBR where the plan genuinely changes based on what the review surfaces) requires leadership to admit that the prior plan was partially wrong and that the team needs to pivot.

This is the structural failure of the typical QBR, and it's the specific thing that separates growth operations that compound from those that don't. Teams whose QBRs actually change the plan learn faster. Teams whose QBRs are reporting exercises learn what was supposed to have been learned three months earlier. This article is about the operating pattern that makes QBRs functional rather than ceremonial.

Why Most QBRs Are Ceremonial

Three structural reasons the default QBR pattern produces reports rather than decisions.

The reviewer and the reviewed are the same people. In most QBRs, the team that executed the quarter's plan also presents the review of that plan. They have strong motivation to frame the quarter favourably, their performance is at stake, their choices are being evaluated, their roles depend on the narrative. Even with good intentions, people presenting their own work struggle to honestly surface what didn't work.

The format rewards polish over honesty. QBR decks take weeks to prepare, have professional design, run 40+ slides. The production effort signals importance but also creates inertia, a deck that took three weeks to build isn't going to be challenged in the session it's presented in. The format produces its own reverence.

The decision framework is missing. A functional QBR should produce specific decisions about what changes for next quarter. Most QBRs don't have a decision section, they end with questions and "great discussion" and implicit agreement that the plan continues. Without a forcing function for decisions, ceremony wins over substance every time.

The fixes are structural, not cosmetic. A more honest QBR requires different inputs, different participants, different outputs. Redecorating the same format with better slides doesn't change what it produces.

What A Functional QBR Produces

Before describing the structure, worth being specific about the outputs a QBR should produce when it's working.

An honest assessment of what happened. Not a narrative about the quarter, but a specific accounting of what was planned, what was achieved, what wasn't, and what the team now believes differently than it did 90 days ago. The honesty is what makes the rest possible.

Named decisions about what changes. Which initiatives continue. Which get paused. Which get scaled. Which hypotheses were confirmed or rejected. These are specific decisions, not themes or directions, "we're pausing LinkedIn Ads for the next quarter and redirecting the budget to content production" rather than "we're going to focus more on content."

A revised plan for the next 90 days. The plan for the coming quarter should reflect the decisions. Not a restart from scratch, a modification of the prior plan based on what the review surfaced. The plan should include both what continues (scaling what worked) and what changes (responding to what didn't).

An updated view of strategic direction. If the quarter's learnings raise questions about the annual or multi-year plan, the QBR is where those questions get raised. Most QBRs skip this because it's uncomfortable; QBRs that do it produce strategic decisions early when course correction is cheap.

The Structural Shifts That Make QBRs Functional

Four specific shifts from the default pattern.

Shift 1: Separate review from presentation

In the default pattern, the team executing the quarter prepares a presentation defending its execution. In a better pattern, the team prepares data and observations, and a separate reviewing voice (a board member, an advisor, an external facilitator, or the CEO if senior enough to be independent) actually conducts the review.

The separation matters because it creates honest evaluation. The executing team shares what they saw; the reviewer probes, asks uncomfortable questions, and tests whether the quarter's story holds up. Without this separation, the QBR becomes presentation and Q&A, which biases toward polish over probe.

At Series A and smaller companies where the reviewer role is hard to fill, the alternative is structured pre-read and a facilitator (often the CEO or Head of Growth) running the session with explicit authority to challenge. This is second-best but workable.

Shift 2: Cut the deck

A functional QBR doesn't need 40 slides. It needs a 4-6 page memo that can be read in 15 minutes before the session. The memo covers: what we set out to do this quarter, what happened, what we now believe differently, what we recommend for next quarter.

The session then becomes discussion rather than presentation. The team doesn't spend the hour walking through slides, the memo is already read, and the session is spent on the things that actually matter: the decisions coming out of what was observed.

Writing the memo forces honesty. Slides let vague statements pass because they're visual; prose forces specific language. "We scaled paid channels throughout Q2 with mixed results on CPL" in a slide is acceptable. In a memo it's visibly weak and needs rewriting to "CPL declined from £310 to £220 on LinkedIn but rose from £180 to £240 on Google, and neither channel hit its MQL volume target."

Shift 3: Explicit kill/scale/test categorisation

The decisions section should force every significant initiative into one of three categories: scale (keep and expand), test (keep and continue to prove), or kill (pause or stop). Each initiative gets categorised. No "continue as is" option, that's the default that allows ceremony to persist.

This categorisation is the forcing function that produces decisions. An initiative that was running in Q2 and isn't in the scale or test list after Q3's QBR is being killed, whether or not the team wanted to name that explicitly.

Shift 4: Document what you now believe differently

One section of the memo should explicitly list the things the team now believes differently than it did 90 days ago. Not dramatic reversals, ordinary updates based on what the quarter's evidence produced.

"We used to believe content would drive 30% of pipeline within 12 months; based on this quarter's results we now believe it will drive 10-15% unless we invest more significantly in distribution."

"We used to believe LinkedIn Ads at £10k/month would be sustainable for us; we now believe the ACV isn't high enough to sustain that CPL at that volume."

"We used to believe our ICP was CMO-level buyers; we now believe the actual buying power is one level down and marketing needs to target accordingly."

This section is the compounding asset of the QBR, it's where learnings get surfaced in a form that shapes future decisions. Without it, learnings stay in individual team members' heads and don't transfer to the organisation.

What The Week Around A Good QBR Looks Like

The operating pattern isn't just the session, it's the week surrounding it.

T-7 days: Team begins pulling data and writing the memo. Rough draft by end of week. No slides yet.

T-3 days: Memo finalised and circulated. Participants expected to read before the session. The circulation moment forces the memo to be complete enough to stand on its own, not a deck that relies on the live presentation to make sense.

Session: 90 minutes for most growth-stage companies. First 20 minutes clarifying questions and observations on the memo. Next 40 minutes working through the kill/scale/test decisions. Final 30 minutes setting the Q+1 plan skeleton.

T+2 days: Revised plan document produced, reflecting the decisions from the session. Distributed to the team. New quarter's operational work starts against it.

This pattern compresses what QBRs usually sprawl across weeks into a focused rhythm. The session itself is more intense than typical QBRs because less time is spent on presentation; the total team time invested is less because slide production is replaced with memo writing.

When The Pattern Breaks

Three conditions that break even a well-structured QBR.

The CEO or senior reviewer can't tolerate honesty. If leadership responds to candid assessment with blame or defensiveness, the next QBR will be more polished and less useful. The pattern requires leadership that rewards honesty even when the news is bad. Without that, teams learn to pre-sanitise and the QBR loses its function.

The quarter was too chaotic for comparison. A quarter with major disruption (fundraising, exec turnover, product reset) may produce a QBR where the structured kill/scale/test framework doesn't quite apply because so much was in flux. The best version is acknowledging this explicitly rather than forcing the quarter into a framework it doesn't fit.

No teeth on decisions. Decisions made in the session that don't actually get executed in the following quarter erode trust in the process. The test of QBR integrity is whether the Q+1 plan actually reflects the Q decisions. If the team keeps running things the QBR said to pause, the QBR isn't functioning regardless of how well the session went.

Where This Sits in the NBT Growth Model

Quarterly business reviews are part of the operating rhythm of Stage 4 (Optimisation) in the NBT Growth Model. They're the larger-scale version of the monthly loop review that the growth-driven marketing loop describes, the quarterly moment where accumulated learnings get converted into strategic decisions rather than just tactical adjustments.

The relationship to OKRs for small growth teams is direct. OKRs define what the team is aiming for each quarter; the QBR is where last quarter's OKRs get honestly scored and next quarter's get set. A QBR without OKR grounding is review without criteria; OKRs without QBR rhythm are targets without reflection.

If your current QBRs are ceremonial rather than functional, or you're setting up a QBR pattern and want to start with structure that produces decisions rather than reports, get in touch for a strategy call. We'll walk through the pattern with you and help install it.