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.
Phase 1: Preliminary phase The first phase, the preliminary phase (see figure 2), consists of three steps: • satisfy essential conditions, • provide leadership / sponsorship, and • 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.
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.
Phase 2: Development phase The second phase, the development of the technology roadmap phase (see figure 3.), consists of 7 steps:
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: • the identification and description of each technology area, • critical factors in the roadmap, • unaddressed areas, •
implementation recommendations, and • technical recommendations. The report can also include additional information. In table 2 all the different sub-activities of the development phase can be seen.
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. == The fast-start approach to roadmapping ==