Promising medical technology can lose time and capital when the clinical program is designed around a generic trial model instead of the decision the evidence must support. Stronger programs stage evidence, test feasibility early, and account for how the device will actually be used.
A compelling device concept is not enough to carry a MedTech company through clinical validation. Sponsors also need evidence that answers the right safety, performance, usability, regulatory, reimbursement, and adoption questions at the right stage of development.
When that evidence strategy is unclear, a trial can be technically compliant yet commercially unhelpful. The protocol may measure an endpoint that does not support the intended claim, recruit a population that does not reflect real use, or lock the sponsor into an expensive study before important design and workflow assumptions have been tested.
Clinical failure often starts before the first participant is enrolled
The highest-leverage clinical decisions are usually made before sites are selected and before a protocol is final. The sponsor must be clear about the decision the evidence needs to support, the product claim being pursued, the risks that remain uncertain, and the clinical setting in which the device will be used.
This matters across markets. In the European Union, the Medical Device Regulation connects clinical evaluation with the manufacturer's claims, risk management, post-market surveillance, and post-market clinical follow-up. In the United States, the appropriate evidence pathway depends on the device, indication, risk, development stage, and submission strategy. Australia and New Zealand introduce their own ethics, regulatory, site, and operating considerations. A useful program aligns those requirements without assuming that one study design automatically fits every market.
Four patterns that make a MedTech evidence program fragile
1. The evidence question is not defined precisely enough
A broad objective such as proving that a device works is not a study strategy. The sponsor needs to define what success means, for whom, compared with what, in which setting, over what period, and for which regulatory or commercial decision. Those choices shape the population, endpoints, comparator, sample size, follow-up, and data collection plan.
2. The company commits to a near-final study too early
A large study can amplify unresolved assumptions. If device design, procedure, training, workflow, or endpoint feasibility is still uncertain, an appropriately staged feasibility program may provide more decision value than immediately committing to a pivotal-scale investigation. Staging is not a shortcut around rigor; it is a way to apply rigor to the uncertainties that matter first.
3. Human factors and clinical workflow are addressed too late
Medical devices are used by people inside real clinical systems. Setup, training, handoffs, alarms, cleaning, data entry, procedure time, and user interpretation can all affect safety and performance. A study that ignores those interactions may produce results that are difficult to reproduce outside a highly controlled environment.
4. Recruitment and site readiness are treated as assumptions
A theoretical patient pool is not the same as an accessible study population. Eligibility criteria, referral pathways, competing studies, procedure capacity, investigator interest, device training, reimbursement, and follow-up burden all affect enrollment. Feasibility should test these conditions with sites and clinicians before they become fixed inputs in the delivery plan.
What smarter medical device study design looks like
- Start with the decision: define the claim, regulatory milestone, clinical question, and commercial uncertainty the evidence must address.
- Sequence the evidence: separate questions that can be answered through bench, preclinical, usability, feasibility, pivotal, and post-market activities.
- Design for the device: account for iteration, user technique, learning effects, procedural variation, and the care pathway rather than copying a pharmaceutical protocol structure.
- Test operational assumptions: validate the population, site capability, recruitment pathway, training model, data flow, and follow-up burden before finalising timelines.
- Plan for reuse: collect high-quality data that can inform later regulatory, payer, clinician, investor, and post-market decisions where appropriate.
Use early feasibility to reduce uncertainty—not to avoid rigor
For suitable programs, an early feasibility study can evaluate initial clinical safety and device functionality in a limited number of participants and may inform device modifications. It is most valuable when early clinical experience can answer questions that cannot practically be resolved through additional nonclinical work alone.
Not every device needs an early feasibility study, and a small study is not automatically the right study. The development stage, available evidence, risk controls, intended use, and target pathway should determine whether early feasibility, traditional feasibility, pivotal, or another evidence model is appropriate.
Bring human factors, clinicians, patients, and sites into the design earlier
Human factors work helps identify and reduce use-related risks. Clinician and site input helps reveal whether a procedure, training model, endpoint, or follow-up schedule will work in practice. Patient input can expose burdens or barriers that affect participation and retention. These perspectives are most useful when they can still change the design, not after the protocol and device workflow have been locked.
Plan evidence across the product lifecycle
The clinical program should connect early development with later evidence needs. Depending on the product and jurisdiction, that may include feasibility and pivotal investigations, usability evidence, registries, post-market clinical follow-up, and fit-for-purpose real-world data. Real-world evidence can support regulatory decisions in appropriate circumstances, but the data source and analysis still need to be reliable and relevant to the question being asked.
A practical pre-protocol check
- What exact decision will this study inform?
- Do the endpoints support the intended claim and matter to clinicians and patients?
- Which product, workflow, or usability assumptions remain untested?
- Is the proposed population available at the selected sites under the planned eligibility criteria?
- What evidence is needed now, and what can appropriately be generated later?
- How will data from this stage inform the next regulatory, clinical, or commercial milestone?
- What would cause the team to stop, adapt, or redesign before committing more capital?
The principle: design the evidence as deliberately as the device
Strong MedTech programs do not simply run smaller trials or larger trials. They run fit-for-purpose studies in a deliberate sequence. The right program reduces the most important uncertainty at each stage while protecting participants, maintaining evidence quality, and preserving a clear line of sight to clinical practice.
Mobius works with MedTech sponsors across Australia, New Zealand, and the United States to connect clinical strategy, feasibility, study design, site delivery, data quality, and regulatory-aware evidence planning.
This article provides general clinical development information and is not regulatory, legal, or medical advice. Requirements and appropriate study designs depend on the product, indication, risk, evidence base, and jurisdiction.
References
- Regulation (EU) 2017/745 on medical devices — EUR-Lex
- Early Feasibility Studies Program — U.S. Food and Drug Administration
- Applying Human Factors and Usability Engineering to Medical Devices — U.S. Food and Drug Administration
- Patient Engagement in the Design and Conduct of Medical Device Clinical Studies — U.S. Food and Drug Administration
- CDRH and Real-World Evidence — U.S. Food and Drug Administration