Practice

Physical, digital and hybrid roadmapping

A design choice about how different media support participation, articulation, capture, reuse and continuing governance across the roadmapping lifecycle.

Evidence base

Empirical digital-workshop research

4 min read

Physical and digital are not maturity levels

Paper cards, sticky notes and large canvases remain effective because they minimise interface overhead. Participants can externalise incomplete thoughts, move ideas, point to relationships and read the state of the room. The medium supports a social process: cogitation, articulation, challenge and convergence. [1]

Digital tools offer different strengths: remote participation, rapid duplication, stable item identity, searchable evidence, linked views and continuity after the workshop. They can also impose friction, privilege confident users or draw attention toward operating the interface. The useful question is not which medium is more advanced, but which affordance the activity needs. [1]

Choose the medium across the lifecycle

Roadmapping has several modes of work. Exploration benefits from speed and low commitment. Synthesis needs visibility of patterns and relationships. Commitment needs ownership, rationale and explicit uncertainty. Continuation needs history, review triggers and reliable reuse. One medium rarely optimises all four.

Phaal, Chaskel and colleagues describe paper sticky notes as flexible technology for organising group dialogue, while noting that digital whiteboards can support distributed application. The important design choice is the handover: how does a provisional workshop contribution become a governed strategic object without losing its meaning? [2]

Research synthesisMatch the medium to the roadmapping activity
A lifecycle view avoids treating the workshop and the maintained roadmap as the same information problem.Original InnovationFlow visual synthesis. The underlying research concepts are discussed in Oliveira, M.G., Routley, M. and Phaal, R. (2022) [1] and Phaal, R., Chaskel, C., Gonzalez Nakazawa, R. and Ross, J. (2024) [2].

Design the workshop before choosing the interface

Clarify whether participants are generating evidence, connecting known items, selecting options or making commitments. Use prompts and visual structure to guide attention, but avoid excessive fields during divergent work. Separate facilitation roles from data-capture roles when the interface would otherwise slow the conversation. For hybrid workshops, plan how remote and in-room participants will have equivalent ways to contribute and challenge. [1]

Visual communication deserves deliberate design too. Kerr and Phaal argue that roadmap visuals should be shaped around the information and narrative required by a target audience. A working canvas can remain detailed while stakeholder views select, aggregate or restyle the same underlying content. [3]

The capture-to-continuation handover is the critical seam

A photograph preserves location but not necessarily authorship, confidence, disagreement or the reason a link mattered. Manual transcription can create a clean-looking dataset while silently dropping context. Define the handover before the workshop: which contributions remain raw evidence, which become roadmap items, who validates them, and how sources and rationale will be retained.

At organisational scale, a common data structure can integrate several roadmap narratives, reuse elements and support different stakeholder views without forcing everyone into one giant visual. Stable identities matter because a shared capability or dependency should not become multiple unrelated copies merely because it appears on several maps. [4]

What the software evidence actually says

A study of 186 R&D units in large technology-intensive Korean firms already using roadmapping found appropriate software positively associated with roadmap utilisation. “Appropriate” included availability, needed data and knowledge, usability for novice and advanced users, and integrity. That is a broader standard than attractive visualisation. [5]

The evidence is contextual and associational. Software does not replace a credible process, organisational support or strategic alignment. A useful digital environment should reduce the administrative cost of continuity while preserving the participative qualities that make roadmapping valuable. [5]

References

  1. [1]Oliveira, M.G., Routley, M. and Phaal, R. (2022). The digitalisation of roadmapping workshops. Journal of Engineering and Technology Management, 65, 101694. Source ↗
  2. [2]Phaal, R., Chaskel, C., Gonzalez Nakazawa, R. and Ross, J. (2024). Roadmapping Roadmapping: Strategic planning for roadmapping systems. Frontiers of Engineering Management, 11(3), 516–527. Source ↗
  3. [3]Kerr, C. and Phaal, R. (2015). Visualizing Roadmaps: A Design-Driven Approach. Research-Technology Management, 58(4), 45–54. Source ↗
  4. [4]Osborne, P., Routley, M. and Ilevbare, I. (2021). A Hierarchical Approach to Technology Roadmapping within an RTO Environment. Research-Technology Management, 64(3), 58–67. Source ↗
  5. [5]Lee, J.H., Phaal, R. and Lee, C. (2011). An empirical analysis of the determinants of technology roadmap utilization. R&D Management, 41(5), 485–508. Source ↗

Practitioner support

Talk to an experienced practitioner

Ask about roadmapping, facilitation or applying a method in your organisation. Your question goes directly to the InnovationFlow team.

Sent securely to hello@innovationflow.app.