5 Questions I Ask Before Every Quarterly Business Review (That Nobody Taught Me to Ask)

Four hours. That was the number. Every quarter, I blocked my Sunday afternoon — the whole thing — to build the QBR deck. I pulled numbers from Salesforce, cross-referenced pipeline data in HubSpot, chased down three department heads who hadn't submitted their updates, reformatted fourteen slides, and wrote a narrative that made the quarter look coherent. By 9pm, I had a deck the CEO could walk into Monday morning feeling prepared. Then I watched him spend the first forty minutes of the QBR reacting to numbers most of the room had already seen in their weekly dashboards.

The meeting ended with seventeen action items. By the following Thursday, four of them had owners. By the next month, the rest had quietly dissolved.

I did this eight times before I changed how I prepared. Not the deck. Not the data. The questions I asked before I opened a single spreadsheet.

McKinsey found that 61% of executives say the time they spend making decisions is ineffective. I believe it. I watched it happen in my own QBRs for two years. The fix was not better data or a sharper deck — it was five questions that turned the meeting from a reporting session into a decision session. I cut my prep from four hours to under two and walked out with six action items instead of seventeen. All six got done.

Question 1: What decisions have to be made before next quarter starts?

This is the question that changed everything. Before I started asking it, my QBR decks were comprehensive. They covered every metric, every department update, every goal status. They were also completely undirected — a reporting exercise disguised as a strategic meeting.

Now I start here. I Slack two people: the CEO and the CFO. One question each: "What do you need to decide before Q3 locks in?" The answers are usually concrete and surprisingly short. Shift the enterprise pricing tier. Decide whether to backfill the VP of Customer Success or restructure. Commit to or kill the APAC expansion pilot.

Those decisions become the deck's skeleton. Every slide exists to arm the room for one of those decisions. Data that does not connect to a decision does not make the deck. This single filter cut my last QBR deck from thirty-one slides to fourteen. The meeting ran forty-five minutes instead of ninety. Every action item left the room with a name on it.

Question 2: What has actually changed in our priorities since the last QBR?

Most QBR decks present the current quarter's goals as if they were set in stone at the beginning and tracked cleanly through to today. That is almost never what happened. Priorities shifted in week four. The CEO came back from a board meeting with a new urgency around profitability. The product roadmap pivoted after a key customer churned.

I now map every priority shift that happened mid-quarter — to give the room an honest picture of what they actually spent three months doing versus what they planned to do. The gap between those two things is the single most important data point in any QBR, and it almost never appears in the deck.

The last time I ran this exercise, I found three priorities that leadership had informally abandoned by mid-quarter without formally updating anyone's OKRs. Twelve people were still working against goals the leadership team had already moved past. That slide — three abandoned priorities, twelve people still running — generated more discussion than every metric slide combined.

Question 3: Where are we genuinely off-track versus where does the data just look off-track?

There is a specific kind of slide I stopped including in my QBR decks: the red-yellow-green status grid with no interpretation. A goal marked "yellow" tells the room nothing. Is it yellow because the number is slightly behind a target that was set aggressively? Or is it yellow because a critical dependency fell through and the initiative is functionally dead?

I spend thirty minutes before every QBR calling the owners of every "yellow" and "red" item. One question: "If I put you in front of the CEO, what would you actually say about this?" The answers split cleanly into two categories: genuinely off-track (needs a decision or a resource reallocation) and cosmetically off-track (the metric looks bad but the initiative is healthy).

Separating those two categories before the QBR saves the room from spending twenty minutes debating a yellow that everyone on the ground already knows is fine. It also forces the room to focus on the items that need intervention — the ones that require an actual decision, not a discussion.

Question 4: What does leadership need to stop doing this quarter?

This is the question nobody wants on the slide. It is also the one that produces the highest-value conversation in every QBR I have run since I started including it.

Every quarter adds initiatives. Very few quarters remove them. By Q3, most leadership teams are carrying commitments from three previous planning cycles, each of which was supposed to be the year's top priority. Nobody says the word "stop." Everybody just absorbs more.

I now include one slide with a single header: "Recommended Stops." Three items, maximum. Each one is an active initiative or operational commitment that I believe the leadership team should formally close, pause, or hand off. I include the estimated cost of continuing — not in dollars, but in senior attention hours per week. The last time I ran this slide, one initiative was consuming eleven hours per week across four directors. It had been deprioritized informally two months earlier. Nobody had said the word out loud.

The "stop" conversation is uncomfortable for about ninety seconds. Then it becomes the most productive part of the meeting.

Question 5: What does our Q3 plan assume that isn't true yet?

This is the question I save for last — partly because it takes the most preparation, and partly because it is the most uncomfortable. Every forward-looking plan contains assumptions: that a hire will close by a certain date, that a product ship will land on time, that a partnership will convert, that the market conditions in the board deck still hold.

I list every assumption I can find in the Q3 plan. Then I mark each one with a confidence level: confirmed, likely, or uncertain. The uncertain ones go on a slide titled "What We're Betting On." That slide does not argue against the plan. It simply makes the bets visible.

The first time I did this, the CFO thanked me after the meeting. Not because I had found a problem — because I had made explicit something the entire room was unconsciously relying on. Two of the five assumptions I flagged turned out to be wrong by mid-Q3. The team was already watching for them because they had seen the slide.

A plan built on invisible assumptions is not a plan. It is a hope with a spreadsheet attached.

The shift that matters

I still build QBR decks. They are shorter now — fourteen to eighteen slides instead of thirty-plus. Prep takes about two hours instead of four. But the real change is not in the deck. It is in the meeting.

A QBR designed to report produces slides. A QBR designed to decide produces outcomes.

The moment it clicked for me was the first QBR where nobody asked "can you pull up the numbers for…" — because every number in the deck was already there to answer a decision the room had agreed it needed to make. No orphaned data. No discussion without a destination. I left that meeting at 10:45am instead of noon, and for the first time, the Sunday before a QBR belonged to me again.

If you are running QBR prep this month, ask these five questions before you open a single slide. The deck you build will be different. The meeting will be different. And the Sunday before it might finally be yours.

Try it free at rhythms.ai.

Frequently Asked Questions

How do I stop spending four hours building the QBR deck every quarter?

Start by asking what decisions the QBR needs to produce — not what data it needs to present. When you scope the deck around three to five decisions, the data you need to gather shrinks dramatically. The hours are not in the formatting. They are in collecting data you did not need in the first place.

What is the difference between a QBR that reports and a QBR that actually produces decisions?

A reporting QBR sequences through metrics and updates, then ends with a list of action items. A decision QBR starts with the decisions that need to be made and organizes every slide around arming the room for those decisions. The prep is different, the deck is shorter, and the outcomes are specific. Most QBRs default to reporting because nobody asks "what are we deciding?" before the deck gets built.

How do I get leadership to actually complete QBR action items?

Every action item needs three things before it leaves the room: a single named owner (not a team), a specific deadline (not "next quarter"), and a visible tracking location. If any one of those is missing, the item will not be completed. I went from seventeen action items with four owners to six action items with six owners. The completion rate went from roughly 25% to over 80%.

How do I handle pushback when I shorten the QBR deck from thirty slides to fifteen?

The pushback comes from people who equate thoroughness with length. I frame it as: "Every slide in this deck arms you for a specific decision. If a slide doesn't connect to a decision the room needs to make, it's not adding value — it's adding time." Most executives come around once they experience a forty-five-minute QBR that produces six clear outcomes versus a ninety-minute QBR that produces seventeen items nobody owns. Run it once. The results make the case.