Roadmap for a board meeting: what to show and what to hide

Everything read aloud at a board meeting is written down by somebody whose job is to write it down. That single fact settles most of the field list. A roadmap in this room isn’t a plan being reviewed. It’s evidence attached to a financial narrative, and every line on it becomes a line a director can return to next quarter with the minutes open in front of them.

So the working question isn’t what the board would find interesting. It’s what you’re willing to be asked about in ninety days.

A board is allocating capital, not reviewing product

Group by area and the picture answers the question the board arrived with: where the money is going and what is expected back. Six items is usually the whole roadmap at this altitude, one or two per area, each one a bet large enough that somebody funded it deliberately.

That second half — what is expected back — is the part most roadmaps can’t show, because nothing on them names the result. A goal-oriented roadmap template puts the goal above the work and the target beside the goal, so the six items arrive already attached to what they were funded to move, and an item attached to nothing is visible before a director finds it.

A leadership meeting takes a looser filter than this one, because that audience can act on more of the list week to week. A board acts on roughly three things: money, hiring, and whether to keep going. Anything that fails that test comes off the view — not out of the file, off the view.

Status is the field that creates work

A director carries a duty to oversee. That’s the difference between this room and every other one, and it changes what a red chip means. In a squad meeting, blocked is information. At a board, blocked is an item the board is now on record as having seen, which means somebody has to be able to say what was done about it. You have handed them an obligation and yourself a follow-up.

The same logic covers dependencies. An arrow between two bars invites a re-sequencing conversation in a room with no delivery context, and what comes out of it arrives as a request you have to decline formally instead of quietly.

Owner is the third. A name on the screen belongs to somebody the board has never met, and the question that follows is rarely about the work.

The dates a board already has

There’s one exception to hiding dates, and it’s narrow: a commitment that already exists outside the company. A regulatory deadline, a contract go-live, an announced launch. These are dates the board either knows or should, and marking them as milestones tells them which parts of the plan have no slack in them.

Everything else is a quarter. The distinction between a roadmap and a committed schedule is worth being explicit about in the room, and roadmap vs project plan is the version of that argument you can send afterwards to whoever asks for dates in writing.

The version you actually maintain

You don’t build a board deck. You keep one set of items carrying owners, status and real dates, and save a view that draws six of them at quarter resolution. Hiding a field is a property of the view: the value stays in the file, every other view still reads it, and sending the file sends everything in it. Export the view as an image at 3840 × 2160 and it fills a 16:9 frame without cropping.

If the meeting itself is the hard part rather than the artefact, how to present a roadmap to executives is the longer treatment.

One thing the file buys you that a deck doesn’t: the roadmap json format is published, so what the board saw in March is a diff away instead of a memory. Every board follow-up is some version of what changed, and answering it from a record instead of a recollection is the difference between a short item and a long one.