Emerging technology is technology whose capabilities, practical uses or supporting ecosystem are still developing in ways that could change how organisations work. This guide explains what the term means, how business value emerges, and why a promising demonstration is different from a dependable operating system.
What Counts as Emerging Technology?
An emerging technology offers a developing capability whose usefulness and risks are not yet fully settled in a particular market or setting. Examples include new forms of AI, quantum computing and augmented reality, though each category contains applications at different stages of maturity. Businesses should evaluate a specific capability against a real problem, rather than assume that an entire category is either ready or irrelevant.
What makes a technology emerging?
“Emerging” is a description of development and adoption, not a quality certificate. It can refer to an underlying scientific approach, a new way to package existing components, or a capability becoming practical for a wider group of users. There is no single maturity boundary that applies equally to every industry.
Novelty alone is not enough. A new interface for an established database may be a useful product improvement without representing a major technological shift. Conversely, a long-studied scientific idea can still be emerging commercially if reliable deployment, skills or supporting infrastructure remain limited.
Three dimensions help clarify the label:
- Capability: What can the technology do that was previously impossible, impractical or difficult?
- Readiness: How reliably can that capability work outside controlled conditions?
- Adoption conditions: Are the required skills, integrations, rules and business models available?
These dimensions do not move together. A capability can improve rapidly while its economics remain uncertain. A product can attract many users while still requiring close supervision for consequential tasks. Widespread attention does not settle either question.
The label is also relative to the use case. AI assistance for drafting an internal meeting agenda and AI support for a clinical decision are not equivalent adoption decisions, even if both rely on related models. Stakes and context change the evidence required.
The main categories and what they actually offer
Business discussions often group unlike technologies together. A better starting point is to identify the capability, its dependencies and the uncertainty that matters to your organisation.
| Category | Potential business capability | Important qualification |
|---|---|---|
| Generative AI | Produce drafts, summarise material or support search | Outputs can be incorrect and require evaluation |
| Augmented reality | Place digital information over a view of physical surroundings | Tracking, visibility, comfort and safe use depend on context |
| Quantum computing | Explore specialised computational approaches | Practical advantage must be demonstrated for the particular problem |
| Advanced robotics | Perform or assist physical tasks | Safety, environment and maintenance shape feasibility |
| New sensing and edge systems | Collect and process information close to equipment | Data quality, connectivity and lifecycle support remain essential |
These are illustrative capabilities, not promises that every product in a category can deliver them. Some solutions combine several categories: a robot might use AI perception, local processing and remote monitoring. Each dependency can introduce a separate failure mode or supplier relationship.
Quantum computing also needs separating from post-quantum cryptography. The latter concerns cryptographic approaches intended to resist attacks from future quantum computers; adopting them is not the same as buying a quantum computer. NIST’s post-quantum cryptography project documents its standardisation work in that area.
This distinction matters because a business might reasonably monitor quantum computing applications while already assessing the future of its cryptographic systems with qualified security specialists. “Wait until the technology matures” is not a universal policy for every related issue.
How a capability becomes business value
A technical breakthrough is only one part of a business system. Value appears when a capability changes a useful outcome and the organisation can sustain that change at an acceptable cost and level of risk.
Consider a distributor exploring AI-assisted handling of product enquiries. Generating a fluent answer is the visible capability. The operating system around it includes a maintained product catalogue, access controls, a way to recognise uncertainty, staff review, customer escalation and records of important interactions.
If the catalogue is incomplete, the system may produce polished but unsuitable suggestions. If every answer needs extensive correction, apparent speed at the drafting stage may not improve the full workflow. If staff cannot explain or challenge recommendations, a helpful feature may become an operational liability.
A useful conceptual model is:
Business value = useful outcomes enabled − operating costs − consequences of failure.
This is a thinking aid, not a precise accounting formula. Some consequences, such as injury or unlawful processing of information, cannot be treated as acceptable simply because an estimated financial benefit is larger. Certain risks require avoidance, safeguards or specialist review.
The practical question is therefore not just “Does it work?” It is “For which tasks, under what conditions, with whose supervision, and at what total burden?” The answer usually depends as much on process design as on the technology itself.
Hype cycles, evidence and maturity
A hype cycle is a way of describing how expectations can rise around a technology, fall when limitations become clearer, and later become more realistic. It can help explain public attention, but it is not a timetable or proof that a technology will eventually become valuable.
Some capabilities find durable uses. Others remain niche, change direction or fail commercially. A business should not assume that buying after enthusiasm fades is automatically sensible, or that early adoption is automatically advantageous.
Different types of evidence answer different questions:
- A research result may establish that a capability is possible under specified conditions.
- A demonstration shows a selected workflow functioning, often with prepared inputs.
- A controlled pilot explores usefulness within a defined business setting.
- Operational evidence shows how a system behaves with ongoing users, exceptions, support needs and change.
None of these stages eliminates uncertainty. A pilot can be useful while still being too small to establish performance during rare but serious events. A deployed product can still change materially after a supplier update.
Read claims by asking what was measured, what the comparison was and which conditions were excluded. Evidence from another organisation may be informative without transferring directly to your data, users or obligations. Treat a supplier roadmap as a statement of intended direction, not an available capability.
Why risk and governance belong in the definition
Emerging technology is often discussed as an innovation topic, but it also changes responsibilities. New data flows, automated recommendations or physical interactions create questions about who approves use, who notices failure and who can intervene.
For AI, NIST’s AI Risk Management Framework uses the functions Govern, Map, Measure and Manage to structure risk management. This reinforces an important principle: assessing a technology includes understanding its context and consequences, not merely measuring technical performance.
In practice, governance means answering ordinary questions clearly. Who owns this workflow? Which uses are permitted? What information can enter the system? What requires human approval? How are errors reported? When must someone stop using it?
Security is part of the same picture. The NIST Cybersecurity Framework provides a common structure for cybersecurity risk outcomes. An emerging tool still needs familiar controls around access, data protection, suppliers and recovery, even when its interface feels radically new.
Responsible evaluation also considers people who do not choose the tool but are affected by it. A customer may receive an inaccurate recommendation; a worker may inherit extra checking duties; someone represented in a dataset may face an unfair outcome. Technical novelty does not remove existing legal or ethical responsibilities.
The main business responses: watch, explore or adopt
Not every interesting technology deserves immediate procurement. Organisations can take different positions for different capabilities and revisit them as evidence changes.
Watch when the application is distant, the evidence is weak or necessary dependencies are missing. A useful watchlist names the development that would trigger reassessment, such as a needed integration becoming available. Simply collecting news is not a strategy.
Explore when there is a plausible problem to solve and a safe way to learn. Exploration might involve staff education, supplier discussions or a bounded pilot. Its output should be better understanding and a decision, not pressure to declare a success.
Adopt selectively when evidence supports a defined use and the organisation can operate it responsibly. Adoption is not a blanket approval of every feature or adjacent use. A system suitable for internal suggestions may remain unsuitable for autonomous customer decisions.
For example, a facilities team might adopt a conventional sensor system now, explore AR maintenance instructions on training equipment, and watch quantum computing developments without buying access. These positions are consistent because each addresses a different business need and readiness level.
The important boundary is between learning about a possibility and depending on it. Dependence brings requirements for support, continuity, monitoring and exit arrangements that a demonstration does not establish.
Questions About Emerging Technology
Is emerging technology the same as disruptive technology?
No. “Emerging” describes a capability or ecosystem still developing. “Disruptive” describes effects on markets, business models or established ways of working. An emerging technology may produce incremental improvements without becoming disruptive, and disruption can arise from a business model using established technology.
Does an established supplier make a technology mature?
Not necessarily. A large supplier may offer strong support while a particular feature remains experimental or narrowly supported. Assess the specific product, terms, evidence and intended use rather than treating the supplier’s reputation as proof of readiness.
Can an old technology become emerging again?
A longstanding idea can gain new commercial relevance when supporting hardware, data, software or economics change. Be precise about what is newly feasible. The age of the underlying concept tells you less than the readiness of the actual application.
Must every company have an emerging-technology strategy?
Every company benefits from a proportionate way to assess relevant changes, but not every company needs a dedicated team or investment programme. A small organisation may only need an owner, a review process and clear conditions for investigating a useful capability.
Judge Technology by Its Business Value
Emerging technology is a developing possibility, not a guaranteed advantage. Understand the specific capability, separate attention from evidence, and judge readiness in the context of the work and people it would affect.
Next steps: Use the getting-started checklist to plan an evaluation, check common emerging-technology mistakes, and browse the Technology section for wider context.
Sources
- NIST — Post-Quantum Cryptography
- NIST — AI Risk Management Framework
- NIST — Cybersecurity Framework
This guide is general education, not professional, legal or security advice.