Medical device development requires careful consideration of user needs at every stage, yet many teams struggle to decide when to conduct different types of usability testing. The timing and approach of your testing can significantly affect both regulatory compliance and user safety outcomes. Understanding the distinction between formative and summative usability testing becomes crucial when developing devices that healthcare professionals and patients will rely on daily.
Formative testing occurs during the design and development process, allowing teams to identify and resolve usability issues before finalising their product. This iterative approach contrasts sharply with summative testing, which validates the final design’s usability performance. The question isn’t whether you need both approaches, but rather when formative testing should take precedence in your development timeline.
What is formative usability testing in medical devices?
Formative usability testing is an investigative approach to understanding how users interact with your medical device during its development phases. Unlike summative testing, which measures performance against predetermined criteria, formative testing explores user behaviour, identifies pain points, and uncovers unexpected usage patterns.
This testing methodology focuses on gathering qualitative insights rather than quantitative metrics. During formative sessions, you observe healthcare professionals or patients as they navigate your device’s interface, noting where they hesitate, make errors, or express confusion. These observations become invaluable inputs for design iterations.
Formative testing transforms user struggles into design opportunities, allowing teams to address usability challenges before they become embedded in the final product.
The regulatory landscape also recognises the importance of formative testing. Standards such as IEC 62366-1 explicitly acknowledge formative evaluation as a critical component of the usability engineering process, particularly for identifying and mitigating use-related risks.
When should you choose formative over summative testing?
Several scenarios strongly favour formative testing. Early in development, when your device concept exists primarily as wireframes or prototypes, formative testing helps validate fundamental design assumptions. Are users interpreting your interface elements correctly? Do they understand the intended workflow?
Formative testing becomes particularly valuable when developing innovative devices or targeting new user groups. If your device introduces novel interaction paradigms or serves users unfamiliar with similar technologies, formative sessions reveal how real users conceptualise and approach your solution.
Consider formative testing when facing tight development timelines as well. While this might seem counterintuitive, early formative testing prevents costly redesigns later in the process. Discovering that users consistently misinterpret a critical control during the prototype phase costs significantly less than making the same discovery during summative validation.
Complex devices with multiple user types also benefit from formative approaches. A patient monitoring system used by both nurses and physicians requires an understanding of how each group’s mental models and workflows differ. Formative testing explores these nuances before you commit to specific design decisions.
How to implement formative testing effectively?
Successful formative testing requires careful planning and execution. Begin by defining clear research questions rather than success criteria. Instead of asking “Can users complete task X in Y seconds?”, formative testing asks, “How do users approach task X, and what challenges do they encounter?”
Recruit participants who represent your actual user base, but don’t worry about achieving statistically significant sample sizes. Formative testing typically involves smaller groups—often five to eight participants per user type—focusing on depth rather than breadth of insights.
Create realistic scenarios that reflect genuine use contexts. Testing a surgical device in a quiet conference room provides different insights than testing in a simulated operating theatre environment. While perfect realism isn’t always feasible, consider environmental factors that might influence device interaction.
Document findings systematically, but avoid getting trapped in extensive reporting cycles. Formative testing’s value lies in rapid iteration, so establish streamlined processes for capturing insights and translating them into design modifications.
Plan multiple formative cycles throughout development. Early sessions might focus on overall concept validation, while later iterations examine specific interface elements or error recovery procedures. Each cycle should build on previous learnings while exploring new aspects of the user experience.
The investment in formative usability testing pays dividends throughout your device’s lifecycle. By understanding user needs and behaviours early, you create products that not only meet regulatory requirements but also genuinely serve the healthcare professionals and patients who depend on them. This user-centred approach ultimately contributes to better health outcomes and more successful product launches.
