Essay · market choice · 9 minute read

How industrial teams choose the next application for a proven technology

A practical framework for the moment when the technical platform works, several markets look plausible, and the real problem is deciding where the next unit of capital belongs.

Test 01

Market potential

Is the problem and resulting value significant enough to change behaviour?

Test 02

Capture challenge

Can this organization reach the buying system and win against the real alternatives?

Test 03

Evidence quality

Can the next proof reduce the uncertainty that actually blocks the decision?

Test 04

Path to adoption

Do production, qualification, access, ownership and complementary capabilities connect?

A proven technology can still have an unresolved market

A material, process, sensor, coating or production capability works. The team can demonstrate it. Several industries can imagine using it. The difficulty is no longer whether the phenomenon is real.

The difficulty is deciding which application deserves investment next.

That decision is easy to underestimate because every function sees a legitimate part of it. Technical teams see feasibility. Commercial teams see demand and access. Operations sees repeatability and capital requirements. Finance sees exposure and return. Senior leadership sees a portfolio choice.

The result can be a great deal of intelligent work without a comparable set of options.

Explore broadly, then stop adding options

Research on emerging technology firms found that generating several market options before first entry was associated with better performance. Experienced founders were more likely to compare a choice set instead of committing to the first plausible use.

That supports broad exploration, but not endless exploration. The same research found decreasing marginal returns as more options were added.

At the beginning, another application can reveal a more valuable use of the technology. Later, another application may simply create another internal constituency and another reason to postpone focus.

A useful opportunity set should therefore end with explicit categories: pursue now, test because one uncertainty could change the ranking, preserve as a future option, or stop allocating attention. Without those categories, the opportunity map is an archive rather than a strategy.

Compare potential with capture challenge

Market size is an input, not a conclusion.

The largest theoretical market can be a poor first application if it requires major technical adaptation, long qualification, entrenched channels or a buying system that the team cannot reach. A smaller market can be a stronger starting point when it has clearer pain, closer technical fit and a faster route to credible evidence.

The Market Opportunity Navigator separates an opportunity's potential from the challenge of capturing its value. Recent work on deep-technology selection adds technological relatedness: pursuing one market can require a different development path and can change which future markets remain accessible.

  1. Reason to change. Is the problem important enough to alter behaviour?
  2. Economic potential. Is there sufficient value if the application succeeds?
  3. Capture challenge. Can this organization reach the buying system and compete against the real alternatives?
  4. Technical distance. How far is today's proof from the performance and acceptance requirements?
  5. Option value. What capabilities, evidence or access would success create next?

These questions do not automatically favour a small beachhead. Some platforms and facilities require a large market from the beginning. They do force that choice to be justified by the economics rather than by a market-size slide alone.

Separate interest from behavioural evidence

Industrial purchases rarely belong to one person. Organizational buying research distinguishes users, influencers, buyers, deciders and gatekeepers because each role controls a different part of the path.

Positive reactions therefore carry different evidentiary weight. "Interesting" is weak. Time spent examining data is stronger. Sharing a requirement or acceptance threshold is stronger again. Providing a sample, operating condition or internal expert makes the question testable. Assigning people, resources or a decision date represents a further change in behaviour.

None guarantees adoption. The point is that they should not be recorded in the same column. A market assessment becomes more reliable when it records what changed, which role changed it and which uncertainty that behaviour reduces.

Treat translation as part of the decision

The distance between technical truth and investment language creates its own risk. A process window, degradation mechanism or uncertainty range cannot simply be removed to make a clean executive story. But a precise technical result is not decision-ready until its operational and economic consequence is legible.

Translation has to work in both directions. From technology to market, it should explain what the capability changes, for whom, under which conditions and with which remaining limitations. From market to technology, it should turn a broad need into a measurable requirement: operating conditions, failure threshold, acceptance test, repeatability and consequence.

The quality test is not whether the explanation sounds simple. It is whether the decisive technical constraint survives while every role can understand what decision it affects.

Make proof responsible for a decision

Teams can accumulate technically valid evidence without reducing the uncertainty that blocks investment. Before running another test, write down the decision that is blocked, the uncertainty blocking it, the smallest credible observation that could change the belief, the threshold separating the outcomes, and the action attached to each outcome.

The final item prevents evidence from becoming activity. If every result leads to more testing, the test has no decision rights.

This does not mean all research needs an immediate economic consequence. Exploratory science needs room to create unexpected knowledge. But work described as reducing development or market risk should state which uncertainty it is reducing and what happens when the result arrives.

Include the physical and organizational system

An application is not only a market and a technology. It also implies a production route, capital base, qualification path, partner system and internal owner.

Installed equipment creates both capability and bias. A machine park makes some applications cheap to consider and others expensive before the comparison begins. That can be rational because switching routes creates cost and uncertainty. It can also lead the organization to select problems that feed the asset rather than problems that deserve solving.

Partnerships create a similar distinction. Research on complementary assets shows why technology firms may need another organization's production, distribution, reputation or market access. But a partnership label is not itself evidence. Its strategic value lies in the capability it adds, the uncertainty it reduces or the commitment it creates.

Use four tests and four actions

The four tests do not remove judgment. A scoring model can create false precision, especially when weak assumptions are averaged into one attractive number. Every judgment should retain its provenance: what is observed, what is inferred and what remains unknown.

A proven technology can support many plausible futures. Strategy begins when those futures stop being treated equally.

Sources