Roadmap for a sales team: what to show and what to hide

A rep will repeat what is on this view to somebody with a contract in front of them, usually inside a week, and usually without you there. That isn’t a criticism of sales. It’s the job. It does mean the filter for this view is unlike every other one on this site. The question isn’t whether sales should know something — sales should know almost everything. The question is what you can live with being said out loud to a customer with money on the table.

Quarters come off, and this is the only audience where they do

A leadership view can carry quarters because a leadership meeting has no counterparty. A deal room does. Tell a rep Q2 and the customer hears Q2, writes Q2 into their internal business case, and their procurement team asks for it in the contract. The quarter didn’t survive the trip as an estimate. It arrived as a date somebody else had already written down.

What replaces it’s sequence. A roadmap without dates sets out how to answer when with no date at all, and the short version is that Now, Next and Later degrades gracefully: when something slips, nothing was written down that now needs a correction.

The item name is a promise

An internal item is named for the work. A customer hears the name as the thing they’re going to get and fills in the shape themselves. An entitlements refactor becomes a permissions feature with an admin screen in somebody’s head, and six weeks later there’s an expectation you never set.

Rewrite the name to the problem being solved before it goes on this view. That’s the same move an external roadmap requires, and internal vs external roadmap makes the fuller argument: the two documents differ in unit rather than in field count, so hiding columns doesn’t produce the second one.

What sales gets in place of what you removed

Not less. Different, and the difference is worth stating out loud when you hand the view over.

Area stays on, so a rep can filter to the two lines an account cares about instead of reading the board aloud and volunteering the rest. Contracted milestones stay on, because a date already in a signed agreement isn’t news to that customer. Stage stays on, and it’s a better answer to when than a quarter is, because it survives being wrong.

Status comes off. Doing is relayed as nearly done every time, and the distance between those two phrases is where a renewal gets lost. Owner comes off, because a rep with a name will use it, and then the roadmap conversation restarts in a call you were not part of.

This view and a customer-facing roadmap land in nearly the same place on dates and nowhere near each other on everything else. A customer gets a rewritten name and three stages. A rep gets the area, the contracted milestones and the real sequence, because a rep has to survive the follow-up question and a published page doesn’t.

Hiding a field isn’t a wall

Say this part plainly when you hand the view over, because a rep will work it out anyway. Hiding is a property of the view. The values stay in the file, every other saved view reads them, and sending the file sends everything in it. So send the picture.

Sharing a product roadmap covers what each format gets you back. For this audience the answer is almost always an image, exported at 3840 × 2160 so it fills a slide, and re-exported when the plan changes instead of redrawn. A rep working from last quarter’s export is selling last quarter’s plan, which is a worse failure than any field you left on.