Product & Go-to-Market

Lesson 6 · Product

Roadmaps & discovery

A roadmap is a statement of intent. Discovery is how you avoid building the wrong thing.

A roadmap is a statement of intent, not a contract. Beyond the current quarter, the most honest format is Now / Next / Later: committed work, likely work and possibilities, with confidence falling as you look further out. A dated list of features a year ahead creates false certainty and locks in solutions before the problem is understood.

Organize the roadmap around outcomes — problems to solve and metrics to move — rather than outputs. “Reduce onboarding drop-off” leaves room to find the best solution; “build an onboarding wizard” does not. Discovery is the work of reducing risk before you build. Is it valuable (will they use it)? Usable (can they)? Feasible (can we build it)? Viable (does it work for the business)?

Run the cheapest test first: customer interviews, a prototype, a fake-door test, or a concierge version delivered by hand. Engineers belong in discovery. You know what is possible, and often what is cheap that nobody thought to ask for. Discovery and delivery run continuously side by side, in the same team.

Picture it

Sales asks for a “reporting module”, estimated at four months. Before committing, the team interviews eight customers and learns that seven of them want one thing: to send a monthly PDF to their boss. The team ships a scheduled PDF export in three weeks. Usage is high, the deal closes, and the other three months go to something else.

Key formulas & frameworks

Roadmap horizons
Now (committed) · Next (likely) · Later (possible)
Outcome over output
The problem and its metric, not the feature
Four product risks
Value · Usability · Feasibility · Viability
Cheapest test first
Interview → Prototype → Fake door → Concierge

Practice

Score: 0 / 5

Question 1

Q1.Which is an outcome-based roadmap item?

Question 2

Q2.A fake-door test — a button for a feature that does not exist yet — mainly tests which risk?

Question 3

Q3.A detailed, dated feature roadmap for the next 18 months reduces uncertainty.

Question 4

Q4.“Can we build this with the time, skills and technology we have?” Which risk is that?

Question 5

Q5.Engineers should take part in product discovery rather than wait for finished specifications.

Up nextEstimation & planning

Next lesson