Bridging the gap between technical feasibility and commercial readiness

The prototype works. The technology has been demonstrated. The investors are impressed. So why is your medical device still years away from market?

It is a familiar challenge in MedTech.

An engineering team develops an exciting new technology. The prototype performs exactly as intended. Early feedback is positive. There is genuine enthusiasm about its potential.

Yet months, sometimes years, later, the programme is still in development.

The technology works, but the product doesn’t exist.

Why?

Because technical feasibility is only one part of commercial readiness.

And the journey between the two is where many promising medical innovations lose momentum, consume budgets and ultimately fail to reach patients.

For MedTech leaders, the important question is not simply whether a technology can work.

It is whether that technology can become a product that is safe, usable, manufacturable, commercially viable and worth buying.

The prototype trap

A prototype is designed to answer a relatively narrow question.

Can we make this work?

It might demonstrate a new sensing technology, a novel therapeutic mechanism, an innovative delivery system or a completely different approach to an established clinical procedure.

That is an important milestone.

But it is not a product development strategy.

A prototype can perform brilliantly in a controlled environment while concealing fundamental challenges that only emerge when the technology moves towards commercialisation.

Can it be manufactured consistently?

Can it withstand repeated use?

Will clinicians find it intuitive?

Can it be cleaned and maintained?

Will the materials and components meet regulatory requirements?

Can it be produced at a commercially acceptable cost?

Can it be validated under the intended conditions of use?

And perhaps most importantly:

Does it solve a problem that customers value enough to change their existing behaviour?

These are not questions to leave until the prototype is finished.

They should influence its design from the outset.

The uncomfortable question

Are you developing a product, or are you continuing to improve a prototype?

There is a significant difference.

One moves towards commercial readiness.

The other can become an expensive engineering exercise.

1. Technical success can hide commercial failure

Engineers are naturally focused on solving technical challenges.

That is their expertise.

But in medical technology, technical excellence does not guarantee commercial success.

A device might achieve exceptional performance but require expensive components, complex assembly processes or manufacturing tolerances that make commercial production unrealistic.

A sophisticated user interface might offer extensive functionality while creating unnecessary complexity for clinicians.

A novel technology might demonstrate clinical potential but offer insufficient differentiation to justify its cost.

The challenge is that these problems are often discovered too late.

By then, significant time and investment may have been committed to a particular architecture or technical approach.

What would happen if your team evaluated commercial viability with the same discipline as technical feasibility?

What if target manufacturing costs, usability requirements, regulatory pathways and customer expectations were established before the engineering architecture became fixed?

This is where experienced multidisciplinary product development can make an enormous difference.

Not by adding more process.

But by identifying the right problems earlier.

2. Design for manufacture cannot be an afterthought

A prototype can be assembled by highly skilled engineers using specialist equipment and considerable manual intervention.

A commercial product cannot depend on those conditions.

Manufacturing introduces an entirely different set of requirements.

Component availability.

Supply chain resilience.

Material selection.

Assembly efficiency.

Production tolerances.

Quality control.

Reliability.

Serviceability.

Cost.

For medical devices, these considerations must also align with the manufacturer’s quality management system and applicable regulatory requirements.

The FDA’s Quality Management System Regulation, which came into effect in February 2026, incorporates ISO 13485:2016 by reference, reinforcing the importance of systematic quality management throughout the medical device lifecycle.

The question for development leaders is simple:

If your prototype works perfectly today, how confident are you that you could manufacture 10,000 identical devices tomorrow?

And at what cost?

The answer may require a fundamental rethink of the design.

That is considerably easier before the product architecture is locked down.

3. Human factors can make or break the product

A medical device does not succeed simply because it performs its intended technical function.

It must work for the people using it.

Under real conditions.

Often under pressure.

Sometimes with limited training.

And frequently in environments that are far less controlled than the development laboratory.

Consider a connected diagnostic device.

The sensing technology may be highly accurate, but what happens if the clinician struggles to interpret the results?

Or a home-use medical device.

What happens when the patient misunderstands the instructions, positions the device incorrectly or misses an important warning?

The FDA’s human factors guidance emphasises reducing use-related risks and ensuring devices can be used safely and effectively by their intended users.

Yet usability is still too often treated as something to optimise once the technology has been developed.

That approach can be expensive.

Are you validating the technology, or are you validating the complete user experience?

The distinction matters.

A technically successful device that people cannot use confidently is not commercially ready.

4. Regulatory strategy should shape the product, not follow it

Medical device regulation is sometimes viewed as a hurdle to overcome once development is substantially complete.

That can be a costly mistake.

Regulatory requirements can influence fundamental design decisions, including:

• Product architecture and materials.
• Software development and cybersecurity.
• Risk management and safety features.
• Verification and validation.
• Clinical evidence requirements.
• Labelling and instructions for use.
• Manufacturing controls and documentation.

Under the EU Medical Device Regulation, manufacturers must demonstrate conformity with applicable general safety and performance requirements.

In the United States, the FDA’s design and development requirements sit within the wider quality management framework.

These are not simply documentation exercises.

They affect the physical and functional design of the product.

Could an early regulatory decision eliminate six months of redesign later?

Quite possibly.

The objective is not to slow innovation with unnecessary bureaucracy.

It is to build regulatory thinking into the development process so that promising technologies can progress without avoidable setbacks.

5. The hidden problem: Development teams are often solving the wrong questions

Many MedTech organisations have highly capable internal engineering and product development teams.

But capability does not automatically mean capacity.

Established companies frequently have multiple programmes competing for the same resources.

Core product maintenance.

Regulatory changes.

Customer-driven improvements.

Manufacturing support.

Next-generation product development.

And somewhere in the middle sits a promising new technology that needs focused attention.

The prototype works, but nobody has the bandwidth to challenge the assumptions, resolve the remaining uncertainties and develop a credible route to commercialisation.

The programme continues.

Meetings multiply.

Milestones move.

But the fundamental questions remain unanswered.

Does your team need more people, or does it need a different approach to solving the problem?

Sometimes the most effective solution is a small, experienced, multidisciplinary team working outside the constraints of the organisation’s day-to-day development structure.

A team empowered to challenge assumptions, explore alternative architectures, build and test quickly, and focus relentlessly on what is required to move forward.

Not another layer of management.

Not a lengthy consultancy report.

A team that gets on with solving the problem.

6. The transition from prototype to product needs different thinking

The skills required to prove a technology works are not always the same as those required to commercialise it.

Early development rewards experimentation, technical creativity and rapid iteration.

Commercial product development demands integration.

Engineering.

Industrial design.

Human factors.

Regulatory requirements.

Manufacturing.

Supply chain.

Commercial strategy.

All must converge around a product that delivers a defined benefit to a defined customer.

This transition is often where development programmes become fragmented.

Different disciplines work towards different objectives.

Technical decisions are made without sufficient commercial input.

Design changes create unforeseen regulatory implications.

Manufacturing constraints emerge after substantial investment.

The solution is not necessarily a bigger team.

It is better integration.

What if the people responsible for design, engineering, usability and commercial feasibility were solving the problem together from day one?

That is when development becomes more focused.

Trade-offs become visible earlier.

Decisions become faster.

And expensive surprises become less likely.

7. Five questions every MedTech leader should ask

If you have a promising technology that has not yet become a commercial product, consider these five questions.

1. Have we defined the product, or just demonstrated the technology?

Is there a clear intended use, target customer, clinical benefit and commercial proposition?

2. Do we understand what could prevent commercialisation?

Have the major technical, regulatory, manufacturing, usability and commercial risks been identified and prioritised?

3. Are we designing for real-world use?

Has the device been evaluated with representative users in realistic conditions?

4. Can we manufacture it economically and consistently?

Do we understand the likely production costs, supply chain requirements and quality controls?

5. Are we making progress towards launch, or simply completing development activities?

Are milestones linked to meaningful reductions in risk and improvements in commercial readiness?

If the answers are unclear, the programme may need a different approach rather than simply more development time.

From possibility to product

At Maddison, we work with MedTech companies facing precisely these challenges.

Sometimes that means taking an early-stage concept and determining whether it has a credible path to market.

Sometimes it means helping an established MedTech business accelerate a programme that has lost momentum.

And sometimes it means challenging a product architecture that technically works but is unlikely to succeed commercially.

Our approach combines experienced product designers, engineers and human factors expertise with an understanding of the realities of medical device development.

We work alongside internal teams, bringing fresh thinking, focused resources and the freedom to explore alternative solutions without disrupting core programmes.

We believe the greatest value comes from identifying the right questions, resolving the critical uncertainties and turning promising technology into products that can succeed in the real world.

Because the objective is not to build a better prototype.

It is to build a product worth launching.

The question for your next development review

If your prototype works, but your product is still not ready for market, ask yourself:

What is really preventing us from moving forward?

Is it a technical problem?

A regulatory uncertainty?

A manufacturing constraint?

A usability challenge?

A commercial assumption?

Or simply a lack of dedicated resources to bring everything together?

Identifying the real barrier may be the most valuable development decision you make this year.

Maddison. Design That Means Business.

References and further reading

1. FDA, Quality Management System Regulation (QMSR), effective February 2026.
The revised regulation incorporates ISO 13485:2016 into the US medical device quality management framework.

https://www.fda.gov/medical-devices/postmarket-requirements-devices/qua…

2. FDA, Applying Human Factors and Usability Engineering to Medical Devices (2016).
Guidance on integrating human factors into medical device development to reduce use-related risks.

https://www.fda.gov/regulatory-information/search-fda-guidance-document…

3. European Union, Medical Device Regulation (EU) 2017/745.
The regulatory framework covering medical device safety, performance, conformity assessment and lifecycle requirements.

https://eur-lex.europa.eu/eli/reg/2017/745/oj

4. ISO 14971:2019, Medical Devices: Application of Risk Management to Medical Devices.
International standard defining principles and processes for managing medical device risks.

5. ISO 13485:2016, Medical Devices: Quality Management Systems.
International standard specifying quality management system requirements for medical device organisations.

6. IEC 62366-1:2015+A1:2020, Medical Devices: Application of Usability Engineering to Medical Devices.
International standard addressing the usability engineering process for medical devices.