{"href":"http://player.captivate.fm/services/oembed?url=http%3A%2F%2Fplayer.captivate.fm%2Fepisode%2F3500f1d0-13c3-41ff-9710-fd417b24a787","version":"1.0","provider_name":"Captivate.FM","provider_url":"https://www.captivate.fm","width":600,"height":200,"type":"rich","html":"<iframe style=\"width: 100%; height: 200px;\" title=\"Determining User Needs for Your Medical Device\" frameborder=\"0\" scrolling=\"no\" allow=\"clipboard-write\" seamless src=\"http://player.captivate.fm/episode/3500f1d0-13c3-41ff-9710-fd417b24a787\"></iframe>","title":"Determining User Needs for Your Medical Device","description":"<p>What is a user need, and when should you start working on them? How can you figure out what the user truly needs \u2013 and by the way, do you know who the user is? These are some of the topics you\u2019ll hear about in today\u2019s episode.</p><p>Jesseca Lyons joins the podcast today to share more information about user needs. Jesseca is a Mechanical Engineer who\u2019s spent most of her career gathering and defining requirements for new product design and development in the medical device industry. During today\u2019s conversation, you\u2019ll learn more about how Jessica is thinking about challenges in getting to user needs, using Root Cause Analysis to get to true user needs, and determining who will be interacting with the medical device and which ones are users.&nbsp;</p><h3>Some of the highlights of this episode include:</h3><ul><li>Themes that trip people up regarding user needs and how Jesseca helps them</li><li>Fears about problems during FDA inspections and 510k submissions</li><li>What Jesseca thinks of when she thinks of user needs</li><li>Guiding a customer through figuring out a user need</li><li>What makes it difficult to get to user needs</li><li>An example of a standalone design input</li><li>When to stop divergent thinking</li><li>More user needs pitfalls</li><li>Which people are users</li></ul><h3>Memorable quotes from Jesseca Lyons:</h3><p><em>\u201cMost of the time, our user needs aren\u2019t really doing a good job of telling us what the user is actually looking for; what problem we\u2019re trying to solve.\u201d</em></p><p><em>\u201cI always found it interesting that we were so willing to solve a problem before we really understood what the requirements were.\u201d</em></p><p><em>\u201cAnyone who comes in contact with your medical device could be a user.\u201d</em></p><p><em>\u201cEvery fear is a legitimate fear.\u201d</em></p><p><em>\u201cYour design inputs shouldn\u2019t be so restrictive that there\u2019s only one right answer.\u201d</em></p><h3>Links:</h3><p><a href=\"https://www.linkedin.com/in/jessecalyons/\" rel=\"noopener noreferrer\" target=\"_blank\">Jesseca Lyons LinkedIn</a></p><p><a href=\"https://www.linkedin.com/in/etiennenichols/\" rel=\"noopener noreferrer\" target=\"_blank\">Etienne Nichols LinkedIn</a></p><p><a href=\"https://www.greenlight.guru/academy\" rel=\"noopener noreferrer\" target=\"_blank\">Greenlight Guru Academy</a></p><p><a href=\"https://community.greenlight.guru/\" rel=\"noopener noreferrer\" target=\"_blank\">MedTech Excellence Community</a></p><p><a href=\"https://www.greenlight.guru/\" rel=\"noopener noreferrer\" target=\"_blank\">Greenlight Guru</a></p>","thumbnail_width":300,"thumbnail_height":300,"thumbnail_url":"https://artwork.captivate.fm/faddd282-b272-4312-8d00-edb4370d08e8/3dbe00d6-9c45-4621-a8e2-defa228b7c7b.png"}