Roadmapping as process
It is often said that "the process of roadmapping is more important than the roadmap itself", as useful as the roadmap is for supporting strategic understanding, communication and alignment. This is attributed to the consensus building nature of the process when used to mediate strategic dialogue, often in the form of workshops. Consensus, while beneficial, brings with it some risks, so a healthy strategy should be subject to challenge. For example, Motorola in their original 1987 technology roadmapping approach required a 'minority report' to be submitted with roadmaps, developed through a consensus building process.
How to balance and blend human and digital in such processes is an interesting question. It's clear there is a spectrum of options, with successful deployments observed at both extremes, and in between, and that digital technologies and applications - hard and soft - continue to develop rapidly.
How long does it take to develop a good roadmap? Between 2 hours and 2 years, it has been observed - it depends on how clear your strategy is. A pair of scissors and some glue are quite useful if presented with a glossy and substantial strategy document - if the strategic plan is complete and coherent, it should not take long to create a roadmap to accompany it.
It's not a good idea to confuse your roadmapping process with your strategy or innovation management process (or any other process for that matter), which it is prone to be, because of its visible integrative nature - roadmapping supports these other business processes; it has limited impact by itself. The unique distinguishing feature of roadmapping is the use of structured visual representations as a primary management lens, and its role is best understood through this perspective. The core principles of roadmapping are simple, which is helpful for dealing with complex business and system challenges, at least initially, as a diagnostic. A single tool alone is limiting, and so a toolkit approach is advocated.
As an executive from Philips was heard to say "roadmaps are dirty mirrors", meaning they will reveal the good, the bad and the ugly. This makes roadmapping a useful diagnostic, especially the first iteration, with a need to moderate expectations if the process reveals problems that have to be dealt with before a satisfactory roadmap can be developed. Don't blame the messenger - roadmapping, or brush the problems back under the carpet. "If you can't see it, you can't manage it" - as a structured visual approach roadmapping can help.
To be effective roadmapping must align with and support other key business processes and tools, together with the associated information flows, aligning stakeholder perspectives, decision making and resource allocation. The figure below shows how an hypothetical roadmapping workshop supports a larger roadmapping initiative, which in turn serves a business process - typically strategy or innovation. Of course, the situation in reality is much more complex in large organisations, and a substantial mapping activity may be required. Shown in red below are key success factors from a study of foresight (sector) roadmapping applications (De Laat & McKibbin, 2003), which are also useful for firm level applications.
Starting up a roadmapping process / system is different to sustaining it, which is notoriously challenging. The limiting factor is the underlying strategic coherence in the organisation and its management and business systems, rather than the roadmapping method itself. Roadmapping is rather simple in nature, and can help to address the complex situations that arise in organisations over time. "Think big, act small" is a good way to start, with it generally making sense to initially focus on the human process, beginning with a meeting and/or workshop to scope the initiative, test the tool and address a strategic problem of concern or as a diagnostic. Aim to deliver early benefits and understanding of how the method can help, how it should be configured, and to agree the way forward. White boards, paper, post-it notes and pens are a good starting point, progressing to more sophisticated systems as appropriate.
Beyond diagnostics and problem solving, deployment of roadmapping in an organisation is a process in itself, and change management frameworks are helpful, as demonstrated by Gerdsri et al. (2009), who break down the process into three stages: Initiation, Development and Integration.
Technology-intensive innovation poses particular challenges that are often overlooked in standard product and service innovation literature and teaching programmes. Technological invention and innovation is uncertain and risky, and can take a long time - it is unwise to rely on unproven technology for a product development if time and cost targets are critical. Similar management frameworks can be applied to both product and technology development - for example, innovation 'funnel' and Cooper's stage-gate frameworks, used with NASA's technology readiness levels (TRLs) to assess technological progress and align the two development processes. The layered structure of roadmaps helps to distinguish between and synchronise research and development projects with product releases, upgrades and commercial milestones, and also different technology development clock speeds (e.g. software vs hardware).
'Fast-start' workshop methods
Cambridge 'S-Plan' and 'T-Plan' 'fast-start' workshop methods are designed to efficiently support the initiation of roadmapping in organisations of all types, as reference processes to adapt from. They can also be used to support review and renewal of existing roadmapping initiatives. Workshop methods are designed to be modular, flexible and scalable, enabling toolkit configuration and deployment.
Methods are based on generic frameworks that can be readily adapted to context in terms of process and structure. The underlying roadmap architecture is neutral to process, which can be overlaid on the roadmap canvas. Process prompts can be embedded into workshop templates to support utility, as demonstrated here.
Light-touch 'fast-start' methods were initially developed for application in small organisations, as there was a perception in the late 1990s that technology roadmapping was the preserve of large technology firms. This is not the case at all, although of course a small start-up will need a very different solution to an established multinational. An impressive long-running national (Singaporean) SME initiative has been reported by Holmes and Ferrill (2005), adapted from the T-Plan approach, with training provided to support transfer of the approach.
Efficiency is also valued by larger firms, particularly when trialling a new method. Roadmapping can always be expanded as required, as it is integrated into management systems, at business, corporate, sector or national levels. Two diverse examples of large corporate applications are provided below - both multinational first-tier suppliers of similar scale (annual revenues of about $10B), in very different sectors.
It is helpful to include all relevant stakeholder groups in workshops - particularly technical and commercial, and possibly strategic customers and suppliers. This can lead to large numbers of participants and facilitation challenges, with methods needing to adapt to group size and task, as illustrated below. The 'self-facilitating' templates for small groups are designed to empower users, improve process efficiency and effectiveness, and to relieve the burden on facilitators, freeing up time to focus on higher value support activities. Medium-sized groups require engaged facilitator attention, whilst large groups demand a more orchestrated approach.
At the other end of the scale, roadmapping is a useful framework for personal reflection, to organise strategic thoughts, and as a research tool - retrospectively, used successfully in several research projects. Roadmapping provides a useful design and planning framework for facilitator and key stakeholders, to clarify focus and scope ('the exam question'), and to gather data and organisational information.
Roadmapping, as with other such approaches, must usually be adapted to fit the specific context, with implementation within a business unit taking some time - up to a year or two is not uncommon. Corporate deployment is even more challenging (as described by Cosner et al., 2007), and rarely observed for reasons not of the tool's making, but rather due to the general challenges of deploying any coherent strategy process in a complex and political environment. For these reasons it is not uncommon to find pockets of successful roadmapping in organisations, often unconnected, focusing on parts of the system that managers can influence.
Roadmapping is an ideal tool for senior managers concerned with strategic alignment, from the board level down. However, as it is very seldom included in standard business textbooks and teaching programmes, many of those who would benefit most from the approach know little about it. This inexplicable omission is one motivation for this website, to provide information and support that is unlikely to be available from your local business school.