Additional Contributor: Tina Berthiaume
In early stages of medical device design, many innovators or teams rely on a proof of concept, which focuses on concept function, not the holistic viability of the concept’s development pathway. Too many jump from concepts to detailed design without clearly defining an official, early milestone to vet design direction and confirm it can achieve both development and commercialization goals.
A well-defined design feasibility gate clarifies what must be proven now, what can be deferred, and how to prove it efficiently. Officially integrating this into the design control process ensures cross functional input within the early design phases and reduces avoidable development risks that arise in later phases. Resulting in documented design iterations with key considerations that inform design inputs and a robust design history file for future reference and improved regulatory compliance.
Design controls require planning, defined design inputs, managing risks, and holding design reviews. These elements are necessary, but they do not explicitly require an early milestone that confirms a design direction is ready for detailed design. That gap leads to later phase development churn, schedule delays, and budget surprises. Design feasibility fills the early-design gap by defining the burden of proof, executing the leanest plan to meet it, and confirming results before detailed design. A well-defined design feasibility gate will answer a clear question: do we have objective evidence that this direction can satisfy requirements within real-world constraints?
Medical Device Development Proof of Concept
A proof of concept shows that a single idea can work. Teams build a prototype, run bench tests or evaluate user tasks, and gather data.
“Proof of concept” in early medical device design phases is inconclusive because:
Treat each POC as a proof point feeding feasibility, not the milestone itself.
Design feasibility is the early gate that concludes, with evidence, that a design direction is ready to enter detailed design development. It is broader than a single proof of concept and different from pharma or clinical “feasibility,” which often refers to trial logistics. In devices, this early design work compares the following aspects to lead to informed down selection with the most viable direction to achieve feasibility. The output is a documented decision, including down-selection rationale and plans to close remaining gaps.
|
Dimension |
Decide Now |
Minimally Viable Evidence Examples |
Pitfalls to Avoid |
|
Requirements |
What must be true for safety, performance, and usability. How success will be measured. |
Top-level, testable requirements with initial acceptance criteria. Traceability to user needs and hazards. |
Vague “goals,” no test method, no acceptance criteria. |
|
Risks |
Which hazards and failure modes could break the program. How they will be mitigated or explored. |
Preliminary hazard analysis or FMEA entries for top risks. Targeted proof points mapped to each risk. |
Treating risk qualitatively only. No links from risks to tests. |
|
Users & Tasks |
Which critical tasks must be proven safe and workable now. |
Formative or simulated-use sessions focused on critical tasks. Task success rates, representative users, environments. |
General preference feedback in place of task evidence. |
|
Technology & Software |
Which mechanisms, algorithms, and interfaces carry the heaviest proof burden. |
Bench or breadboard data for hardest claims. Software behavior in representative scenarios. Data integrity checks. |
Pretty prototypes with no measurement. “Happy-path” demos only. |
|
Constraints |
Sterilization, packaging, shelf life, transport, environment, serviceability, cybersecurity. Which apply now. |
Modality and materials screen. Packaging concept with basic transit exposure. Shelf-life rationale or plan. Early COGS bounds. |
Deferring constraints. Picking materials before modality. |
|
Business |
What makes the product viable to make, sell, service, and pay for. |
Preliminary COGS model and pricing guardrails. Reimbursement and market access scan. Timeline realism. |
Ignoring cost-per-use, real world evidence, or reimbursement codes. |
|
Decision Record |
What “go” looks like and who signs off. |
Independent review, down-selection to one direction, open issues with owners and dates. |
Informal approvals. No single owner for gaps. |
Use the minimally viable evidence approach, for each element. Define the smallest proof that credibly closes risk with a blend of applied research, utilization of prior data, SME rationales, and / or targeted testing.
User
Technology
Business
Requirements and risk traceability
Decision record
If your medical device roadmap jumps from concepts to detailed design, add the missing gate. A formal, focused design feasibility milestone gives leaders credible forecasts, reduces late rework, and sets up the project for success. We can help you plan the feasibility effort, build the right proof points, and facilitate an independent review so development progresses smoothly with confidence. Get in touch. It’s never too early.
What is a proof of concept in medical device development?
A proof of concept shows that one idea can work under defined conditions. Treat it as an input to feasibility, not the go-forward milestone. With Veranex’s Innovation CRO approach, proof points are executed by one cross-disciplinary team, so usability, engineering, and regulatory learnings feed each other in real time, not in vendor silos. That reduces churn and accelerates decisions.
What is design feasibility and how is it different?
Design feasibility is the early gate that proves a design direction can satisfy testable requirements within real-world constraints. It evaluates multiple concepts or variants and ends with a documented decision. Veranex integrates the evidence across discovery, rapid prototyping, human factors, regulatory strategy, market access strategy, and even considering manufacturing scale-up, so feasibility is a single evidence stream rather than a stack of disconnected studies.
How does design feasibility fit within design controls?
Feasibility operationalizes planning, inputs, risk management, and design reviews into one decision point early in development, then carries the record into the Design History File. Utilizing the same team to execute early discovery, usability, and engineering also aligns regulatory, quality, and commercialization strategies, will de-risk regulatory submissions and strengthen your evidence plans for market adoption and success.
What evidence is required to pass the design feasibility gate?
A right-sized, risk-based minimum viable evidence package of testable requirements, targeted results, simulated-use findings based on critical tasks, and early constraint checks like sterilization, packaging, shelf life, and cost. Best constructed with cross-functional teams, because, with Veranex, design, software, human factors, manufacturing, regulatory, quality and market access live under one roof, so you get decision-grade evidence without relaying between vendors.
About the Author: As Vice President, Innovation and Technology, Joe Gordon drives innovation by identifying strategies, opportunities, and technologies impacting clients across medical devices, healthcare delivery, diagnostics, and consumer healthcare. Over 30+ years and 400+ projects, he leads cross-functional teams developing creative solutions for complex challenges, including a digital surgical robotic system developed in just over three years. Joe excels at guiding innovation through chaos, bringing clarity to complex concepts, and navigating crowded patent landscapes while building robust IP protection strategies. His expertise spans complex capital systems, next-gen wearables, and integrated drug delivery platforms.