How to present a roadmap to executives without losing the room
Open with the decision you need, not the roadmap. Show one view, filtered to the items that could change that decision, with quarters rather than dates and no owner or status column. Park execution questions in writing instead of answering them live. Twelve minutes of content for a thirty minute slot.
| Decision | When | Why |
|---|---|---|
Open with the decision you need | Always, in the first sentence | A roadmap with no question attached becomes a status update, and status updates get interrupted |
One view, not a tour | Always | Switching views mid-meeting reads as hedging and costs you the thread |
Quarters, never exact dates | Unless a date is contractual | An exact date is minuted as a commitment, and then defended instead of revised |
Hide owner and status | Unless the meeting is about delivery | Both fields redirect a strategy discussion to a single item or a single person |
Park execution questions | When the first one arrives | Answering one invites four, and the agenda is gone by the third |
Send the image, not the file | In the follow-up | A file invites edits and comments; an image is the record of what was shown |
What is the meeting actually for?
A roadmap review with leadership is a decision meeting wearing the clothes of a status update. If you open it as a status update, you will get a status update’s dynamics: line-by-line questions, one item consuming the half hour, and no decision.
So open with the decision. "I need agreement that identity comes before reporting next quarter" is a first sentence that shapes everything after it. The roadmap then has a job — it’s the evidence for that question — and items that don’t bear on the question can be filtered out without anyone feeling something was withheld.
What should be on the screen?
One view. Filtered. Quarters rather than dates, no owner column, no status column. The field-by-field reasoning is set out in roadmap for executives , and it comes down to this: every column you add is a question you have invited.
Sequence is usually the thing you’re actually asking this room to confirm, which is why a now next later roadmap template survives the meeting better than a dated layout. Its columns say what comes first without naming a day anyone can hold you to.
The instinct to bring three views and switch between them is worth resisting. It feels like thoroughness and reads as indecision. Pick the view that answers the question you opened with, and keep the others saved for the meetings they were made for.
How do you handle the question you didn’t want?
Someone will ask about a dependency, a specific date, or who is working on what. This isn’t a failure of your preparation; it’s what happens in a room of people whose job is to probe.
The move is to defer visibly. Write the question down where people can see you doing it, say you will confirm it in writing, and return to the thread. What makes this work is the writing down — a deferral that looks like note-taking reads as diligence, and a deferral that looks like a dodge reads as a dodge. Answer one of these fully and you have set a precedent for the rest of the meeting.
What about things that slipped?
Say them first, briefly, one sentence each. Two items that moved a quarter, named by you at the start, cost you almost nothing. The same two items discovered by someone reading the screen cost you the room’s trust in everything else on it.
This is also the argument for not rebuilding the roadmap by hand for each audience. A hand-rebuilt deck is a snapshot, and a snapshot is exactly what goes stale between the meeting you prepared for and the meeting you’re in. One set of items with a saved view per audience means the leadership view is current because you changed the item, not because you remembered to update a second copy — and roadmap tool alternatives is specific about which kinds of tool give you that and which hand you a second copy to maintain.
What do you send afterwards?
An image and the decision, not the file. Export the view at 3840 × 2160 and put it on one slide under the sentence you opened with. An image is a record of what was shown; an editable file is an invitation to renegotiate a plan that was already agreed in the room.
Send it the same afternoon, while the room still agrees on what was decided. A week later the decision has three versions, and the one that wins is whichever was written down first.
Common mistakes
Walking the room through every item. You’re asking for a decision, not reading a list, and the list is what invites line-by-line questions.
Bringing three views to show flexibility. It reads as not having decided which view answers the question.
Answering the first execution question fully. One thorough answer sets the format for the next twenty minutes.
Presenting the roadmap your squad uses. Owner and status belong in that view and cost you this one.
Sending the editable file afterwards. You will get suggested edits to a plan that was already agreed.
Questions
How long should a roadmap presentation be?
Around twelve minutes of prepared content in a thirty minute slot. The discussion is the point of the meeting, and it needs most of the time.
What do I do when someone asks about a specific dependency?
Say you will confirm it in writing and move on. Write it down visibly while you say so, which is what makes the deferral land as diligence instead of evasion.
Should I show what slipped since last time?
Yes, once, at the start, in one sentence each. Volunteered slippage buys credibility; slippage discovered by the room costs it.
Do I need a slide deck at all?
One image is usually enough. Export the view at slide dimensions and put it on a single slide with the decision written above it.
Related
- Roadmap for executivesFour fields to show, two to hide, and why each call goes the way it does.
- Now Next Later roadmap templateSequence instead of dates, with a board, two timelines and a table already saved.
- Roadmap tool alternativesWhat the category does better, what a local file does better, and how to tell which you need.
Last updated