Road-mapping

Road-mapping creates a shared, time-based view of how markets, products, technologies and capabilities may evolve. It connects a desired future with the decisions, research, resources and milestones that could make that future possible. The map is a coordination instrument, not a prediction.

When to use it

Use product–technology road-mapping when future customer needs and technical choices must be aligned across functions or organisations. It is particularly valuable in technology-intensive settings with long development lead times, interdependent platforms or shortening product life cycles.

A useful road map describes:

• Delivery – products, capabilities and research outputs required.

• Purpose – the market need, strategic objective and value each layer serves.

• Timing – horizons, decision gates, dependencies and critical milestones.

• Resources – people, funding, partnerships, data and technology needed.

Road-mapping can:

• create a shared evidence base for long-range planning;

• connect external market and technology signals with internal choices;

• align R&D, product, commercial and capability investment;

• identify opportunities to reuse platforms or technologies;

• expose gaps, uncertainty and long-lead dependencies;

• coordinate suppliers, customers, researchers and partners; and

• help teams adapt when assumptions change.

Origins

Technology road-mapping developed in industrial planning and was popularised through corporate practice at Motorola before spreading to sector, national and research settings. Industry road maps coordinate priorities across organisations; corporate road maps guide a single enterprise; product–technology road maps connect market needs, products and enabling technologies; and competence–research road maps identify the knowledge and research required.

What it is

The method lays several linked layers across time. A market layer expresses changing needs and drivers; a product or service layer shows how the offer may respond; technology and capability layers identify what must be available; and project or resource layers show the work needed to close the gaps.

Common forms include:

• Industry road maps, which describe shared challenges, standards and development paths across a sector. They can coordinate precompetitive research and support funding discussions, but require governance around competition, confidentiality and whose priorities dominate.

• Corporate road maps, which connect strategy with product–market and capability choices inside one organisation.

• Product–technology road maps, which combine market analysis, product assessment and technology scanning into an R&D and rollout plan.

• Competence–research road maps, which focus on scientific knowledge, skills, facilities and research programmes needed to enable a technology.

A road map may contain scenarios or alternative branches where uncertainty is high. The discipline lies in linking layers through explicit reasoning: a technology belongs on the map because it enables a product capability that serves a market need.

How to use it

Build the evidence base through:

1. Market analysis
2. A technology scan
3. Product assessment.

Market analysis works outside-in, identifying current and emerging customer jobs, regulation, competitors and ecosystem change. Technology scanning works inside-out and outside-in, assessing maturity, performance, cost, ownership and uncertainty. Product assessment evaluates the existing portfolio, customer outcomes and gaps against alternatives.

Bring cross-functional participants together to connect the layers. Generate product and platform options, then evaluate reward, strategic fit, readiness, risk and resource demand. Translate selected options into research, capability, partnership and rollout paths.

Assign owners to assumptions and milestones. Record confidence, dependencies and trigger signals. Use experts and respected champions to improve evidence and adoption, while preventing reputation or hierarchy from substituting for challenge.

For effective practice:

• involve people with market, product, technical, operational and commercial knowledge;

• secure management commitment to the decisions and resources, not merely the workshop;

• use a consistent visual grammar so maps can connect;

• facilitate disagreements and preserve minority scenarios;

• update the map at a cadence matched to change; and

• choose a horizon long enough to influence capability and technology investment. If the strategic view does not extend beyond 2 years, a delivery plan may be more suitable.

Final analysis

The process of building a road map can be as valuable as the artifact because it exposes assumptions and creates shared language. Consensus, however, is not automatically correct. A firm with a contrarian strategy should not erase that view to match an industry map.

Use the road map to inspire, coordinate and test choices. Mark uncertainty and branches explicitly, compare actual signals with assumptions and retire paths when evidence changes. A visually coherent map can otherwise create false confidence in one linear future.

Top practical tip

Start with the market or mission need, then require every product, technology and research item to trace upward to that need and downward to an owner, decision gate and evidence signal.

Top pitfall

Do not present a road map as a forecast or promise. One polished timeline can suppress uncertainty, alternatives and dissent; show branches, confidence and the conditions that would cause a path to change.

Further reading

European Industrial Research Management Association (EIRMA) (1997) Technology Road Mapping. No. 52. Paris: EIRMA.

Farrukh, C., Phaal, R. and Probert, D. (2003) ‘Technology road-mapping: linking technology resources into business planning’. International Journal of Technology Management 26(1), 2–19.