Most Quarterly Business Reviews fail before the first slide loads.
Not because the data is wrong. Not because the presenter is unprepared. They fail because someone confused a QBR with a status update. One is a report. The other is a conversation with stakes. If you walk in with a slide deck full of metrics and no narrative holding them together, you will lose the room in twelve minutes and spend the next forty fighting to get it back.
Here is what I have learned from building and delivering QBRs across enterprise HR technology accounts: the structure matters less than the story. But the story still needs a structure.
Start With Their Reality, Not Your Data
The temptation is to open with platform stats. Resist it.
Before a single number appears on screen, your client needs to feel understood. That means framing the review inside a context they recognise. Where does their organisation sit on the maturity curve? What were the priorities they walked in with at the start of the quarter? What has changed in their business environment since you last spoke?
I use the Bersin HR Maturity Model as an opening anchor in my QBRs, not to lecture the client, but to give both sides a shared language and a shared sense of position. When you can say “you have achieved operational and standardised maturity, and here is precisely where the optimisation gap sits,” you have transformed data into a position. That is a conversation worth having. Clients who see themselves clearly on a maturity curve are far more receptive to capability recommendations than clients who have just been handed a usage report.
The opening of a QBR should make the client nod, not scroll.
Build a Spine, Not a Slide Stack
Every strong QBR has a single narrative spine. One thread that runs from the opening context through the data and into the recommendations. If you pulled any three slides from your deck and read them in isolation, a stranger should still be able to sense the direction of travel.
A structure that works, and one I follow consistently:
Strategic context — Where are they now, and what does that mean?
Platform health — Is the technology performing as expected?
Workforce signals — What is the data telling us about people risk?
Module engagement — Where is adoption strong, and where is it stalling?
Gaps and opportunities — What is subscribed but unused? What is the cost of that gap?
Prioritised recommendations — Not a wish list. A sequenced action plan.
Decision and next steps — What needs to happen, by whom, before next quarter?
Notice that recommendations are not bolted on at the end as an afterthought. They are the destination the entire deck has been building toward. Every section before it earns the right to that conversation. When the structure is right, the client does not feel sold to at the end. They feel like the recommendation was inevitable given everything they just saw.
Use Data to Surface Tension, Not Just Progress
Good QBR storytelling creates productive tension. It does not just celebrate wins. It names the gap between where the client is and where they need to be, and then offers a credible path forward.
This is where most account managers play it too safe. They show the green metrics, skim the amber ones, and avoid the red entirely. That is a mistake. Clients are not looking for a cheerleader. They are looking for a trusted advisor who will tell them what the data actually means.
In my QBRs, I go module by module and assign RAG scores against adoption benchmarks. Every module gets a status — not just the ones performing well. When a client sees that their Helpdesk has zero tickets raised despite nearly a thousand employees on the platform, that number lands differently than it would buried in a table. It is a blind spot. I name it clearly, explain the implication, and then pivot immediately to the fix. That sequence — problem, implication, recommendation — is the storytelling unit that makes the rest of the deck credible.
The same discipline applies to workforce analysis. I do not just show attrition headcount. I break it down by department, by hire type, by exit reason, and by tenure band. When a client can see that a single department accounts for a third of all permanent exits in a quarter, and that department happens to be revenue-facing, the conversation about predictive analytics ceases to be a nice-to-have. It becomes a business case they write themselves.
That shift — from vendor presenting data to client drawing conclusions — is the mark of a QBR that actually changes something.
Prioritise Ruthlessly
One of the most common QBR failures is the kitchen sink recommendation list. Fourteen action items across eight modules, presented with equal urgency and no sequencing. The client leaves feeling overwhelmed instead of directed.
My approach: every recommendation is categorised as Critical, High, or Medium, and the closing section is structured around that hierarchy. Three urgent actions that need to happen now. Three quick wins that can be configured this week with zero cost. Three goals for the coming quarter with measurable targets attached.
That structure does two things. It tells the client exactly where to focus their limited attention and political capital. And it creates a natural accountability framework for the next QBR, because now there are nine specific, time-bound commitments you can open with next time. Progress becomes visible. Accountability becomes mutual. The relationship moves from vendor management to genuine partnership.
Make the Close Impossible to Ignore
The final slide is not a thank-you. It is a decision document.
I close every QBR with named actions, named owners, and named timeframes. If a module is subscribed and unused, the close says so directly — here is the opportunity cost, here is the configuration effort, here is who needs to sign off. Vague commitments do not survive the journey from the meeting room back to the client’s desk.
When a client leaves a QBR with a list of three things they have personally committed to doing in the next two weeks, the probability of those things happening is orders of magnitude higher than when they leave with a general sense that “things went well.” The close is where the story becomes action. Treat it accordingly.
The best QBRs end with the client reaching for their notebook, not their phone.
One Last Thing
The QBR is ultimately a test of whether you understand the client’s business well enough to have an opinion about it. Not just to report on it. Anyone can pull usage stats and put them on slides. The differentiator is the ability to look at platform data and see the people story underneath.
Attrition numbers tell you talent is leaving faster than the organisation can absorb it. Unused modules tell you there is a gap between what HR has invested in and what they are actually using. Low onboarding completion rates, when placed alongside early exit data, tell you the retention leak begins on day one, not at the resignation letter.
The QBR is your moment to say: here is what I see, here is what it means, and here is what we do about it. Show up with that, and you will never lose the room.
Leave a Reply