Building the Product

How do I build a roadmap without over-planning?

A starting point

Work in short fixed cycles with variable scope, Basecamp's Shape Up runs on six-week bets, not a rigid multi-quarter Gantt chart. Make a few bets you can finish, avoid a runaway backlog, and re-decide every cycle based on what you learned. A roadmap is a direction, not a contract.

Go deeper

Read

📖 Book
Free Intermediate

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

From Basecamp / 37signals by Ryan Singer free online book

Why we picked it

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.

  • 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 →
📖 Book
Paid Intermediate

Continuous Discovery Habits

From Product Talk by Teresa Torres ~240 pages

Why we picked it

The standard modern playbook for keeping discovery continuous so roadmap decisions stay grounded in real customer input, not one-off research. Exactly what founders need to stay close to users while shipping.

  • Start from a clear desired outcome.
  • Interview customers weekly to surface opportunities.
  • Use an opportunity solution tree to visualize and align your decisions.
Open producttalk.org →

People also ask

How do I decide what to build next? Prioritize outcomes, not output, and use a simple scoring frame like RICE, Reach x Impact x Confidence, divided by Effort, to compare ideas honestl... Intermediate 2 resources → How often should an early-stage startup ship? Ship weekly, at least, cadence is a competitive advantage because faster loops mean faster learning. You haven't really started until you launch, a... Beginner 2 resources → How do I keep talking to users while I'm heads-down building? Make discovery continuous, not a one-time phase: interview a customer or two every single week, even in a build sprint. Teresa Torres's opportunity... Intermediate 2 resources → How do product teams keep a consistent shipping rhythm as they grow? Separate your planning cadence from your execution cadence and lean on async updates instead of endless meetings. A predictable operating rhythm, w... Advanced 2 resources → How do I say no to feature requests without losing customers? Anchor every 'no' to the outcome you're chasing and the customers you're building for, most requests are solutions in disguise, so dig for the unde... Intermediate 3 resources →