MVP (Minimum Viable Product) in Medical Product Development

Shen Hsin-Wei, Vice President of Medical Affairs, BizLink Biotech Venture Capital

In the world of medical innovation, product development cycles are long, regulations are strict, and risks are extremely high. At the same time, it is a field urgently in need of innovative solutions that genuinely improve clinical workflows and patient outcomes. Therefore, introducing the concept of the MVP (Minimum Viable Product) can help reduce risk and accelerate validation—while preserving the value of innovation.

What Is an MVP?

MVP originally refers to creating a product prototype with minimal resources in the shortest time to validate core assumptions. The idea comes from the software and startup world, helping teams avoid investing heavily in products the market does not need.

In the medical field, an MVP is not an incomplete medical device. Rather, it is a testable version designed to validate core value assumptions. It might be:

  • A functional UI mock-up

  • A workflow storyboard simulating the patient journey

  • A Wizard-of-Oz–style manually supported service

  • An initial clinical workflow integration test (shadowing study)

The key is that it does not need to be perfect or clinically deployable—
but it must validate whether someone wants it, whether someone will pay for it, and whether someone is willing to participate in development.

Why Medical Products Need MVPs Even More

Medical entrepreneurs face challenges such as:

  • Complex and conservative clinical workflows

  • High development costs and strict regulatory barriers

  • Different users (clinicians) and buyers (hospitals)

  • Long feedback cycles

Without early validation of practicality and product–market fit, greater investment means greater risk.

MVPs help teams validate critical assumptions with minimal cost and determine whether further investment is worthwhile.

However, medical MVPs differ from those in consumer electronics or software. Due to strict safety and regulatory demands, adjustments are required. For example, the UK consulting firm IDC recommends developing a complete Product Requirement Specification (PRS) even at early stages to clearly define functions and regulatory needs—preventing rework and delays later. This contrasts with the typical “launch fast and iterate” mindset in general startups.

Common Types of Medical MVPs

1. Interactive Workflow Simulations

Using tools like Figma to create physician or patient workflow prototypes and observing real user feedback.

2. Wizard of Oz Testing

Example: a smart monitoring system “detects abnormal vitals,” but the backend is manually operated.
This validates whether caregivers would act based on system feedback.

3. Patient Journey Mapping

Observing and reconstructing real patient scenarios to identify how and where a product fits into the clinical workflow.

4. Concept + Business Model Validation

Sometimes, a single presentation slide plus a feasible hospital billing model is enough to test hospital willingness to adopt or reimburse.

Key Principles for Building a Medical MVP

Clarify the Hypothesis

  • Are you validating whether doctors will spend 5 minutes using it?

  • Whether patients will report data?

  • Whether payers (e.g., insurance/NHI) recognize its value?

Remove Non-Essential Features

  • Anything unrelated to validating the core assumption should be excluded.

  • MVP ≠ MVP+.

Use the Fastest Possible Testing Method

  • Excel simulation, hand-drawn workflows, or acting as the “AI” yourself.

  • Real feedback is more important than elegance.

Test with True Decision-Makers

  • Engage actual users or buyers—not only researchers.

Leave Room for Future Innovation

  • Even early MVPs should consider future scalability and deeper technology integration.

Common Misconceptions

  • Misconception: MVP must be feature-complete but cheap.
    Reality: MVP validates one “core assumption,” not all functions.

  • Misconception: A successful MVP means the product is ready for market.
    Reality: MVP is only the first checkpoint. Full development includes design, regulatory review, clinical validation, and market testing.

Successful MVP Cases

Butterfly iQ (Handheld Ultrasound)

Early versions used rough UI and workflow diagrams tested with clinicians, validating clinical demand before investing in chip and AI automation.

A Taiwanese Remote Care Team

Initially used LINE + Google Forms for patient reporting and caregiver alerts.
After demonstrating real demand, they built a full platform.

MVP as a Safety Parachute for Medical Innovation

Medical entrepreneurship is a long-distance marathon involving multiple iterations and challenges.
The MVP is not merely a product prototype—it is a decision-making tool, enabling teams to “fail smarter.”

Only through continuous dialogue with clinical environments, rapid testing, quick iteration, and careful balancing of regulatory requirements and user needs can innovators find truly viable paths in the high-risk field of medical innovation.