Roadmapping for Startups
Introduction
Roadmapping becomes useful once a startup has achieved product-market fit (PMF). While early-stage startups often operate in a highly experimental mode, post-PMF companies can introduce enough structure to coordinate product and engineering work. This guide outlines a practical framework for quarterly roadmaps that balance product development with engineering excellence.
The key challenge in roadmapping at this stage is maintaining the startup's agility while introducing just enough process to ensure the team moves in a coordinated direction. Too much structure can slow you down, while too little can lead to scattered efforts and missed opportunities.
Below is a step-by-step process I’ve found effective for quarterly planning, with a particular focus on balancing immediate product needs with long-term engineering investments.
The Roadmapping Process
Step 1: Create the Engineering Excellence Roadmap
- Start with engineering initiatives before tackling the product roadmap.
- Compile a list of engineering excellence projects the team wants to pursue.
- Rate each project's Impact and Effort on a scale of 1 to 10.
- Include brief justifications for each rating to facilitate asynchronous feedback.
- Sort the table by
Impact/Effort - The output for this step should look like this:
| Project | Impact | Effort | Impact/Effort |
|---|---|---|---|
| Project 1 | 6 | 1 | 6 |
| Project 2 | 10 | 2 | 5 |
| Project 3 | 7 | 2 | 3.5 |
| … |
Step 2: Create the Product Roadmap
- Identify key projects that should be prioritized for the next quarter.
- Focus the team on one or two themes per quarter rather than spreading efforts across many projects.
- Rate each project's Impact and Effort, including brief justifications to enable asynchronous feedback.
- Sort the table by
Impact/Effort - The output for this step should look like this:
| Project Name | Tags | Impact | Effort | Impact/Effort |
|---|---|---|---|---|
| Project A | Product Bet | 9 | 1 | 9 |
| Project B | Product Excellence | 7 | 1 | 7 |
| Project C | Customer commitment | 6 | 1 | 6 |
| … |
Step 3: Estimate team capacity
Account for these often overlooked time commitments:
- On-call and customer success work
- Planned vacations and holidays
- Onboarding new team members
- Any team offsites or planning days
- Unexpected PTO
Step 4: Combine and draw a cutline
- Bring the top projects from Step 1 into the doc for Step 2.
- Save at least 30% of the bandwidth for Engineering Excellence work, although this varies from startup to startup.
- Based on the capacity in Step 3, you’ll be able to see the cutline of what you can realistically accomplish.
- Do not change a score simply to move a project above the line. If a commitment or strategic constraint overrides the ranking, label that decision explicitly and explain why.
- Alternatively, look for ways to break work into two parts: a smaller first part that meets the immediate need and a second part that can be deferred.
- The output of this step should look like the following table:
| Project Name | Tags | Impact | Effort | Impact/Effort |
|---|---|---|---|---|
| Project A | Product Bet | 9 | 1 | 9 |
| Project B | Product Excellence | 7 | 1 | 7 |
| Project 1 | Eng Excellence | 6 | 1 | 6 |
| Project C | Customer commitment | 6 | 1 | 6 |
| … | ||||
| [Cutline] | ||||
| Project 2 | Eng Excellence | 10 | 2 | 5 |
| Project 3 | Eng Excellence | 7 | 2 | 3.5 |
Step 5: Make it official
I like using Initiatives and Projects in Linear to record and execute on the roadmap. Whatever tool you use, publish the chosen priorities, owners, and the reasoning behind the cutline. Revisit the roadmap as assumptions change.
A roadmap is not a prediction. It is an explicit set of choices based on the best evidence the team has today.