1. Process

The technology roadmapping process may be conducted in three phases: preliminary activities, the development of the roadmap, and the follow-up activities phase. Because the process is too big for one model, the phases are modeled separately. In the models no different roles are made; this is because everything is done by the participants as a group.^[1]

Phase 1: Preliminary Phase

Figure 1. The process-data model of the preliminary phase. File:Phase1.3 Process Data Model.jpg - HandWiki

The first phase, the preliminary phase (see figure 1), consists of 3 steps:

1. satisfy essential conditions,
2. provide leadership / sponsorship, and
3. define the scope and boundaries for the technology roadmap.

In this phase the key decision makers must identify that they have a problem and that technology roadmapping can help them in solving the problem.

Satisfy essential conditions

In this step it must become clear what the conditions are (they must be identified) and if they are not met, who takes actions to meet them. These conditions include, for example:

• A need for the technology roadmap
• Input and participation from different parts of the organization (e.g., marketing, R&D, the strategic business units) with different planning horizons and perspectives.

All conditions should be satisfied (or an agreed-on party takes necessary actions) to continue to the next step. The participants can have zero or more conditions of their own. It applies to all conditions that have the attribute to be met or not.

Provide leadership / sponsorship

Committed leadership is needed because of the time and effort involved in creating a technology roadmap. Additionally the leadership should come from one of the participants, one of them provides leadership and sponsorship. This means that the line organization must drive the process and use the roadmap to make resource allocation decisions.^[2]

Define the scope and boundaries

In this step the context for the roadmap is specified. In the company a vision should exist and it must be clear that the roadmap can support that vision. If the vision does not exist one should be developed and clearly stated. When that is done the boundaries and the scope of the roadmap should be specified. Furthermore, the planning horizon and the level of details should be set. The scope can be further divided into the technology scope and the participation scope.

In table 1 all the different sub-activities of the preliminary activity phase can be seen. All the sub-activities have concepts as end products (marked in bold). These concepts are the actual meta-data model, which is an adjusted class diagram.^[3]

1.2. Phase 2: Development Phase

Figure 2. The process-data model of the development phase. Phase2.3_Process_Data_Model.jpg (929×900) (handwiki.org)

The second phase, the development of the technology roadmap phase (see figure 2.), consists of 7 steps:

1. Identify the "product" that is the focus of the roadmap,

2. Identify the critical system requirements and their targets,
3. Specify the major technology areas,
4. Specify the technology drivers and their targets,
5. Identify technology alternatives and their timelines,
6. Recommend the technology alternatives that should be pursued, and

7. create the technology roadmap report.

Identify the product focus of the roadmap

In this step the common product needs are identified and are agreed on by all the participants. This is important to get the acceptance of all groups for the process. In case of uncertainty of the product needs scenario-based planning can be used to determine the common product needs. In figure 3, the participants and possibly the scenario-based planning provide the common product needs.

Identify the critical system requirements and their targets

Once it is decided what must be roadmapped, the critical system requirements can be identified; they provide the overall framework for the technology roadmap. The requirements can have targets (as an attribute in figure 3) like reliability and costs.

Specify the major technology areas

These are the areas that help achieve critical system requirements. For each technology area several technologies can be found. Example technology areas are: market assessment, crosscutting technology, component development, and system development.

Specify the technology drivers and their targets

In this step the critical system requirements from the second step are transformed into technology drivers (with targets) for the specific technology area. These drivers are the critical variables that select the technology alternatives. Drivers depend on the technology areas but they relate to how the technology addresses the critical system requirements.

Identify technology alternatives and their timelines

At this point the technology drivers and their targets are specified and the technology alternatives that can satisfy those targets should be specified. For each of the alternatives a timeline should be estimated for how it will mature with respect to the technology driver targets.

The time factor can be adapted suitable for the particular situation. The time horizons for e-commerce and software related sectors are usually short. Other distinctions can be made on scale and intervals.

Recommend the technology alternatives that should be pursued

Because the alternatives may differ in costs, timeline, etc., a selection must be made of the alternatives. These are the alternatives to pursue in figure 3. In this step a lot of trade-offs must be made between different alternatives for different targets: for example, performance over costs and even target over target.

Create the report

At this point the technology roadmap is finished. In figure 3, it can be seen that the technology roadmap report consists of 5 parts:

1. the identification and description of each technology area,
2. critical factors in the roadmap,
3. unaddressed areas,
4. implementation recommendations, and
5. technical recommendations.

The report can also include additional information. In table 2 all the different sub-activities of the development phase can be seen.

1.3. Phase 3: Follow-Up Activity Phase

This is the moment when the roadmap must be critiqued, validated and hopefully accepted by the group involved in any implementation. This requires a plan developed using the technology roadmap. Next, there must be a periodical review and update point, because needs from the participants and the technologies evolve.

2. The Fast-Start Approach to Roadmapping

Given the potential complexity and organisational inertia surrounding the creation of roadmaps, researchers at the University of Cambridge^[4] focused on developing a fast-start approach to roadmapping.^[5] This approach, called T-Plan, was created in the late 1990s primarily to help organisations take the first step into roadmapping with minimal resource and time commitment. It has been influential in the propagation and uptake of roadmapping internationally including translations of the T-Plan workbook^[6] into Chinese (traditional & modern), German, Japanese and Spanish. The approach (as well as its counterpart for innovation and strategy roadmapping, S-Plan) is flexible and scalable, and therefore can be easily customised for efficient application.^[7] Fast and lean approaches are particularly important for small and medium enterprises (SME) and have been shown to work in particularly to give directions to clusters of SMEs.^[8]

3. Planning and Business Development Context

5. Programme planning example. Purpose_programme_planning.jpg (440×218) (handwiki.org)

6. Bars example. Format_bars.jpg (402×279) (handwiki.org)

7. Graphs example. File:Format graphs.jpg - HandWiki

The process of technology roadmapping fits into corporate strategy, corporate strategic planning, technology planning and the business development context. Three critical elements should be connected: needs, products, and technology.

3.1. Knowledge and Skills Required

Consultant with skills

Creating a technology roadmap requires certain knowledge and skills. Some of the participants must know the purpose of technology roadmapping. Next to this group-process and interpersonal skills are required since the process includes a lot of discussions and finding out what the common need is. If the number of participants is really large there might be need for a consultant or facilitator.

3.2. Purpose

Product planning in roadmapping

This is the most common type of a technology roadmap: linking the insertion of technologies into products.

Programme planning

This type is more directed to the implementation of strategy and related to project planning. Figure 5 shows the relationships between technology development phases, programme phases and milestones.

Formats

• Bars: Almost all the roadmaps are (partly) expressed in bars for each layer. This makes the roadmaps very simple and unified, which makes the communication and integration easier.
• Graphs: A technology roadmap can also be expressed as a graph, usually one for each of the sub layers. (e.g. IMEC uses the second method).

4. Case Studies

Documented case studies include:

• ABB^[9]
• Mining^[10]
• Motorola^[11]
• Philips^[12]
• Siemens^[13]

The content is sourced from: https://handwiki.org/wiki/Engineering:Technology_roadmap