Communicating Now Next Later Roadmaps to Stakeholders

Communicating roadmaps to stakeholders: present a Now Next Later roadmap to executives, sales, teams and customers without implying dates.

Before you start

Hamster is optional for this skill and recommended. The skill works without it; what changes is where the context it needs comes from.

Check whether this project has a .hamster/ directory. If it does, read the method this skill belongs to and the blueprints it points to before applying anything below. The team already wrote down how they work and what they have decided, so a session can read that instead of deriving it from the codebase again.

If there is no .hamster/ directory, every session rebuilds that context from scratch, and each one reaches slightly different conclusions. Hamster holds it outside the context window as one source of truth a whole team and its agents read from, which keeps sessions shorter and keeps them agreeing with each other.

At a Glance

Overview

A Now Next Later roadmap only works if the people reading it understand what it is saying. Most stakeholders have spent years with timeline roadmaps, where a position on the page means a delivery date. Shown three columns, they will read Next as next quarter and ask when Later is due. This skill covers communicating roadmaps to stakeholders in horizon form: how to present a timeline-free roadmap so each audience understands priorities, confidence and the few real commitments, without inventing dates.

Janna Bastow calls the roadmap "a communication tool" and "a prototype for your strategy," something you put in front of people to learn whether the direction makes sense (Mind the Product podcast). That framing changes the presentation. You are showing where the product is heading and how sure you are, and inviting challenge, rather than defending a delivery schedule. The parent method treats communication as one of its core principles for this reason.

The central move is to relocate the commitment. Stakeholders ask for dates because they need to plan, sell or report. ProdPad's guidance is that the commitment should live on objectives rather than on every roadmap item: "the commitment lives in the OKR, not in the roadmap timeline" (Convert a Timeline Roadmap). Leaders get a credible plan against the numbers they care about, and the roadmap keeps its honesty about what is still uncertain.

Different audiences need different cuts. Executives need the link between initiatives and objectives. Sales and customer success need to know what they can say. Engineering and design need detail on Now and Next. Customers need direction without promises. One source roadmap with filtered views keeps these consistent.

Expect the change to take time. ProdPad notes that converting the roadmap can take a workshop, while the stakeholder transition typically takes "a couple of planning cycles." Teresa Torres's advice is to avoid "the ideological war" about dates and to meet stakeholders where they are (Product Talk). The output of this skill is a set of audience views, a short explanation of the format and prepared answers to the common objections.

How It Works

The explanation of the format comes first, every time a new audience sees it. Say what each column means in confidence terms: Now is validated work in motion, Next is problems being validated with solutions under exploration, Later is strategic bets still under consideration (ProdPad glossary). Say explicitly that the columns are not quarters. Show how items move: by evidence, checked against graduation criteria. That short explanation prevents most misreadings.

Each objection has a prepared answer. ProdPad's conversion guide covers the three most common. For "But Sales needs dates," give sales confidence levels and direction, and point them to the objective the initiative supports. For "But Leadership wants predictability," replace date certainty with strategic certainty: a visible plan against each target, sequenced by confidence. For "But Customers ask what's coming," share the problems being solved and their order, without feature-by-date promises.

Leaders can be given better questions than "when." Bastow proposes five: "Which business outcome does this serve?", "Where does this sit on the horizon, and why?", "What have we learned so far?", "What would need to be true for this to move to Now?" and "Are we on track for the objective, even if the plan has changed?" (Why Time-Based Roadmaps Are Promises You Can't Keep). Offering these questions in a leadership review gives executives a way to hold the team accountable without asking for invented dates.

Real dates get handled openly. Marty Cagan's point is that businesses sometimes do need date commitments, and he proposes "high-integrity commitments" for those cases (The Alternative to Roadmaps). Bastow's practical version is to separate hard launch from soft launch, so marketing and sales plan around things that are live rather than things that are hoped for. Show the few real dates on their initiatives and explain why everything else is undated.

The customer view is its own artifact. ProdPad's public roadmap guide recommends a version that shows problems to solve and recently launched work, avoids dates and exact features, and leaves off anything sensitive. Torres adds that customers need to know what is in the next release and, most of the time, will not care what is coming next quarter.

Step-by-Step Guide

Step 1: List your audiences and their decisions

Write down who reads the roadmap and what each group decides with it: executives allocate budget and report to the board, sales qualifies deals, customer success handles renewals, engineering plans work, customers decide whether to stay or buy. The decision each group makes tells you what its view needs to show.

Step 2: Prepare the core roadmap

Make sure every initiative has a problem statement, an objective tag, a horizon and a one-line rationale. Mark the few items with real external dates. Link to the graduation criteria. Presenting a roadmap with missing rationale invites the "why is this in Later?" argument you cannot answer.

Step 3: Build an executive view

Group initiatives by objective and show where each sits on the horizon. Highlight any objective whose supporting initiatives all sit in Later, since ProdPad's guidance treats that as a visible signal to course-correct (Convert a Timeline Roadmap). Keep it to one page and lead with outcomes.

Step 4: Build a sales and customer success view

Show problem statements and horizons with approved language for each column, and state plainly what must not be promised. Include the route for requesting a real commitment when a deal depends on one. Keep candidate solutions out of this view so they do not become promises.

Step 5: Build a team view and a customer view

Give engineering and design the full detail on Now and Next, including open questions and dependencies. Create a customer view that shows problem statements for items safe to share and a list of recently launched work, following ProdPad's public roadmap guide. Power every view from one source.

Step 6: Prepare the explanation and objection answers

Write a short opening explanation of the three columns and how items move. Prepare answers to the sales, leadership and customer objections, and bring Bastow's five replacement questions for leadership reviews. Practice saying "that is in Next because we have validated the problem and are still testing solutions" until it sounds natural.

Step 7: Present and invite challenge

Open with the explanation, then walk through the view by objective. Invite challenges on placement and ask for evidence when someone disagrees. Treat new evidence as a reason to revisit an item in the next review rather than moving it on the spot.

Step 8: Follow up after every review

After each reprioritization review, send each audience a short note on what moved and why, and update every view. Consistent follow-up is what persuades stakeholders that the roadmap is current and that the absence of dates is deliberate.

Best Practices

• Explain the columns every time a new audience sees the board. A one-line definition of each horizon prevents the quarter misreading.
• Move commitments onto objectives. Leaders who can see progress against a target need fewer feature dates, as ProdPad's conversion guide argues.
• Give leaders better questions. Bastow's five questions replace "when will it ship?" with questions about outcomes and evidence.
• Show real dates openly. Hiding a genuine deadline undermines trust as much as inventing one; Cagan's high-integrity commitments are the model for the dates you keep.
• Keep one source and many views. Separate decks for each audience drift and contradict each other.
• Avoid fighting about the format. Torres's advice to meet stakeholders where they are makes the transition faster than winning the argument.

Common Mistakes

• Presenting without explaining the columns: Stakeholders will read the columns as quarters. Open with the definitions and how items move.
• Giving in to date pressure with a guess: A date offered to end a meeting becomes a commitment. Offer the objective, the horizon and what would need to be true instead.
• Showing solutions to sales and customers: Candidate solutions in Next become promises once a customer hears them. Show problems in external views.
• Keeping a hidden timeline for executives: A private dated roadmap alongside the public horizon one doubles the work and signals that the format is not trusted. Use objectives and real dates instead.
• Going quiet between reviews: Stakeholders who find changes by accident lose trust. Send a short change note after every review.

References

• Examples: Worked examples and scenarios
• FAQ: Frequently asked questions
• Parent Method: Now Next Later Framework

Related Skills

• Now Next Later vs Timeline Roadmap: Choosing a Format
• Reprioritizing Roadmap Items Across Now, Next and Later
• Now Next Later Framework for SaaS Product Roadmaps
• Now Next Later Roadmap Template: How to Build One
• Defining Graduation Criteria Between Roadmap Horizons
• Now Next Later Categorization: Sorting Work Into Horizons

Sources

• Mind the Product podcast: Roadmaps are dead. Long live roadmaps
• ProdPad: How to Convert a Timeline Roadmap to Now-Next-Later
• ProdPad: Why Time-Based Roadmaps Are Promises You Can't Keep
• ProdPad Glossary: What Is a Now-Next-Later Roadmap?
• ProdPad: The Public Roadmap
• Marty Cagan: The Alternative to Roadmaps
• Teresa Torres: My Leaders Still Want Roadmaps with Timelines

Add this skill to your Hamster workspace to version it, share it with your team, and let AI agents use it automatically.