Design Verification vs Design Validation
Outputs meet inputs, or the device meets the user’s real need?
What a comparison is not
A comparison is SPEQ’s reading of how two published documents differ. Neither is the right answer, it is not a determination of which applies to you, and neither is summarised in a way that replaces reading it.
In medical-device design controls, verification and validation are distinct, both-required activities. Design verification confirms that the design outputs meet the design inputs — you built to spec. Design validation confirms that the finished device meets user needs and intended uses under actual or simulated use conditions — you built the right device. Conflating them is a classic design-control finding.
| ASPECT | DESIGN VERIFICATION | DESIGN VALIDATION |
|---|---|---|
| Question | Do the outputs meet the inputs? | Does the device meet user needs and intended use? |
| Reference | The design inputs (requirements/specs) | User needs and intended uses |
| Conditions | Test/inspection against specifications | Actual or simulated use conditions |
| Uses initial production | Not necessarily | Performed on initial production units, lots, or equivalents |
| Typical activities | Analysis, test, inspection vs inputs | Clinical/usability/simulated-use, often incl. human factors |
| Both required? | Yes — verification precedes validation | Yes — validation confirms the verified design is the right one |
You are doing design verification when you confirm the design outputs satisfy the design inputs — testing and inspecting the design against its requirements.
You are doing design validation when you demonstrate, on production or equivalent units and under actual/simulated use, that the device meets user needs and intended uses — including human-factors/usability where relevant.
Verification checks you met the spec; validation checks the spec was the right one for the user. Both are mandatory design controls, and validation must be done on devices representative of production, under real use conditions — not on a bench prototype. The recurring finding is a firm that verified thoroughly against inputs but never validated against the user’s actual need.
Design Verification vs Design Validation: frequently asked questions
Common questions on how Design Verification and Design Validation differ and when each applies.
What is the difference between design verification and design validation?
Design verification confirms design outputs meet design inputs (built to spec). Design validation confirms the finished device meets user needs and intended uses under actual or simulated use conditions (built the right device). Verification is against the requirements; validation is against the user’s need.
Does design validation have to use production units?
Yes. Design validation is performed on initial production units, lots, or batches, or their equivalents, to ensure the device that will actually be made meets user needs — not just a lab prototype.
Where do human factors fit?
Human-factors/usability engineering is part of design validation for many devices — confirming users can operate the device safely and effectively under real use. It validates the design against actual use, which is exactly what design validation addresses.
Can you validate a design without verifying it?
Not credibly. Verification establishes that outputs meet inputs; validation assumes that foundation and adds the confirmation that the design meets user needs. Skipping verification undermines the meaning of a successful validation.