Are you Spending Enough Time Defining and Managing Requirements for your Medical Device?

Global Medical Device Podcast · 18 Nov 2020 · 35m · Episode 168

What this episode covers

Devin Mack, mechanical engineer and owner of Enqual, discusses the critical importance of defining and managing requirements in medical device product development. He argues that companies should spend approximately one-third of their project time on this phase to avoid chaos and ensure market fit. Mack advocates for early cross-functional involvement from quality, manufacturing, and regulatory teams, rather than siloed engineering efforts. He also shares his 'stoplight' methodology for tracking progress against customer specifications and emphasizes the need for usability models to get it right the first time.

Other shows on the same ground, closest first.

  • Let's Combinate · 26m

    176 - The Fastest Way to Ruin Drug/Device Development (And How to Avoid It!) with Eric Sugalski

    Eric Sugalski, founder and CTO of Archimedic, explains that the fastest way to ruin drug-device development is premature concept lock and misaligned outsourcing strategies. He argues that companies must distinguish between needing overflow capacity versus specialized expertise, such as human factors or industrial design, to avoid the 'piecemeal approach' that destroys innovation. Sugalski emphasizes the importance of early, hands-on user research and open-source quality management systems to bridge the gap between engineering and clinical reality, warning that locking down requirements before validating use cases injects costly redo loops into the project.

  • The Pragmatic Embedded Podcast · 50m

    Requirements Engineering, part 2: A Practical Process for Safety-Critical Development

    Jeff Gable and Luca engineer discuss a rigorous process for requirements engineering in safety-critical development, particularly for medical devices. They distinguish between prototyping (technical feasibility) and MVPs (market viability), emphasizing that design-controlled requirements must be minimal yet comprehensive, including extensive error handling. The hosts advocate for writing test cases alongside requirements, tracking requirements completion for honest project status, and using 'tracer bullets' to reduce uncertainty early in implementation.

  • Being an Engineer · 43m

    Dakota Welker | User Needs, Design Inputs, Verification & Validation

    Dakota Welker, founder of Think MedTek, explains his four-phase product development methodology for medical device startups, emphasizing user needs, design inputs, verification, and validation. He details how he rescues stalled projects by clarifying scope and documentation, and describes a specific case where bringing manufacturing in-house and negotiating with multiple vendors reduced costs by 50%. Welker also discusses his transition from automotive and pneumatics to medical devices, his focus on CFD tools like Simscale, and the importance of balancing engineering rigor with client communication.

  • Being an Engineer · 53m

    S7E19 Ryan Schoonmaker | How to Take A Structured Approach to Solving Engineering Problems

    Ryan Schoonmaker, founder of Tight Line Solutions and former Director of Mechanical Engineering at Beta Bionics, Dexcom, and BD, explains how to bring structure to chaotic product development. He emphasizes that successful execution requires clear requirements, robust assembly specifications, and early decisions on critical elements like component colors to avoid regulatory delays. Schoonmaker draws on his experience with the Dexcom G6 and G7 to illustrate how narrowing down system failures and managing technical debt differently at startups versus large enterprises leads to predictable outcomes.

  • Let's Combinate · 21m

    157 - Design Inputs that Don't Suck, Risk Control Measures and Problems with Verification with Chuck Ventura

    Chuck Ventura, founder of Ventura Solutions and CEO of HemoTek, explains why poor design inputs are a primary cause of delayed product development and verification failures in medical device and combination product projects. He advocates for spending 30% of project time on design inputs using concurrent engineering, where systems engineers collaborate with verification teams early to define clear acceptance criteria. Ventura also clarifies the structural relationship between user needs, risk controls, and design inputs, arguing that risk controls should serve as parent requirements to design inputs to ensure traceability and effective risk management.

The summary, chapters and topics are generated from the episode’s audio by this directory, not written by Global Medical Device Podcast. The episode itself belongs to its publisher.