Skip to content
Back to search results

Technology Roadmapping

Introduced by
Robert Phaal, Clare Farrukh, David Probert (Cambridge T-Plan); Motorola/Corning origins
Year
2004
Type
Time-based strategic-planning process
Family
Foresight and strategic planning
Font size

What does it do?

Technology roadmapping is a strategic-planning technique that produces a time-based, multi-layered chart linking markets and business drivers, products and services, and the technologies and resources needed to deliver them.

By laying these layers along a common timeline and drawing the links between them, a roadmap aligns research and development with strategy, answering where an organisation wants to go, how it will get there, and which technologies must mature and when.

The intuition behind the method

Imagine a single large chart with time running left to right and several stacked rows. The top row shows market needs and business drivers as they evolve; the middle row shows the products or services that will meet them; the bottom rows show the technologies and resources required, with arrows linking a future product to the technologies it depends on. Read top-down it answers 'what does the market pull us toward?'; read bottom-up it asks 'what can our technology push into products?' The power of the roadmap is that it forces these usually separate conversations—marketing, product, R&D—into one shared picture, exposing where a planned product has no technology to support it or where a maturing technology has no product to use it.

History

Technology roadmapping was pioneered in industry in the late 1970s and 1980s, most famously at Motorola, which used product-technology roadmaps to align its development efforts, and at Corning. The approach gained wide visibility through the International Technology Roadmap for Semiconductors, which coordinated the industry's R&D for decades. Kostoff and Schaller's 2001 paper distinguished science and technology roadmap types and their construction, while Phaal, Farrukh, and Probert at the University of Cambridge generalised the technique into the flexible, layered T-Plan framework set out in their 2004 article, making roadmapping accessible to firms and foresight programmes well beyond its semiconductor origins.

When to use it

Use technology roadmapping when an organisation must coordinate market, product, and technology planning over time and wants a shared, visual framework to align R&D investment with strategy. It is well suited to product- and technology-intensive businesses, to sectors coordinating pre-competitive research, and to foresight programmes translating a vision into actionable milestones. Roadmapping assumes that markets, products, and technologies can be meaningfully linked on a timeline, that cross-functional participation produces better plans, and that the roadmap will be maintained rather than shelved. It is less appropriate in highly turbulent environments where any timeline is quickly invalidated, for purely exploratory research with no product target, or where the organisation lacks the cross-functional engagement the process depends on.

Limitations and considerations

  • Roadmaps can become rigid; in fast-changing environments a fixed timeline is quickly outdated and may anchor planning to obsolete assumptions.
  • The process is resource-intensive and depends on sustained cross-functional engagement that is hard to maintain.
  • Quality rests on the input judgements about future markets and technologies, which carry all the uncertainty of any forecast.
  • Without disciplined updating, the roadmap becomes a one-off artefact that drifts out of sync with reality and loses credibility.

Source conditions do not replace independent scientific review or validation by an analysis engine.

Strengths

  • Integrates market, product, and technology planning into one shared, time-based picture that aligns R&D with strategy.
  • Exposes gaps and dependencies—products without enabling technologies, or technologies without target products—before they become problems.
  • Reconciles market pull and technology push, balancing customer-driven and capability-driven innovation in a single framework.
  • Builds cross-functional communication and consensus, since constructing the roadmap forces marketing, product, and R&D to align.

Applications

  • Corporate product-technology planning, linking product portfolios to the technologies that enable them.
  • Sector-wide pre-competitive roadmaps, such as the semiconductor industry's ITRS, coordinating collective R&D.
  • National and governmental technology roadmaps guiding research investment toward strategic goals.
  • Emerging-technology and energy-transition roadmaps (e.g. clean energy, hydrogen) setting milestones to long-term targets.
  • Project and programme planning, sequencing technology development against product launches.
  • Innovation and foresight exercises translating scenarios and visions into time-phased action plans.

How it works

How it works

1

Define the roadmap architecture and scope. The team agrees the purpose, time horizon, granularity, and the set of layers—typically market/business drivers, products/services, and technology/resources—plus the boundaries of the exercise, so the resulting chart fits the strategic question and the organisation's planning cycle.

2

Identify and prioritise the market and business drivers in the top layer. Workshops capture the customer needs, market trends, and strategic objectives that will shape demand over the horizon, ranking them so that downstream product and technology choices are anchored in what actually matters to the business (the 'market pull').

3

Map the products, services, and functional features that will satisfy those drivers over time. The middle layer translates market needs into the evolving portfolio of offerings and their key performance features, sequenced along the timeline to show how products must develop to keep meeting demand.

4

Link the technology and resource layers to the products. The lower layers set out the technologies, capabilities, and resources required to deliver each product feature and when each must be ready; arrows connect technologies to the products they enable, reconciling market pull with technology push and exposing gaps where neither aligns.

5

Assemble the integrated roadmap and establish a review cycle. The layers and links are consolidated into a single time-based chart that surfaces gaps, dependencies, and decision points; the roadmap is validated with stakeholders and periodically revisited and updated as markets, products, and technologies evolve, keeping it a living planning tool.

Common pitfalls

  • Treating the roadmap as a fixed prediction rather than a living plan, and failing to schedule regular reviews and updates.
  • Building the technology layer in isolation from market drivers, so R&D pursues capabilities with no business pull.
  • Over-detailing distant time horizons, creating false precision about a future no one can actually foresee.
  • Letting the exercise be owned by a single function, which produces a partial roadmap lacking cross-functional buy-in.

Frequently asked questions

What are the typical layers of a technology roadmap?

Most roadmaps use three broad layers along a common timeline. The top layer captures market and business drivers—customer needs, trends, and strategic objectives (the 'why' and 'what'). The middle layer holds products, services, and functional features that meet those drivers (the 'what'). The lower layers cover the technologies, capabilities, and resources required to deliver them (the 'how'). Arrows link the layers so that the chart shows how technologies enable products that satisfy market needs over time.

What is the difference between market pull and technology push in roadmapping?

Market pull works top-down: it starts from market and customer needs and asks which products and then which technologies are required to satisfy them. Technology push works bottom-up: it starts from existing or emerging technological capabilities and asks which products and markets they could enable. A good roadmap reconciles both perspectives in one framework, ensuring that planned products have supporting technologies and that promising technologies have target applications.

How does roadmapping relate to foresight and scenarios?

Roadmapping is often the implementation end of a foresight process. Where horizon scanning detects emerging issues and scenarios explore alternative futures, a roadmap translates a chosen direction into a concrete, time-phased plan of products, technologies, and milestones. Scenarios can be used to stress-test a roadmap's robustness, and Delphi surveys can supply expert estimates for when key technologies will mature, dating the milestones the roadmap depends on.

Related methods

Sources

  1. Phaal, R., Farrukh, C. J. P., & Probert, D. R. (2004). Technology roadmapping—a planning framework for evolution and revolution. Technological Forecasting and Social Change, 71(1-2), 5-26.

    Open DOI reference
    Copied.
  2. Kostoff, R. N., & Schaller, R. R. (2001). Science and technology roadmaps. IEEE Transactions on Engineering Management, 48(2), 132-143.

    Open DOI reference
    Copied.