The only question worth asking
Did anything change because of this meeting?
This was the note we ended Part 1 with. That question is crucial for both designing and measuring the effectiveness of the meeting.
Who needs to be in the room
In my experience, for meetings that involve “high level folks”, the general instinct is to include everyone who might be believed to have a stake. If those leaders extend the invite to their second and third levels, in a company of five hundred people, the invitee list burgeons to thirty to forty people in a single room, and on the teleconference bridge.
That by itself may not pose a problem. The core issue though is that many of those people cannot tell why they are there. Most are there because their boss asked them to be there. Some are there because they were there in the same meeting last quarter.
But all of them are there because nobody thought carefully enough about who actually needed to be part of such a critical business cadence.
The most effective QBRs have a different starting point. Someone (we will get to that soon) asks two questions before the invites go out. What decisions actually need to get made in this meeting? Who has the authority, context, and accountability to make them?
Those two questions naturally produce two groups. The people who can say yes or no and have it mean something. And the people with ground-level visibility into what is actually happening with customers, product, and numbers. The second group brings the information. The first group acts on it. There is of course a third group that is needed to make all this machinery work smoothly, but let’s leave them out of the picture for now.
Everyone else is probably better served by a summary of meeting minutes and a well-managed action items log.
The tendency of some leaders to walk into the room with a small army of their next layer people needs a special mention. It signals several things happening in the background, and that would be a longer conversation. However, at minimum, it indicates that either the leader has not internalized their own material before showing up. Or they seriously need to reduce their reporting span.
What belongs on the agenda
How many teams truly run through a meeting agenda at the beginning of a meeting and have some sort of self-correction mechanism in case the meeting starts running away from the set agenda?
It is easier to talk about the failure modes here as well. The runaway agendas that consistently fail in meetings have one thing in common. Nobody stopped to ask what each item was supposed to produce, or what it needed to even be discussed properly.
Items get added because they feel important, or because a leader pushed for airtime, or because they were on last quarter’s agenda and nobody thought to question them. By the time the QBR starts, we have a deck covering twelve disparate topics with ninety minutes of room time and zero clarity on which of those twelve things actually needs the leadership team in a room together.
What’s left then? The agenda that is specific and actually needs attention from the assembled forum. Decisions that need to be made, challenges that require the full leadership team’s visibility and cross-functional transparency for a resolution, commitments that need to be reviewed or renegotiated. Of course, there must be a sufficiently deep retrospective on past business performance, which many teams either skip entirely or spend too long on.
Mere status updates that don’t lead to a decision are better consolidated in a pre-read and circulated at least 24-48 hours before the QBR. Context-setting for topics needs to happen before the QBR, not during it. When it happens during the meeting, it is usually a sign that the pre-read didn’t get sent, or didn’t get read, or both.
A simple thumb rule might be in order here. Before an item gets added to the agenda, ask what decision or commitment it requires. If the answer is vague, that vagueness needs to be resolved with the relevant teams before the QBR, not inside it.
That being said, there is one category that gets inconsistent space on the agenda, though it is probably the most important one. The QBR is the one moment in the quarter where the full leadership team is in the same room with the full picture of a business. The mere cost of the meeting demands that it be used for crucial purposes like setting or aligning all teams on strategic issues. Using some of the allotted time to account for what already happened is important, but a good portion of the agenda has to be looking forward.
Even if that look ahead is included, it cannot be a cursory “thoughts on next quarter?” that gets five minutes at the end, when the room is already mentally elsewhere. A real conversation with the actual stakeholders on whether the priorities going into the next quarter still hold, given what just played out in the past quarter.
If the invite list was done right, that forum has the exact context needed to answer such questions. To be clear, the QBR is NOT the place to set strategy from scratch. It is a forum to get alignment from different functional leaders and stakeholders on the strategy and also to decide what needs to shift in the execution layer to reflect the alignment.
Tracking whether anything actually changed
Walk out of most QBRs and ask someone what got decided. They might give you a reasonable answer. The same question asked six weeks later will get answers that are fuzzy. A week before the next QBR, many people are quietly hoping nobody brings up those decisions.
Commitments get made during the meeting. Usually, a facilitator records the details of the commitment, who owns it, what done would actually look like, and when it is due. The meeting ends and the action item tracker gets circulated. And then three months later, the same topic gets back on the agenda with a slightly different title. These days AI agents handle the recording and tracking of the action items, but the phenomenon of action items getting defocused over time and quietly deprioritized isn’t going away.
Commitments without a single owner are just shared hopes. A named team is not a named person either. Someone specific has to own it, even when there are efforts needed from multiple teams, with a clear definition of what done looks like and a timeline for its completion.
The tool matters far less than people think. A shared tracker that everyone can actually see between quarters will do more work than an elaborate project management setup that nobody opens until the week before the next QBR. Missed commitments are an operational issue. Not just a cultural or tool issue.
The obvious discipline that separates well-run QBRs from the rest: the opening of every QBR goes through what happened to last quarter’s commitments as the first agenda item. If that review becomes consistently uncomfortable for the gathered forum, it is telling you something about the organization that the rest of the meeting will not. That alone deserves an operational health check.
What might have been a priority inside the QBR quickly drops down in importance once it hits the actual owner’s list of things to do, especially if it is not a burning item that has a lot of eyeballs on it. With time, it simply gets buried in the business-as-usual stuff. A well-designed QBR process has an inbuilt, periodic tracking mechanism for commitments, driven by the meeting’s key facilitator, who is given the authority and visibility to enforce it across functions.
On Time
A QBR with twelve large agenda items, no pre-circulated context, and blocked for three hours on the calendar is not a time management problem. It is an operations and design problem.
One common mistake is to allocate time by function, though it is logical and sufficient for certain levels of operational maturity. However, when Finance gets thirty minutes because finance is important, Product, Sales & Marketing each get thirty minutes for the same reason, there is no time left on the clock to talk about items that actually needed real discussion.
A more useful, active management method is to allocate time by decision weight. How much discussion does this item actually need for a clear decision? Some items might need ten minutes. Some would need forty-five. The function it comes from is largely irrelevant.
Rabbit holes deserve a special mention again. They kill QBRs faster than almost anything else, and I have observed that they are surprisingly hard to interrupt in the heat of the moment. It becomes that much harder still when the person digging is also one of the senior people in the room.
The discipline of saying “this needs a separate conversation with the right people” is a simple one, in principle. In practice, this makes the role of the facilitator that much more critical.
The QBR process needs its owner. And its movers.
Most high stakes meetings have a visible power gradient. Many a time, the most useful signal tends to come from people who are least likely to offer it without prompting. This is not a problem specific to QBRs. But it gets amplified by the very nature of a QBR, where the stakes are higher, the audience is larger, and the cost of saying something uncomfortable takes different but real forms.
Circulating a pre-read is an obvious solution, but inviting written observations or questions before the meeting works well to streamline the QBR. It prevents people from formulating their views under pressure during the QBR. Having a pre-agreed plan on who will address each agenda item, instead of letting the loudest voice fill the space, would also make the flow easier.
All of this hinges upon having a facilitator who is not the most senior person in the room. Finding someone with the gravitas to fill that role without making it feel like a demotion for the room’s senior leader is harder than it sounds. Inside the QBR room, the facilitator’s authority on keeping to the process should remain absolute. And that buy-in should be gotten across the board, so that there are no awkward looks, silences and temper tantrums in the room when the facilitator attempts to bring a derailed discussion back on track.
None of this is complicated. However, many organizations don’t do it because the QBR was never deliberately designed. It is simply a practice that gets built through accumulation of requirements over time, inherited from whoever ran it before, with each iteration changing as little as possible on structure or outcome.
The closing question, again
Did anything change because of this meeting?
If yes, what changed? Who owns it? When will it be visible?
Part 3 is about what a well-designed QBR starts revealing once it is running properly.
And why that can be an uncomfortable thing to look at.