The Quarterly Business Review is the most expensive recurring meeting most B2B companies run. It eats two to three full days of senior time per quarter, multiplied across every region and segment. It generates a deck that nobody reads after the meeting ends. And it almost never produces a decision that wouldn’t have happened anyway.

That is not a process failure. It is a design failure.

“Most QBRs would survive being deleted from the calendar. The two or three each year that wouldn’t are the ones worth designing around.” — Mark Southgate

The good news is that QBRs are not hard to fix. The redesign is small. The hard part is being honest about what the existing forum is — and what it is not — before changing it.

What the QBR has become

The shape is familiar. Each regional leader presents a deck. The deck has 30 to 50 slides. The first ten are a recap of the quarter that just ended. The next ten are pipeline. The next ten are forecast. The last ten are commentary on enablement, attrition, marketing pipeline, or whatever theme the corporate office assigned.

Each presenter reads through their deck. The audience asks polite questions. The CRO summarises. The next leader presents. After two days, everyone has been on the receiving end of the same recap they had already seen in their own pipeline reviews three weeks earlier. No decision has been made. No risk has been changed.

This is inspection theater. It looks like governance. It functions as ritual.

The Gartner research on B2B buying behaviour is a useful mirror here. In a May 2025 survey of more than 1,200 buying teams, 74 percent showed “unhealthy conflict” during the decision-making process. The buying side is harder, more fractured, and slower. The seller-side forum that responds to that with a recap deck is fighting last year’s war.

What a useful QBR is actually for

A useful QBR exists to resolve a small number of decisions that the operating cadence below it could not. Three to five, not thirty.

Those decisions tend to be of a particular shape:

  • A territory or segment reallocation that requires the CRO’s authority.
  • A coverage or capacity intervention — moving headcount, restructuring a team, opening or closing a segment.
  • A deal-level intervention on a small number of strategic accounts that need executive participation to close.
  • A change in forecast methodology or category definitions because the existing one is misleading the leadership team.
  • A change in the operating cadence itself — what the pipeline review, deal review, and forecast call are inspecting and how often.

Those are the things only the QBR audience can decide. Everything else — the pipeline narrative, the rep-level performance commentary, the recap of last quarter’s deals — belongs in a different forum, a written brief, or nowhere.

As Mark Southgate puts it: “The QBR question is not ‘how was the quarter?’ It is ‘what do we have to decide that the rest of the operating cadence cannot?’”

Redesigning the forum

A QBR redesign that actually changes behaviour usually has four moves.

Move 1: shift the recap to writing. The deck recap exists because somebody once needed it. They no longer do. A two-page written brief, circulated 72 hours before the meeting, covers the same ground in 15 minutes of pre-reading time. The meeting starts with everyone having read the brief, not with the first presenter reading it aloud.

Move 2: name the decisions before the meeting. Each leader brings two to four explicit decisions they need from the room. “We need a call on whether the public sector vertical gets two additional AEs or whether we redirect that headcount to mid-market.” Not “we want to share an update on public sector.” Decisions, not updates.

Move 3: assign decision rights in advance. Each named decision has an owner, a recommendation, and a clear escalation path. The QBR is the forum where the recommendation gets accepted, modified, or rejected — not the forum where it gets formulated. Formulation happens in the operating cadence before the QBR.

Move 4: capture commitments, not minutes. The output of a useful QBR is a short list of commitments — who is doing what, by when, with what review mechanism. Not a deck. Not minutes. A list. If the list is empty, the forum did not justify its existence.

What this changes

Done well, the redesign shrinks the forum dramatically. A two-day QBR becomes a half-day QBR. The recap content moves to a written brief. The pipeline narration moves to the pipeline review. The deal narration moves to the deal review. The forecast narration moves to the forecast call. The QBR is left doing what only the QBR can do.

The other effect is more important. The pre-work changes. To bring three real decisions to a QBR, the regional leader has to have already pressure-tested them in their own cadence. They have to have a recommendation, a counterfactual, and the data to defend either. That work makes the operating cadence below the QBR sharper, because the QBR is now demanding outputs that the lower cadence has to produce.

“Forums are not neutral. They train the work that feeds them. A QBR designed for narration trains pipeline reviews that narrate. A QBR designed for decisions trains pipeline reviews that decide.” — Mark Southgate

The diagnostic

If you want to know whether your QBR is doing leadership work or decorative work, run a small audit on your last two.

For each QBR, list every decision the room actually made — meaning a named action with an owner and a date, where the absence of the QBR would have meaningfully changed the outcome. If the list is fewer than three items per QBR, the forum is not earning its place. If the list is zero, the forum is a habit, not a mechanism.

The fix is not to scrap the QBR. The fix is to redesign it around the three to five decisions that only this audience can make, and to move everything else to a forum that matches its purpose. The two days you save are not the win. The win is that the operating cadence below it starts producing different work.

Most companies have a QBR because they have always had a QBR. The companies that get serious about their deal review and forecast operating system end up redesigning every forum in the cadence, starting with the most expensive one. The QBR is usually that.

The forum is not the problem. The forum doing the wrong job is the problem. Fix the job, and the forum starts earning its time back.