A friend who runs ops at a mid-market SaaS company told me recently that her CEO had taken to calling the company's QBRs "the most expensive book club in the industry." Three days of preparation, two days of presentations, sixty leaders in a room, and almost no decision that anyone could trace back to the meeting six weeks later. Sound familiar?
Quarterly business reviews are the largest single piece of management ceremony most companies run. They consume more leadership attention than any other single artefact in the operating year. And the honest assessment — across every company I've watched up close — is that the majority of them describe the past instead of changing the future. If your team would behave identically next quarter whether the QBR happened or not, what exactly were those three days for?
What separates a real review from a recital
The QBRs that move the needle share three properties. None of them require new tooling. All of them require the leadership team to behave differently in the room.
The first is a real pre-read with the actual data. Not a teaser deck. The full numbers, the work that was tagged to each objective, what shipped, what slipped, what got quietly deprioritised — sent two business days ahead, with the expectation that everyone arrives having read it. Nobody presents numbers live. Reading slides aloud to people who already read them is a ritual, not a review. The meeting is for the conversation those numbers should provoke, not for the numbers themselves.
The second is one question per objective, asked plainly. Not "tell me everything that happened with this KR." Just: what changed, and what should we do about it? If the honest answer is "nothing changed and nothing should change," then the objective wasn't a real bet. It was a long-running task. Real bets generate real movement — either toward the outcome or away from it — and a quarter without movement is a quarter without learning.
The third is a written decision register that lives in the same system as the work. Not a Google Doc. Not a meeting note in someone's notebook. An artefact attached to the initiatives, KRs, and owners it concerns, so that when somebody asks in six weeks "wait, what did we agree about the pricing rollout?", the answer is in the same place as the work it changes. If the decisions live in a place nobody opens until the next QBR, you've reproduced the exact pattern you were trying to break.
The thing that quietly kills most reviews
The single most common failure mode is the steering-committee shuffle. Each function presents its slides, gets polite nods, the CEO summarises, and the room moves on. Nobody asks the question that would make the meeting useful, which is: given everything we just heard, what are we going to do differently?
That question is hard to ask because it implies someone is going to be told to stop something they were planning to start, or that a peer's pet project is going to be deprioritised in favour of someone else's. Those are uncomfortable conversations. They are also the only conversations that justify the meeting existing. A QBR that produces zero start/stop/reassign/kill decisions across three days is functionally a status meeting with catering.
What the best ones do differently
The best QBRs I've seen run on a deliberately shorter agenda — three or four objectives in genuine depth rather than seventeen at surface level. They start with the misses, not the wins, because the misses are where the learning is. They use live drilldown into the system of record rather than screenshots, so that when someone asks "what work was actually moving this KR?", the answer is on screen in the tool the work lives in. And they end not with a closing summary but with a published list of decisions, each with an owner and a date.
The format is less important than the discipline. Three days of conversation should produce somewhere between five and fifteen real decisions. If the number is closer to zero, you ran a recital.
The Vindaris view
A QBR is not a presentation layer. It's a decision layer. What survives the meeting isn't the deck — it's the change to next quarter's plan and the trace from each change back to the data that argued for it. When strategy, capacity and work all sit in one graph, the review can move in real time: someone asks why a KR slipped, the answer is on screen, the decision lands as a change to the initiative, the owner sees it before the meeting ends. The ceremony shrinks. The behaviour change grows.