The Adoption-Stuck Builder
Keeps adding features while clinicians keep not using the product. The problem was never the feature set.
Your privacy
May we use Google Analytics to see how visitors use this site? It sets cookies and only runs if you allow it. The site works fully without it, and you can You can change your choice any time under "Cookie settings" at the bottom of each page.
Most MedTech ventures never reach a physician's daily routine, and almost none of them fail for lack of technology. This is the long version of why, written from inside the ward.
Definition
Clinical adoption is the point at which a medical technology becomes part of clinicians' routine practice: used in the eligible cases, by the intended users, without a champion in the room.
It is not regulatory approval. It is not a purchase order. It is not a pilot. A MedTech product can have all three and still not be adopted.
The distinction matters because the industry measures the wrong things. A CE mark tells you a product may be sold. A reimbursement code tells you someone will pay. A pilot tells you a motivated team tried it under supervision. None of them tells you whether a nurse on a Tuesday night shift, with three admissions waiting, will still open your application in week three.
Healthcare is not an industry. It is a system: interconnected workflows, incentives, liabilities and habits that respond to a new product as a whole. That is why technically excellent solutions fail in it, and why the failure is structural rather than technical.
The enemy has a name
Every MedTech venture collects the same trophies. Investors reward them, accelerators celebrate them, founders build roadmaps around them. Each one is a permission to enter the market. None of them is evidence that the market will use the product.
Approval is the starting line. Adoption is the goal.EvoMed Consulting
Buying a product is not the same as adopting it. True adoption requires seamless integration into clinical practice, and that is a much higher bar than any certificate.
The numbers behind the failure
Sources: Nelson (2025), MD+DI; TTi Health Research; EMC survey of 150+ MedTech innovators, validated against StarMap assessments; Accenture and AdvaMed survey of MedTech executives (2022).
When we rank where ventures actually break, clinical adoption leads. In the EMC Industry Report 2026, structural adoption problems appear in 41% of failing ventures; funding readiness in 31%, regulatory alignment in 20%, scaling operations in 13%. Most failing ventures show more than one cause, which is why the shares add up to more than 100%, and why fixing one factor in isolation rarely saves a venture.
The seven success factors
StarMap scores a venture on seven success factors. They only make sense together: a weakness in one undermines the others. Watch the map light up as you read.
A defined, urgent problem for a clearly targeted patient group. If you try to be everything to everyone, you risk being no one's first choice.
The product slots into real hospital routines with minimal training and makes care more plannable, not less.
Care is moving out of the hospital into outpatient and home settings. Tools that only work inside the hospital risk obsolescence.
Interoperability with EHRs (electronic health records) and cross-provider coordination. Siloed tools end up unused.
A return on investment the buyer accepts, aligned with reimbursement or a new payment model. Clinical benefit alone does not carry a venture.
Measurable improvement in outcomes, safety or efficiency. Outcome data is the new currency of adoption and funding.
Onboarding, IT hurdles, staff resistance, change management. The number one reason brilliant products become shelfware.
Each factor is described in depth on the StarMap framework page and, chapter by chapter, in the book Fit before Scale.
Four founder archetypes, one blind spot
Across the ventures we have assessed, the same four patterns keep producing the same adoption failures.
Keeps adding features while clinicians keep not using the product. The problem was never the feature set.
Optimizes for the next round. The deck gets better every quarter; the clinical fit doesn't.
Works on all seven factors at once, prioritizes none, and burns runway on motion.
Maps the system before moving through it. This is the posture StarMap is built to produce.
The KOL trap
A key opinion leader (KOL) who loves your product is the most dangerous data point in MedTech. The KOL is motivated, senior, technically curious and rarely the person who has to use the product at 3 a.m. A successful pilot in their department proves that the product works when someone wants it to work. It says nothing about routine use by the other twenty clinicians, the IT department that has to integrate it, or the controlling department that has to justify it.
Adoption is decided by the routine, not by the champion.
Pilots should be designed to test the routine: the least motivated user, the busiest shift, the referral partner outside the building.
How to measure clinical adoption
Logins are not adoption. Licenses are not adoption. These are the questions that actually predict it. If three or more are a no, a venture is accumulating the structural misalignments behind MedTech's 75% failure rate, whatever the certificates say.
In what share of eligible cases is the product used, once the pilot team has moved on?
Can a new user reach confident use in under 15 minutes of self-service onboarding?
Can referring physicians and external specialists access results securely without installing your software?
Has at least one clinical KPI, recovery time, complication rate, readmissions, moved measurably after implementation?
Is there a one-page ROI case a hospital CFO would accept as a valid financial justification?
Before capital is committed
The cheapest moment to correct structural misalignment is before regulatory decisions lock in long-term constraints and before a funding round prices in assumptions that were never tested. That is what StarMap is for.
Start with the free Alignment Check, then a Discovery when it's warranted. A physician-led diagnosis of where the venture stalls after approval, and what to fix first.
Screen applicants and cohorts with StarMap OS before selection. Structural adoption risk next to the pitch score, not instead of it.
Add clinical adoption as the third diligence lens next to technical and regulatory. See the risk before you price the round.
Written by Dr. med. univ. Amel Havkic, MBA, physician, founder of EvoMed Consulting and creator of StarMap. About EvoMed.
Questions we get asked
Clinical adoption is the point at which a medical technology becomes part of clinicians' routine practice: used in the eligible cases, by the intended users, without a champion in the room. It is different from regulatory approval, from a purchase order and from a pilot. A product can have all three and still not be adopted.
Market access covers whether a product may be sold and paid for: regulatory approval, reimbursement, procurement. Clinical adoption covers whether it is actually used once all of that is in place. Market access is the ticket to the stadium. Adoption is whether anyone plays.
Approval Theater is the industry habit of celebrating the CE mark, the funding round, the pilot letter of intent and the reimbursement code as if they were the finish line. They are stage props. None of them puts a product into a physician's daily routine. Approval is the starting line. Adoption is the goal.
Rarely one person. Adoption is decided by the clinicians who have to use it in a running shift, the IT department that has to integrate it, the controlling department that has to justify the cost, the nursing staff whose workflow changes, and the referring physicians outside the building. A key opinion leader can open the door. The routine decides whether it stays open.
Routine use in eligible cases, not logins. Time to value for a new user. Whether external clinicians can access results without installing anything. A clinical KPI that moved after implementation. A financial case a hospital CFO accepts. StarMap turns these into seven scored success factors.
StarMap Alignment Check
Answer 14 questions and see how your solution maps against the seven success factors.
Start the Alignment Check