Practice : Collaborative Roadmap Shaping

Purpose and Strategic Importance

Collaborative Roadmap Shaping ensures roadmaps are co-created with the people who deliver the work and those impacted by it. This practice increases alignment, trust, and engagement while improving the quality of decisions by integrating diverse perspectives.

By bringing delivery teams, product leaders, and stakeholders together in shaping the future, organisations reduce disconnects between strategy and execution and create greater collective ownership of outcomes.

Description of the Practice

  • Roadmap creation is a participatory process, not a top-down directive.
  • Workshops, planning reviews, and framing sessions are used to align on vision, priorities, and outcomes.
  • Teams contribute insights on feasibility, effort, and technical dependencies.
  • Stakeholders bring market, customer, and business perspectives.
  • The roadmap becomes a shared artefact reflecting both aspiration and realism.

How to Practise It (Playbook)

1. Getting Started

  • Invite representatives from product, engineering, design, and business to roadmap framing sessions.
  • Start with shared context: customer problems, goals, metrics, and constraints.
  • Use structured facilitation to generate and prioritise ideas collaboratively.
  • Build in time for exploration, challenge, and alignment—not just scheduling.

2. Scaling and Maturing

  • Establish a regular cadence (e.g. quarterly) for roadmap shaping and refinement.
  • Use discovery reviews or mid-cycle checkpoints to course correct as needed.
  • Make roadmap artefacts visible and accessible to all involved parties.
  • Invite feedback loops from delivery teams and stakeholders after roadmap iterations.

3. Team Behaviours to Encourage

  • Actively seek and value input from different roles and levels of experience.
  • Ask clarifying questions about value, feasibility, and outcomes before committing.
  • Share roadmap context and trade-offs transparently.
  • Collaborate with curiosity, not certainty.

4. Watch Out For…

  • Treating collaboration as consultation with no real influence.
  • Dominance of loud voices or senior roles in shaping priorities.
  • Failing to close the loop with contributors after shaping sessions.
  • Creating a roadmap that satisfies everyone’s wishlist rather than driving focus.

5. Signals of Success

  • The roadmap reflects a balance of strategic intent and delivery feasibility.
  • Teams feel ownership of and clarity around roadmap priorities.
  • Planning artefacts evolve based on feedback, not static updates.
  • Stakeholders are engaged and aligned without constant pushback.
  • Roadmap reviews spark meaningful conversations about impact and direction.