The typical mid-market QBR is a two-day sequence of forty-five-slide decks, read aloud to people who already approved the contents in the pre-read. The leadership team nods, the function heads sit down feeling validated, the CEO summarises, and the room files out. Six weeks later, nobody can point to a decision that came out of those two days. Next quarter's plan looks substantially like last quarter's plan with the numbers updated.
That isn't a review. That is a recital. And recitals are an unusually expensive way to fill a leadership calendar — especially when the actual purpose of a QBR is supposed to be the opposite of recitation.
Why QBRs default to performance
The drift toward theatre is structural, not personal. A status-deck QBR optimises for two things: looking good, and not getting interrupted. Neither is the actual point. The point is a small number of decisions about what the company should do differently in the next ninety days.
The reason most QBRs can't get to those decisions is that the data the deck is built on lives in five different tools, was reconciled by hand the week before, and cannot be drilled into in the room. So when someone asks the obvious question — "what work was actually moving this KR?" — there's no answer. There's a screenshot at best. The meeting cannot get below the headline, so the meeting becomes the headline, so the only thing the room can do is take it on faith and move on. If you cannot drill from a missed KR to the work that was supposed to move it within thirty seconds, the meeting is structurally incapable of producing a real decision.
The model that changes behaviour
A QBR built around traceable work has four parts, in this order.
The first is a pre-read with the data, not the conclusions. The numbers, the work that was tagged to each KR, what shipped, what slipped, what got quietly deprioritised. No narrative arc, no recommended decisions, no hero shots. The narrative is what the meeting is for. If the pre-read already contains the conclusion, the meeting is just a place to read it out.
The second is one question per objective, asked plainly: what changed, and what should we do about it? If the honest answer is "nothing changed and nothing should change," the objective was not a real bet — it was a long-running task with a number attached. Real bets generate movement, in one direction or the other, and the conversation is about what to do with that movement.
The third is live drilldown, not slides. When someone asks "what work was actually moving this KR?", the answer is on screen in the same tool the work lives in. Not a screenshot of last week's status. The system. If you can't do this, your tooling is the bottleneck, and the rest of the format won't save you.
The fourth is a written decision register. The meeting ends with an explicit list of decisions — start, stop, reassign, kill — captured in the same place the work lives. Not a Google Doc. Not a Notion page nobody opens until the next QBR. Attached to the initiatives and KRs the decisions concern, so the system reflects the new plan by the end of the meeting.
What traceable work actually buys you
It buys you the ability to answer, in the room, three questions that a status-deck QBR cannot:
For each KR you missed, what work was tagged to it, who owned it, and where did it actually go? You discover, more often than you'd expect, that the KR you missed had almost no real work pointed at it. The miss wasn't an execution failure. It was a staffing failure that nobody flagged at the time.
For each KR you hit, what work moved it, and is that work continuing into next quarter or done? You discover that some of your "wins" were really one-time pushes that nothing is sustaining. The KR will quietly regress next quarter unless you do something about it now.
What work shipped this quarter that wasn't tagged to any strategic objective at all? This is usually the most interesting list in the room. The unattributed-work column is your honest map of where the company actually spends itself — independent of what the strategy deck said you'd do. If a meaningful share of last quarter's shipped work points at nothing strategic, the question isn't whether to ship less of it. The question is whether the strategy is wrong, or whether the operating system isn't translating it.
Why the format keeps slipping back
The decks come back because they're safe. A live drilldown can fail in public. A traceable system can show a leader's function in a worse light than their narration would have. Decision registers create accountability that lives past the meeting. Every part of this is uncomfortable for the people who benefit from the recital. Which is, of course, the point of replacing it.
The Vindaris view
A QBR is not a presentation layer. It is 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 work that argued for it. When strategy, capacity and the underlying work all sit on one surface, the QBR stops being something you prepare for and becomes something you can actually run from: live, drillable, and honest about where the bets and the bandwidth currently disagree.