Product Management Craft · 18 min · 130 XP

Roadmaps as outcomes, not dates

Build a roadmap of problems to solve, more certain near-term than long-term, that communicates direction without promising dates you can't keep.

A roadmap is a communication tool. Its job is to tell the team, the company and sometimes customers where the product is heading and why. The classic failure is the feature-and-date Gantt chart: twelve features with twelve delivery dates, a year out. It's out of date within a month, every slip feels like a broken promise, and it commits the team to solutions before anyone has learned whether they solve anything.

Now, Next, Later: certainty drops as you look further out

NOW (committed, in progress)
  Finance can see who approved each invoice
    → measured by: approved-invoice share

NEXT (likely, being explored)
  Invoices get paid faster
    → candidates: reminder emails, card payments on invoice

LATER (direction, not commitment)
  Small teams run all their billing here
    → open: multi-currency, accountant access

Two changes make a roadmap honest. Write outcomes, not outputs: “invoices get paid faster” instead of “build reminder emails”. That leaves the team free to find the best way to get there, and makes it obvious when something shipped but didn't work. And let certainty fade with distance. A Now/Next/Later format says plainly that this quarter is committed, next quarter is likely and anything after is direction. Put a date on an item only when something outside the team really depends on it, such as a regulation, a contract, or a conference launch.

Different audiences need different views of the same roadmap. Engineers need the Now column in detail. Sales wants to know what they can talk to customers about, which usually means Now only, because promising Later items to customers turns them into commitments. Executives want to see how the roadmap connects to company goals.

A roadmap that never changes is a warning sign. If learning from discovery and launches never moves anything, the team either isn't learning or isn't allowed to act on it. Review it on a regular schedule, monthly or quarterly, and say what changed and why.

Do it this week: rewrite your team's current roadmap into Now, Next and Later, with each item as an outcome and the measure beside it. Notice which items you can't phrase as an outcome: they may not have a reason yet.

Loading your workspace…