An organization that runs a well-built QBR process can learn a lot from it over time.
The agenda is fixed. The right people are in the room. The flow is managed well. The action items have owners and dates. The meeting ends on time.
The QBRs start showing certain patterns, over time. About the organization.
A well-run QBR is like an X-ray
In a poorly run QBR, the patterns of dysfunction stay hidden below the noise of the meeting itself.
But a QBR that is run well enough surfaces patterns over time that go beyond numbers and trends.
It will show how decisions actually get made versus how the org chart says they should. Where real information lives and who holds it. Which commitments get kept and which ones keep slipping into the next quarter’s agenda, sometimes with a different title.
Data preparation
Getting the numbers ready for a QBR is a tedious task in many places. More than being a preparation problem stemming from disconnected systems, it indicates that the organization does not have a trusted source of truth of its own performance.
On top of this, different functions arrive with different numbers for the same metric. They are not wholly correct or wrong. Each team typically reports from their point of view.
Of course, the problem with that is each one is showing a different slice of the same thing, and no one ends up seeing the whole.
Sales sees the pipeline from the front. Finance sees revenue from the back. The middle, where the actual business is happening, belongs to no one’s report or is too fragmented.
When data eventually centralizes into a single visible system, the integrity of numbers and how they were derived becomes even more important.
For example, data shows 25% of the customers who churned left because their feature request got ignored. Then a deeper cut of the data shows that only 20% of all churned customers have even bothered to give a reason why.
It is not the purpose of the QBR to judge which number is correct. That should be sorted out before the review happens. The data (or the gaps in them) always reflects the state of the processes feeding it. When the source becomes visible, the clean-up moves to the processes rather than their outputs.
Decision-making
QBRs quickly reveal how and where decisions are actually made in your organization.
When every small decision gets deferred to the most senior person in the room, regardless of topic, it means that the decision rights are either unclear or do not match the accountability structures that exist on paper. Both are fixable but only after being seen and acknowledged as a problem.
Decisions that get made in the room but resurface, often predictably, before the next QBR indicate a different issue. Either the decision was made with insufficient or incorrect information, or the people who needed to own it were not in the room when it was taken.
Forecasts and feedback
Looking at the retrospective of a single quarter’s forecast against the actual numbers in a review can tell you several useful things on its own. But a person who has sat through three or four cycles of those reviews can learn a lot.
It is not so much about whether one person or team was right or wrong about their forecasts for a given time period. A leader who walks in with a good grasp on where the data is pointing to, what the gaps are, why the gaps look the way they do, and what to expect, cuts a very different picture as compared to one whose outlook revises itself quietly and repeatedly as results come in.
For the CEO in the room, this forms a valuable signal over time: an indication of which leaders have a grip on their numbers and which are the ones reporting a version of reality.
Culture dynamics
Observing who speaks or remains silent during the QBRs helps form a reasonably accurate map of the organization’s actual power dynamics.
The person who is able to control the narrative regardless of what is shown in the deck. The senior leader who reacts aggressively to bad news. The function head who consistently brings up certain cross functional issues but deflects similar concerns from their peers. The team that never surfaces a problem until it is made visible through expensive escalations.
Organizations develop these patterns because their work ecosystem rewards them over time. If a QBR has not been deliberately designed for honesty, it will become just a periodic performance, and prove to be extremely damaging in the long run.
The pattern that matters most
After a few quarters of well-run QBRs, there is one pattern that will surface clearly: which commitments get kept, by whom and within what time periods.
Commitments that keep slipping reveal more about either the organization’s capacity, its prioritization discipline, or its willingness (or inability) to say no in the room. An organization or even just one team that consistently over-commits and under-delivers, or where the commitments evaporate within days or weeks, has much deeper problems than just accountability.
On the other hand, an organization or team that delivers on everything it commits to in a QBR consistently is either genuinely healthy, or it has quietly learned to commit only to things it was already going to do anyway.
What to do with what you see
The QBR is not the place to fix every challenge it reveals. The purpose of a QBR is to make the right signals visible. The actual work of addressing them happens outside that room, in the weeks that follow.
Whether the organization is honest enough to act on what it sees is a different test altogether.