The Truth About Medical Device MVPs | Aaron Joseph & Russ Singleton
In their return to LifeSci Continuum, medtech veterans Aaron Joseph and Russ Singleton tackle one of the most misunderstood concepts in medical device development: the MVP (minimum viable product).
From surgical robotics to capital equipment, we discuss why “minimum” doesn’t mean cheap or simple and how smart teams use MVPs to learn faster without compromising safety, trust, or regulatory strategy.
In Medtech, Your MVP Isn’t Small. It’s Strategic.
Founders love to throw around the term MVP.
Usually wrong.
In software, MVP often gets treated like a stripped-down version you shove into the world fast so you can learn. In medtech, that thinking can get expensive fast. Or worse, it can box you into a regulatory, clinical, or commercial path that makes future growth harder than it needs to be.
That’s exactly why this latest Life Sci Continuum episode matters.
In my conversation with medtech veterans Aaron Joseph and Russ Singleton, we unpack one of the most misunderstood ideas in device development: what a minimum viable product actually means when safety, trust, workflow, reimbursement, adoption, and regulatory strategy are all in the room, glaring at you.
And here’s where Jobs to Be Done becomes incredibly useful.
Too many teams define their MVP by asking:
“What’s the smallest thing we can build?”
That’s the wrong question.
The better question is:
What is the smallest thing we can build that helps us learn whether we can solve the real job better than the current alternative?
That shift matters.
Because the “job” in medtech is rarely just functional. A surgeon is not just trying to complete a procedure. A hospital is not just buying a device. A clinician is not just adopting a tool based on technical performance. They’re hiring a solution to reduce risk, protect outcomes, fit into workflow, preserve reputation, satisfy procurement, support training, and avoid creating chaos.
That means your MVP cannot be defined by product features alone. It has to be defined by what you need to learn about the job, the context around the job, and the barriers that stop adoption.
Sometimes that means your MVP is not minimal in any normal-person sense of the word. Sometimes it is overbuilt, manually supported, operationally painful, and commercially ugly. Good. If it helps you learn the right thing faster, that may be exactly what it should be.
JTBD helps teams avoid a classic medtech screw-up: building an early device around what engineers can make instead of what the market actually needs to hire. It forces sharper questions:
What progress is the user trying to make?
What anxieties could stop adoption even if the tech works?
What workarounds are they firing to make room for this?
What has to be true for them to trust this in a real clinical environment?
That’s how you build an MVP that teaches you something useful instead of just giving you a demoable object and a false sense of momentum.
This episode gets into all of it: why some of the best early systems are intentionally unprofitable, why first-in-human platforms can accelerate learning, how bad regulatory framing can trap your future roadmap, and why clinician champions matter more than founders sometimes want to admit.
Because in medtech, speed is not about rushing to market with less.
It’s about learning the right things earlier, with less delusion.
If you’re building a medical device and trying to figure out what your market actually needs before you waste time, money, and credibility, connect with Bill on LinkedIn.
Follow Bill: / founderandcdo
Contact Bill: https://meshagency.com/lets-connect/
Video Podcast: / @billschickfcmo
Audio Podcast: https://www.buzzsprout.com/2380430
Explore Aaron and Russ’s ongoing writing on complex medical device development and connect with them directly to continue the conversation.
Follow Aaron: / ajosephprofile
Follow Russ: / russellsingleton
Visit https://www.mpo-mag.com/when-things-go-wrong-in-the-development-of-complex-medical-devices/ to read their latest article.