A development team completes a prototype. The system performs as designed. The benchmark improves. A pilot demonstrates that the technology can operate in a real environment. The project review is positive, and the organisation begins discussing scale.
But an important question remains unanswered: has the business moved closer to a purchase decision, or has it only moved closer to proving that the technology works?
Technical milestones and commercial milestones are related, but they are not interchangeable.
Technical evidence answers a technical question
A technical milestone may establish that a design meets a performance threshold, a process is repeatable under specified conditions, an interface functions or a prototype can operate in a relevant environment. These are necessary achievements. Without them, the organisation may have nothing credible to offer.
A commercial milestone answers a different question. It establishes that a defined customer problem matters enough for someone to consider adopting and funding the solution. It may show that a buyer has agreed to a qualification process, that an operational owner has accepted a deployment plan, that procurement requirements are understood or that a customer has made a budget-backed commitment.
A technical result can support a commercial milestone, but it does not automatically create one.
The missing transitions
The path from technology to revenue contains several transitions:
Capability: Can the technology perform the required function?
Customer problem: Does it address a consequential problem for a particular customer or user?
Economic outcome: Does the improvement affect cost, quality, throughput, risk, reliability or another outcome that matters to the buyer?
Adoption: Can the customer integrate, qualify, operate and support the solution?
Purchase: Is there an identified decision-maker, budget, procurement pathway and reason to act?
Repeatability: Can the supplier deliver the outcome consistently at economics that work?
A project may advance through one transition while remaining stuck at another. For example, a medical instrumentation prototype may achieve its performance target but still require a validation pathway, user workflow assessment, service model and procurement route before a customer can adopt it. A manufacturing technology may run successfully in a demonstration but fail to meet the customer's uptime, maintenance or integration requirements.
Redesign milestone reviews around evidence of progress
Technical development reviews should continue to assess engineering quality. But leadership reviews should also ask what commercial uncertainty has been reduced.
Instead of recording only “prototype completed”, record which customer requirement has been validated, who accepted the evidence and what decision it enables. Instead of recording “pilot successful”, specify whether the pilot changed the customer's willingness to qualify, budget, purchase or expand deployment.
This does not mean every technical milestone must immediately generate revenue. Deep technology often requires substantial development before the commercial pathway is clear. It means the organisation should make the remaining uncertainty visible rather than assuming that technical progress will eventually convert into demand.
Use separate scoreboards
A useful operating discipline is to maintain two connected views. The technical view tracks performance, reliability, reproducibility and technical risk. The commercial view tracks customer problem validation, economic impact, stakeholder commitment, adoption requirements, purchasing path and delivery economics.
The two views should inform each other. A technical limitation may change the target segment. A customer requirement may change the product roadmap. A successful demonstration may justify the next validation step without yet justifying full-scale investment.
The strategic implication
Technical progress is real progress. But a business should not use it as a substitute for commercial evidence.
The leadership question at every milestone is: “What uncertainty have we reduced, whose decision can now change, and what is the next evidence required before we commit more?” That question connects engineering achievement to the customer and commercial outcomes the business ultimately needs.
Related reading
- Why Industrial Pilots Fail to Become Purchase Orders
- The Gap Between a Working Prototype and a Scalable Product
Continue exploring this collection: Execution — Sustaining the Advantage
Browse all articles · Ideas & Insights
Interested in the decisions behind technology-led growth? Explore Work With Me →
Continue reading in this collection
Build an Operating Rhythm That Converts Strategy into Results
A strategic operating rhythm connects milestones, evidence, accountability and resource decisions so leaders can adapt execution as conditions change.
Read article →
The Execution Gap Usually Begins with a Missing Decision
When priorities, ownership or authority remain unresolved, more activity cannot compensate for the decisions the organisation has not made.
Read article →
From 30 Ideas to 3–5 High-Value Growth Opportunities
Narrowing a broad idea set requires a common evaluation logic that tests customer value, strategic fit, capability, economics and evidence.
Read article →