PRODUCT NOTES
A Roadmap That Isn't a Wish List: Now, Next, Later for Early-Stage Startups
How to build a Now, Next, Later roadmap for an early-stage startup that links each item to an outcome and helps you say no.
Many startup roadmaps are lists of features with dates attached. They look organized, but they break the first time reality changes. A better approach for early-stage teams is a Now, Next, Later roadmap, built around outcomes rather than dates.
Why dates cause trouble early on
When the product, the market and the team change quickly, dates become promises you cannot keep. Missing them costs trust. A roadmap that shows order and confidence is more honest than one that shows false precision.
The three columns
Now (the next four to six weeks). Work that is being built or about to start. Specs are written, owners are named, and the team has capacity.
Next (the following one to three months). Work you intend to do after Now. Direction is clear, details are not.
Later (beyond that). Problems and opportunities you are watching. No promises on timing, and the list can change.
What goes in each item
Each item should answer four questions:
- Problem: what are we trying to solve, and for whom?
- Outcome: what should change if we succeed?
- Evidence: why do we believe this matters (customer conversations, data, support requests)?
- Confidence: how sure are we? (low, medium, high)
An item without a problem and an outcome is an idea, not a roadmap entry.
A template
NOW
- Problem / Outcome / Evidence / Confidence / Owner
NEXT
- Problem / Outcome / Evidence / Confidence
LATER
- Problem / why we are watching it
How to keep it honest
- Limit Now. If the Now column has more items than the team can finish, it is a wish list.
- Tie to a goal. Each item should connect to the goal for the current period.
- Move items by decision, not by drift. When something moves to a different column, write down why.
- Review monthly. Update the columns, drop what no longer fits, and note what changed.
Using it to say no
A roadmap makes it easier to answer requests. Instead of "no", you can say: "That is a fair idea. Here is where it sits and what would need to change for it to move up." The answer is clear and respectful, and it shows the reasoning.
Signs your roadmap is a wish list
- Items have no stated outcome.
- The Now column is longer than the team can deliver.
- Nothing has ever moved to Later.
- Items are included because one person asked.
- No one can explain why the order is what it is.
Share it, but carefully
Share the roadmap with the team and, where it makes sense, with customers. Describe it as a statement of current thinking and direction, not as a list of commitments. That keeps trust high when plans change.