• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Practice : Now–Next–Later Roadmaps

Purpose and Strategic Importance

Now–Next–Later Roadmaps offer a simple, adaptive structure for communicating strategic intent without overcommitting to speculative future work. This format balances clarity of direction with the flexibility to respond to learning and change.

By focusing detail only where needed and avoiding false precision, teams maintain alignment with stakeholders while preserving their ability to pivot. It supports lean roadmapping practices and aligns strategy with agile execution.


Description of the Practice

  • Roadmap items are grouped into three evolving time horizons: Now (in flight), Next (likely to happen soon), and Later (ideas or options).
  • Items in “Now” are delivery-ready and well-defined.
  • “Next” represents prioritised, near-term work requiring further refinement.
  • “Later” is a space for opportunities, ideas, or bets still under evaluation.
  • This format supports frequent roadmap review and adjustment without having to replan entire timelines.

How to Practise It (Playbook)

1. Getting Started

  • Map current initiatives into the Now–Next–Later structure.
  • Limit “Now” to active delivery work and avoid bloating it with too much.
  • Treat “Next” as the focus area for shaping, refining, and stakeholder engagement.
  • Use “Later” to hold ideas that are not yet committed, while signalling strategic direction.

2. Scaling and Maturing

  • Review and update the roadmap as part of quarterly planning or release cycles.
  • Integrate metrics or OKRs to connect items to measurable outcomes.
  • Use “Later” to engage teams in exploration, experiments, or technical spikes.
  • Visualise the roadmap in a collaborative tool and make it accessible across the organisation.

3. Team Behaviours to Encourage

  • Revisit the roadmap regularly and adjust based on learning.
  • Invite input from delivery, product, ops, and stakeholders when shaping “Next”.
  • Clarify that items move between zones based on readiness and insight—not rigid dates.
  • Treat the roadmap as a conversation, not a contract.

4. Watch Out For…

  • Using “Later” as a dumping ground without review or pruning.
  • Planning too much in “Now”, limiting flexibility.
  • Assuming “Next” items are guaranteed—be clear that they’re probable, not promised.
  • Failing to communicate how and why items move across zones.

5. Signals of Success

  • Teams and stakeholders can clearly see what’s being worked on and what’s coming.
  • Roadmap conversations focus on priorities, not dates.
  • There is a healthy flow of items moving from “Later” through to “Now”.
  • The roadmap stays current, relevant, and aligned with strategy.
  • Changes in direction feel natural, not disruptive.

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering