A PowerPoint roadmap slide you never have to rebuild

Everyone has rebuilt this slide. Twelve rounded rectangles, four swimlane rows, a quarter divider, and about forty minutes of nudging boxes until the columns line up before a meeting. Next month a date moves and half of it has to be nudged again, which is why the roadmap slide in most decks describes a plan that was true in August.

The slide is an output, not a document

PowerPoint shapes hold no data. A rectangle doesn’t know it represents an item that moved from the second bucket to the third, so nothing about the change propagates. Every revision is a human repositioning geometry, and a human repositioning geometry at eleven at night makes the smallest change that will survive the room instead of the correct one.

Draw the roadmap somewhere that holds items, then export a picture of it. The picture goes on the slide. When the plan changes you change the item and export again, which takes under a minute and produces a slide that’s correct instead of merely defensible.

One thing worth being exact about, because product managers check: what comes out is an image sized for a slide, not a .pptx file with editable shapes. That’s deliberate. A native PowerPoint export would hand you back the same twelve rectangles to maintain by hand. A roadmap maker that gives you an image at 3840 × 2160 gives you something you never edit, which is what stops it drifting from the plan underneath it.

What belongs on the slide?

Five to seven bars, one row of quarters, and nothing else. No owner column, no status column, no percentage complete. Those are the fields that turn a portfolio conversation into a delivery conversation, and the hardest version of that audience is the one a board meeting roadmap works through field by field.

Above the image, one line of slide text saying what you’re asking for. A roadmap image on its own is a status slide; a roadmap image under a sentence naming the decision is evidence. Keep that line as text instead of baking it into the picture, so you can change the ask for a different audience without re-exporting anything.

If the deck will travel outside the company afterwards, the version on that slide is usually the wrong one to forward, and internal vs external roadmap covers what has to be rewritten before it goes.

Re-export, never edit

The moment someone edits the exported image inside the deck, the deck becomes a second source of truth, and it’s the one that gets forwarded. Within two months there are three decks with three roadmaps and no way to tell which is current.

Treat the slide as disposable. The document holds the plan; the slide holds a photograph of the plan on a particular Tuesday. When the meeting moves, take a new photograph. The same argument applies to the whole artefact rather than the single slide, and how to present a roadmap to executives covers what to do with the twelve minutes it’s on screen.

The test is whether anybody would think to open the deck to change the plan. If the answer is no, the slide is doing its job, and forty minutes a month goes back into the week.