Roadmap for a quarterly business review: what to show and what to hide

Every other roadmap on this site answers what is coming. A quarterly business review asks a different question first: what did you say in April, and what happened. Build the view for that question and the field list follows from it.

The practical consequence is that the window matters more than the fields. Two quarters behind, two ahead. A view starting at the current quarter looks like the check was avoided, and the room will notice before you finish the first slide.

Why leave the shipped work on the screen?

Status stays on, collapsed to shipped or not shipped. This is the only audience for whom done is information rather than noise. The whole point of the hour is reconciling intent against outcome, and a clean run of completed items is the fastest way to stop the room asking a question you have already answered.

It also does something a verbal summary can’t. It shows the shipped work in the same place, at the same scale, as the work that slipped. A list of accomplishments read aloud gets discounted. The same items sitting in Q2 alongside the two that didn’t land is a picture nobody argues with.

Mark the committed dates as milestones while you’re there. Those are the only items anybody will check line by line against the last review.

Name what left, before somebody else does

The items that disappear between one QBR and the next are the ones a finance lead notices, because they were in the numbers. An item removed without comment reads as an item hidden, and you will spend more of the hour on it than the removal ever deserved.

So keep a short list of what was dropped and why, and say it early instead of waiting to be asked. Keeping a roadmap up to date makes the general case for recording what left. At a QBR it’s closer to mandatory, because the previous version of the document is in the room with you.

An outcome-based roadmap template is built around both halves of this. Items sit under the measure they were funded to move, which is the reconciliation the meeting is for, and dropped bets stay on the board as a view of their own rather than being deleted and remembered.

This is also what separates this meeting from the monthly one. Run the roadmap review as a decision meeting : bring the diff, get the calls made, cancel it when there’s nothing to decide. A QBR is a reconciliation, and its audience sat in none of those monthlies.

Two fields that turn a review into an appraisal

Owner comes off. A quarterly review with names attached stops being a discussion of what happened and becomes a discussion of who let it happen, and the room then plans next quarter with that conversation still in the air. Say the credit out loud instead. It lands better from you than from a column.

Notes come off for a subtler reason. Whatever the squad wrote for itself reads as pre-emptive defence when somebody sees it cold, and a slip you were going to explain in one sentence becomes the subject of the hour.

Dependencies come off too. The slips worth explaining get named with their cause, and an arrow invites a re-plan the hour can’t hold.

Do not rebuild it for the deck

Build the view once, export the image, drop the image in. The moment somebody redraws the picture in slideware it stops matching the file, and the discrepancy surfaces while you’re standing in front of it. A PowerPoint roadmap slide you never have to rebuild covers the mechanics — the export is 3840 × 2160, sized so a 16:9 frame takes it whole, and re-exporting next quarter is a ten second job.

Hiding owner and notes is a view setting, not a deletion. The values stay in the file and the squad’s own view still reads them. Which is the quiet advantage of doing it this way: next year’s QBR is this year’s file with the window moved, and the version you’re being asked about is still in it.