Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Inventory of every roadmap in circulation
Most product teams have more roadmaps than they think: a planning spreadsheet, a slide in the sales deck, a board appendix and a promise sitting in someone's inbox, each slightly different. Finding every version before building a new one shows where the contradictions are and who relies on which copy, so nothing breaks quietly when the new roadmap replaces them.
First tasks
- Search shared drives and chat for files and slides named roadmap
- List each version with its owner, audience and last edit date
- Ask sales and support which roadmap they show customers
- Ask the agent to compare the versions and list every contradiction
- Set a retirement date for each version you will replace
Roadmap purpose and audience statement
A roadmap that tries to serve engineers, executives, salespeople and customers at once usually serves none of them well. Writing down which decisions the roadmap exists to support, and which audience gets which version, settles arguments about detail and dates before they start.
First tasks
- Write the three decisions the roadmap must help people make
- List each audience and the level of detail it needs
- Decide which audiences see dates and which see only sequence
- Agree the statement with your manager or co-founder
Choosing between Now, Next, Later and a dated timeline
Timeline roadmaps look precise but turn every estimate into a promise, while a Now, Next, Later board shows sequence and confidence without inventing dates months away. Choosing the format deliberately, with your contracts, release trains and audiences in mind, avoids switching formats halfway through the year.
First tasks
- List every item that carries an external date commitment
- Mock up five current items in both formats side by side
- Write the rule for when a date may appear on the roadmap
- Record the chosen format and the reason on the roadmap page