Build the product

How do I build a roadmap without over-planning?

Write it as Now, Next and Later instead of a dated Gantt chart: Now is what the team is building this cycle, Next is the few problems you will take on after, Later is what you believe matters but have not committed to, and every item is a customer problem or outcome rather than a feature with a deadline. Choose what goes in from customer feedback, company goals and effort, and re-decide every cycle, the way Basecamp's Shape Up works in six-week cycles with flexible scope. Keep it where the team already works: a spreadsheet or one slide is enough for two or three people, Jira is free for up to 10 users (Standard about $8.48 per user a month), Linear has a free plan and costs $10 per user a month above it, and ProdPad is built around Now-Next-Later. Update it every week or two; a roadmap is a direction you revisit, not a contract.

Part of Product management on eChai Explore.

Go deeper

10 resources, 10 link-checked.

▶️ Video
✓ Link checked Free Beginner

Before you can run short cycles you have to decide what goes in them, and this is a founder grade framework for that from the person who built Justin.tv and Twitch. Shear is concrete about tying each candidate feature to one or two metrics that matter. Watch it to keep your bets small and pointed instead of trying to do everything.

How to Prioritize Features

On Y Combinator Startup Library by Emmett Shear ~30 min

  • Pick one or two metrics and judge features against them
  • Say no to good ideas that do not move those metrics
  • A short focused list beats a complete plan
Open ycombinator.com →
🎧 Podcast
✓ Link checked Freemium Intermediate

The inventor of Now-Next-Later goes deep with Lenny on how to run a roadmap that stays flexible without turning into chaos. She is practical about handling stakeholders who demand dates and about pruning the roadmap so it does not sprawl. Useful once you have picked a format and need to operate it without backsliding into a wishlist.

Building better product roadmaps (Janna Bastow)

On Lenny's Newsletter by Janna Bastow, Lenny Rachitsky ~60 min

  • Treat the roadmap as a prototype of your strategy, not a plan of record
  • Answer date demands with confidence levels, not fake commitments
  • Regular pruning keeps the roadmap from becoming a backlog
Open lennysnewsletter.com →
📄 Article
✓ Link checked Free Intermediate

This is the direct answer to the pressure problem in the question: if a public roadmap scares you because of dates you cannot hit, stop putting dates on it. Bastow invented the Now, Next, Later format precisely because fixed timelines create false promises, and she walks through how to communicate direction and confidence without committing to a calendar. It is the format most public roadmaps quietly adopt for exactly this reason.

Why I Invented the Now-Next-Later Roadmap

From prodpad.com by Janna Bastow

  • Drop dates and group work into Now, Next, and Later so the further out something is, the less certain you are seen to be about it.
  • The format signals priority and direction without a deadline, which is what protects you from over-promising to early users.
  • The roadmap's real value is the conversations it starts, not the artifact itself, so treat it as a way to talk with users, not a contract.
Open prodpad.com →
📄 Article
✓ Link checked Free Beginner

Atlassian's guide to building a product roadmap: weigh ideas against customer feedback, company goals and effort, size the detail to the audience, link delivery work (epics and stories) back to it, and update it every week or two.

Product Roadmap Guide: What It Is and How to Create One

From atlassian.com by Atlassian ~10 min read

  • Prioritise from customer insight, goals and effort, not the loudest request.
  • Make the roadmap readable for its audience: too much detail gets ignored.
  • Update it weekly or fortnightly so people consult it instead of asking you.
Open atlassian.com →
📖 Book
✓ Link checked Free Intermediate

Basecamp's battle-tested, opinionated system for shipping meaningful work in fixed cycles without endless backlogs, a primary source, free in full. The antidote to over-planning your roadmap.

Shape Up: Stop Running in Circles and Ship Work that Matters

From Basecamp / 37signals by Ryan Singer free online book

  • Work in short cycles with a cool-down between them.
  • Fix time, vary scope, use 'appetites,' not estimates.
  • Make bets, not plans; no runaway backlog.
Open basecamp.com →
✍️ Essay
✓ Link checked Free Advanced

Cagan makes the sharpest version of the argument: replace a list of features with a small set of outcomes you are trying to move, then let the team find the features. It is the strongest case for a roadmap as direction rather than a shipping contract. Read it when your roadmap has quietly become a promise list to stakeholders.

The Alternative to Roadmaps

From Silicon Valley Product Group by Marty Cagan ~10 min read

  • State the outcome you want, not the feature you assume will get it
  • Most roadmap features never deliver their intended result
  • Commit to a few high integrity dates, keep the rest flexible
Open svpg.com →
📄 Article
✓ Link checked Free Intermediate

A clear tour of roadmap styles that shows exactly why a feature by date roadmap sets you up to over promise. Torres contrasts feature roadmaps with theme and Now-Next-Later roadmaps and explains what each hides or reveals about uncertainty. Read it to choose a format on purpose instead of defaulting to a timeline because it looks organized.

Product Roadmaps: How the Best Product Teams Plan for Uncertainty

From Product Talk by Teresa Torres ~15 min read

  • Feature and date roadmaps pretend to a certainty you do not have
  • Theme based roadmaps commit to problems, not specific features
  • Pick the roadmap style that matches how much you actually know
Open producttalk.org →
🛠️ Tool
✓ Link checked Freemium Beginner

Jira's plans: Free for up to 10 users, Standard at about $8.48 per user a month and Premium at about $15.56. Jira's timeline view is where many software teams keep a delivery roadmap.

Jira pricing

From atlassian.com by Atlassian Pricing page

Jira on eChai Explore

  • Free covers a team of up to 10 users.
  • Use it when engineers already track work in Jira, so the roadmap and the tickets stay linked.
  • Standard adds more automation and permissions when the team grows.
Open atlassian.com →
🛠️ Tool
✓ Link checked Freemium Beginner

Linear's plans: Free for unlimited members with 2 teams and 250 issues, Basic at $10 per user a month and Business at $16 per user a month, billed yearly. A fast tracker many early startups use for issues, cycles and project roadmaps.

Linear pricing

From linear.app by Linear Pricing page

Linear on eChai Explore

  • The free plan caps you at 250 issues, enough for an early team to try it.
  • Basic at $10 per user a month removes the issue cap.
  • Pick it over Jira when you want speed and little setup.
Open linear.app →
🛠️ Tool
✓ Link checked Freemium Beginner

If you want to actually run a Now-Next-Later roadmap rather than just read about it, this is the tool built for it by the people who invented the format. It nudges you toward horizons and outcomes instead of dates, which structurally discourages over planning. A simple whiteboard or Notion board works too, but this bakes the discipline in.

ProdPad (Now-Next-Later roadmap tool)

From ProdPad by Janna Bastow, Simon Cast software, free trial

  • Run a lightweight roadmap in the tool built for the format
  • Horizon columns discourage committing to hard dates
  • A cheap or free board is a fine substitute if you prefer
Open prodpad.com →

People also ask

Also in D2C

The same ground, over in Make your product, our D2C track.

Also in How Founders Use AI

How founders actually use AI for this, over in Vibe Coding.

eChai Partner Brands The partnership →