Sharing a product roadmap: link, file, or picture
Pick the format by what you want back. An image is a record and gets you questions. A file is an invitation and gets you edits. A live link is current and gets you people reading it without the context you gave in the room. Send the image, keep the file.
| Decision | When | Why |
|---|---|---|
Send an image | After a meeting where the plan was agreed | An image is the record of what was shown, and it cannot be edited into a different agreement |
Send the file | To someone who has to build on it, such as a peer product manager | They need the items, not a picture of them, and they are not the audience who renegotiates |
Share a live view | To a squad that watches it weekly | They need current, and they have the context to read a change as a change instead of a broken promise |
Write the decision above the roadmap | Every share outside your squad | A roadmap forwarded without its question is read as a commitment list by whoever gets it third |
Never share the internal view outward | Always | Owner and status turn a plan discussion into a performance one, and a forwarded copy loses the room that could have corrected it |
Three formats, three different replies
The format you pick determines the response you get, and most of the frustration with sharing a roadmap comes from picking one format and expecting the other one’s response.
An image is a record. It can’t be changed by the person holding it, so what comes back is questions. That’s the right reply after a meeting where something was decided, because the decision isn’t reopened and the questions can be answered in writing at your own pace.
A file is an invitation. Handing someone a document they can open in an editor is an implicit offer to let them change it, and people take the offer. What comes back is suggested edits to a plan that was agreed an hour ago, which you then have to decline one at a time.
A live link is current. What comes back is people reading whatever it says on the day they open it, without the framing you gave in the room. For a squad that looks at it weekly that’s exactly right. For a stakeholder who looks twice a year it’s how a replan gets discovered instead of explained.
Send the picture, keep the file
The default after any meeting outside your squad is the image, with the decision written above it in the body of the message. Not attached, not in a footer. A roadmap that travels without its question is read as a commitment list by the third person it reaches, and by then there’s nobody in the thread who was in the room.
Export at slide dimensions so it survives being pasted into a deck, which is what will happen to it. The mechanics of that, and why a hand-drawn version goes stale first, are in roadmap slide in PowerPoint .
The file goes to people building something on top of it: a peer product manager planning around your sequence, a programme manager assembling a portfolio view. They need the items themselves, and a picture won’t do, and they aren’t the audience that renegotiates.
What never goes out as it stands
The squad’s working view. Owner and status are the two fields that convert a discussion about sequence into a discussion about a person, and once the file has been forwarded there’s no room available in which to correct the reading. Which fields survive which audience is set out in roadmap for executives , and the rewriting required before anything reaches customers is in internal vs external roadmap .
Sales is where this goes wrong fastest, because a quarter read off a slide is repeated to a customer the same week and written into their business case the week after. Roadmap for sales team is specific about which fields come off before it leaves your building.
One copy, several views
The tempting shortcut is a tailored copy per audience: one for leadership, one for the squad, one for customer success. Each copy is accurate the day it’s made and wrong by the following month, and the one that goes wrong first is always the one you look worst holding.
Saved views over a single set of items remove the problem rather than managing it. A swimlane roadmap template is a useful structure underneath when the readers are spread across teams, because the lane somebody cares about is the one thing they can find without being told, and the rest of the work stays on the page instead of being filtered into invisibility.
Pick the format for the reply you want, send it once, and let the next version be a new export rather than a correction.
Common mistakes
Sending the editable file after the decision. You get suggested edits to something that was already agreed.
Sharing a live link and assuming people saw the version you meant. They will see whatever it says the day they open it.
Forwarding without the question it answers. Two forwards later it’s a list of commitments with no author.
Keeping a separate copy per audience. Each copy is correct on the day you make it and wrong by the next meeting.
Questions
Is a live link ever right outside the squad?
For a peer team that checks it weekly, yes. For anyone who will look at it twice a year, no. The second group needs the version you meant, and a live link gives them the version that exists the day they open it.
What format should go to a customer?
An image of an external view, with the rewriting done first. Sending an internal file outward is the most common version of this mistake and the hardest one to take back.
Should I password-protect a shared roadmap?
If it matters that much, don’t send it. Access controls on a document that has already been forwarded once are a record of intent. They aren’t a control.
How do I stop people working from an old image?
Put the date on it and re-send when it changes. An image with a visible date is self-correcting; an undated one gets quoted two quarters later as though it were current.
Related
- Roadmap for executivesFour fields to show, two to hide, and why each call goes the way it does.
- Roadmap tool alternativesWhat the category does better, what a local file does better, and how to tell which you need.
- Internal vs external roadmapDifferent documents, not one with columns hidden. What to rewrite before the roadmap goes outside.
Last updated