Medical Device Usability and Customer Requirements Validation
Updated: 4 days ago
Reviewed by Aaron Lyon, President of A.P. Lyon and former Director of Quality Assurance and International Regulatory, with more than 30 years in medical device quality. Last reviewed November 10, 2026.
When is customer feedback insufficient to answer a usability question?
Choose human-factors documentation for user-interface tasks and use-related risk, and customer-requirements validation for structured feedback on how a defined configuration meets customer needs. Positive customer reactions are valuable, but they do not automatically establish safe and effective use of critical tasks.
Customer feedback and usability evaluation answer related but different questions. Customers can tell you whether a product addresses their needs. Human factors work examines how intended users interact with the device and where use errors can lead to harm. A useful plan identifies the question before choosing a study method.
Decision table: match the gap to the evidence
Situation | Decision | Evidence to retain |
Users misunderstand a control | Examine the task, interface and use-related risk. | Observed behavior and contributing conditions. |
Customers prefer a feature | Assess the defined need and feedback method. | Participant context, configuration and responses. |
A critical task needs validation | Plan evidence matched to intended users and conditions. | Task rationale, study records and limitations. |
Define users, environments and tasks
Describe the intended users’ relevant characteristics, the use environment and the tasks they perform. Include interactions with packaging, displays, controls and instructions where relevant. Identify tasks in which an error could have important consequences and connect them to use-related risks.
Choose evidence that fits the question
Early evaluations can reveal misunderstandings while changes are still practical. Later evaluations need a justified design, representative conditions and clear interpretation of observations. Record the configuration tested, assistance given and deviations from the plan. Customer preference results can inform development, but satisfaction alone does not establish that use-related risks have been adequately controlled.
Worked example: a fictional planning decision
A fictional home-use device has an attractive display and receives favorable preference scores. During an evaluation, some intended users confuse a confirmation symbol with a completed treatment. The preference result does not resolve this task problem. The team retains the favorable feedback, links the misunderstanding to its use-risk analysis and evaluates the interface or instructions before deciding what further evidence is needed.
Implementation record: make the decision reviewable
Use a task record with the user group, environment, interface revision, expected action, observable error, assistance provided and consequence of error. Separate what the participant did from the observer's explanation of why it happened. Define beforehand how training and instructions represent actual use. If a session includes coaching unavailable in normal use, make that visible when interpreting results. Feed findings into risk controls and change assessment, then specify which earlier observations remain applicable after a revision.
Applicability, exceptions and conclusion limits
Formative work can explore alternatives; a later validation question needs its own justified scope. No fixed participant count or generic survey establishes adequacy for every device. A professional-use device and a home-use device may involve different users and constraints. If a feature changes only appearance, document the assessment rather than assuming either that every study must be repeated or that no use impact is possible.
Choose documentation by the missing workflow
Select the Human Factors and Usability Engineering Procedure for the use-engineering workflow, or Customer Requirements Validation for the feedback workflow. Check overlap if buying the software bundle, which already includes human-factors documentation. If your approved process covers both and the missing element is actual evaluation evidence, another document will not close that gap.
Use human factors and usability engineering documentation for user-interface planning, use-related risks and evaluation activities.
Use customer requirements validation when collecting feedback on a defined configuration and assessing how it meets customer needs.
Common mistakes and an additional practical check
Avoid coaching participants through difficulties and then treating the completed task as evidence of independent use. Record assistance and assess what the difficulty reveals about the interface or instructions.
Users may prefer a smaller label, yet have trouble recognizing a critical warning during a simulated task. The preference result and the use-risk finding should both be recorded; one should not erase the other.
Review checklist before approving the workflow
State the evaluation question.
Define users, tasks and environments.
Identify the device configuration and training.
Record observed difficulties and their causes.
Connect findings with design and risk decisions.
Inside the supplied document: planning the usability evidence
Source: supplied A.P. Lyon SOP 7-042, revision 2, effective September 19, 2026. This is a selected preview. Image wording is retained from the source; the explanation below is adapted. It is not an executed record or a quotation from a regulation.
The supplied procedure begins with a defined interface, users and use context. That makes an evaluation plan more useful than a generic statement that the product is easy to use.

Selected original document text: planning the usability evidence.
Identify the device and interface versions, intended users, user groups and use environments.
Plan hazard-related scenarios, evaluation methods, participant rationale and decision criteria.
Link use-related hazards, controls, formative findings and summative results to risk and design records; document exclusions and applicability decisions.
Buyer decision: Choose the Human Factors and Usability procedure when the missing work concerns use-related risk and evaluation. Customer Requirements Validation addresses a related customer-needs question. Neither a blank file nor a satisfaction survey establishes that critical use tasks have been evaluated.
Scope and how to use this guide
This is general implementation guidance for selecting and organizing documentation. The worked planning scenarios are fictional. Separately labeled document extracts come from the supplied A.P. Lyon files identified in their source notes. Neither is a completed study or evidence of compliance. Apply the requirements for your device, process and markets, and have the responsible technical and quality personnel approve decisions. Product downloads supply editable documentation; your organization remains responsible for its implementation and evidence.
Related buyer decisions
Primary references and review date
Technical references and linked product scope checked October 13, 2026. Regulatory summaries are identified above; checklists, decision tables and fictional examples are A.P. Lyon implementation recommendations. Consult the full applicable standards and regulations before approving a project.
Publisher and editorial standards
Published by A.P. Lyon. Aaron Lyon is the company’s founder; his professional background is described on the About page. These guides use AI-assisted research and drafting. Each guide is reviewed and approved by Aaron Lyon before publication; that review does not certify applicability to your device.
Building a complete quality system? Build Your QMS lets you choose ISO 13485 + FDA QMSR, Dual-Standard or ISO 9001:2026 procedures in one place, and applies volume discounts automatically: 20% off 5–9 procedures, 35% off 10–19, 50% off 20–39 and 60% off 40 or more.
Not sure where your quality system stands? Take the free QMS gap check: about 20 questions, an instant report of your gaps by clause, and the procedures that close each one.
Just getting started? The free Startup Quality Plan shows which procedures you need now, which can wait, and how long they take to put in place.
Comments