Product Roadmaps: How the Best Product Teams Plan for Uncertainty

Teresa Torres traces how product roadmaps have evolved from feature-and-date lists to theme and outcome-based formats, arguing each fixes some problems while creating others. Feature roadmaps imply false certainty that erodes trust when broken, while theme and outcome roadmaps give teams room to explore but leave sales, marketing, and support without the specifics they need. Janna Bastow's Now Next Later format adds honesty about declining certainty over time. Torres proposes extending it by pairing Now with solutions, Next with opportunities, and Later with outcomes, drawing on opportunity solution trees. This matters because generative AI's uncertainty makes the tension between exploration and commitment sharper than ever.

01Key takeaways

• Feature-and-date roadmaps create false certainty that makes trust erode when plans inevitably change.
• Theme and outcome roadmaps protect exploration but often leave sales, marketing, and support without enough detail.
• Match the level of commitment to certainty: specific solutions for near-term work, directional outcomes for distant work.
• Put solutions in Now, opportunities in Next, and outcomes in Later to communicate progress without overpromising.
• Start incrementally by connecting current features to the opportunities and outcomes they serve.

02Key sections

Why feature roadmaps mislead

Feature-and-date roadmaps assume known durations, flawless delivery, and that every feature deserves to exist. Organizations treat them as contracts, so breaking them damages trust.

Theme and outcome roadmaps

Themes and measurable outcomes give product teams flexibility and accountability, but they fail to give other departments concrete detail, so teams drift back toward features.

Now Next Later format

Bastow's format removes dates beyond the current work, reflecting that certainty decreases over time, though teams often still fill every column with features.

Extending with opportunity solution trees

Torres maps solutions to Now, opportunities to Next, and outcomes to Later, so each column carries the right level of commitment for the audience.

Transitioning incrementally

Teams can start by linking existing features to outcomes, use missed deadlines to reframe discussions, and use AI uncertainty to justify the new format.

03From the post

“We need to talk about product roadmaps. I once worked at a startup where our product roadmap was literally an Excel spreadsheet full of feature ideas. Most of them came from our CEO. Our head of product simply prioritized the rows. Based on what, I have no idea. This is”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.