Run the roadmap review as a decision meeting or do not run it

The failure isn’t that the meeting is badly run. It’s that most roadmap reviews have no decision in them, so the hour is spent producing the appearance of oversight. Everyone leaves having heard the status of thirty items and made no calls, and the next month’s invitation gets accepted with slightly less attention than the last one.

The agenda is the diff

Ninety percent of the board didn’t change since last time. Reading it aloud spends the hour on the part nobody had a question about and leaves no room for the part that needs a decision.

Send three lines the day before: what moved, what was dropped, and the one or two calls you need made. The roadmap stays on screen during the meeting as the evidence behind those three lines, not as a script. When someone asks about an item that didn’t change, the answer is short and you return to the thread.

If you can’t fill the third line, there’s no meeting. Cancel it and send the current view with a note. This is the part people resist, and it’s the part that determines whether anyone prepares for the review in March when something genuinely has to be decided. A recurring meeting that reliably decides nothing trains its attendees to arrive having read nothing.

Can two audiences share the hour?

No, and the attempt produces one meeting about delivery. Delivery detail always wins the room, because it’s concrete and because there’s usually someone present who is anxious about a specific date.

The squad review is about what is blocked and what moves this sprint. It needs owner, status and dependencies. The leadership review is about sequence and investment, and those fields actively get in the way of it. At a quarterly cadence the second meeting has its own field list again, set out in roadmap for a quarterly business review, and the presentation mechanics are in how to present a roadmap to executives.

Running both from the same set of items with two saved views is what makes this practical. Two separate documents is what makes it collapse back into one meeting, because maintaining the second document stops being worth anyone’s time by about week six.

Decisions land before the hour ends

A decision written up afterwards is a decision that gets relitigated, because the write-up is one person’s account and everyone else remembers the caveats differently.

Change the document while people are in the room. Move the item, drop the item, mark the bucket. Ten seconds of screen sharing turns a discussion into a record, and the record sits where people will look for it rather than in a document nobody opens. It also removes the update task entirely, which is the cheapest version of the argument in how to keep a roadmap up to date.

If the structure fights you here, that’s a signal in itself. A goal-oriented roadmap template puts the call where the meeting needs it: every item sits under the goal it’s meant to move, so "drop this" and "this supports nothing" turn out to be the same sentence, and it takes one move to act on. A layout that needs re-plotting takes long enough that you defer it, and deferred changes are how the document and the decision come apart.