technology‑review.com

Method 04 · Assess

Technology Lifecycle & ADL Classification

Technologies pass through a lifecycle, and their strategic significance shifts along the way: from the emerging technology (unclear whether it will ever matter) via the pacing technology (beginning to change competition) to the key technology (deciding competitive advantage today) and on to the base technology (everyone has it, nobody wins with it any more). This classification after Arthur D. Little is one of the most useful tools of technology management — and one of the most sloppily applied. Because it is strictly relative to an industry: what is a key technology for an automotive supplier is irrelevant for a bank and long since base for a software house.

EMERGINGPACINGKEYBASE observebuildmasterbuy in Industry A Industry B Industry C The same technology —three industries, three classifications.
Four stages with four consequences — and the same technology in three places, depending on the industry. That is why our roadmaps classify for reference industries, not absolutely.

Procedure

  1. Name the frame of reference. For which industry, which market, which company is the classification made? Without a reference, every rating is worthless.
  2. Break down into sub-technologies. A bundle like "robotics" is too coarse; gripping, machine vision, motion planning, foundation models for motor control are separate entries.
  3. Judge competitive relevance. Per sub-technology and frame: does it differentiate today? Will it? Did it once?
  4. Classify. Emerging · pacing · key · base — with one sentence of justification.
  5. Repeat. The classification moves; pacing becomes key becomes base. Review annually.

Strengths

  • Connects maturity with strategic significance — not just "how far" but "how important, for whom".
  • Clear consequences: buy base, master key, build pacing, watch emerging.
  • Established and readily understood in companies.

Limits

  • Often applied absolutely instead of relative to an industry — then it misleads.
  • The boundaries between stages are a matter of judgement.
  • Does not capture interactions between technologies.

How we use it in our roadmaps

Here our roadmaps solve a problem on which generic roadmaps fail: a roadmap for "everyone" cannot classify absolutely, because the classification depends on the reader. That is why the absolute axis in our roadmaps is maturity (TRL plus adoption), and the ADL classification is reported as a matrix for three to four reference industries — for instance: "pacing for manufacturing, already key for software companies, emerging for financial services."

That is more honest than a seemingly objective rating, and more useful for the reader: they find their industry and see immediately whether they must watch, build or master. Block 3 of every roadmap.

References