Verification and validation — V&V — is the phase of product development that most organizations understand best in principle and manage worst in practice. In principle, V&V is the systematic process of confirming that a product was built correctly and that it performs the function it was designed to perform. In practice, it is the phase that absorbs the schedule overruns, budget exceedances, and last-minute design changes that accumulated quietly throughout earlier phases of the program.
The reason is almost always the same: V&V was treated as a late-stage activity when it should have been planned — and in important respects, begun — at the front end of the program.
The Distinction That Matters
Verification answers the question: did we build the product right? It confirms that the product meets its specified requirements — performance parameters, material specifications, dimensional tolerances, and regulatory compliance requirements.
Validation answers the question: did we build the right product? It confirms that the product, as built to specification, actually meets the needs of the users it was designed for — performing as intended in the intended use environment, by the intended users, for the intended purpose.
These are different questions. A product can pass verification — it meets every specification — and fail validation — it does not work the way customers actually use it in the field. Both questions must be answered, and neither answer can substitute for the other.
Why V&V Fails When It Starts Late
The most common V&V failure is not a testing failure. It is a planning failure that does not reveal itself until testing begins.
V&V testing requires a stable product. You cannot validate a product that is still changing. This means the decision to begin formal V&V testing is, in practice, a commitment to design freeze. When V&V is planned late, this commitment arrives before the team is ready. The protocol was written against a product definition that was still evolving. When testing begins, the product changes — and testing has to be repeated, partially or entirely, against the revised design. The schedule impact compounds with each cycle.
Organizations that plan V&V early avoid most of this failure mode. They define the testing approach against the design intent before the design is mature enough to test. They identify which performance attributes will be most difficult to validate and build the development program around resolving those difficulties before formal validation begins. They treat V&V planning as a design input rather than a design output.
The Components of a V&V Strategy
A V&V strategy developed at the right time addresses: What are the critical performance attributes? What is the intended use and user population? What regulatory standard applies? And what will a failed test result require? Each question has a different remediation path with a different timeline and cost. Organizations that have thought through failure scenarios before testing begins respond to failures faster and more effectively.
V&V in the Regulatory Context
In regulated industries, V&V is not just an internal quality assurance activity. It is a regulatory commitment — the primary evidence base for demonstrating that a product meets the requirements applicable to its classification and intended use.
FDA 21 CFR 820.30 requires that design validation confirm the device conforms to defined user needs and intended uses. ICH Q8 addresses pharmaceutical development in analogous terms. The expectation is not just that V&V was performed, but that it was planned systematically, executed against a defined protocol, and that the results are traceable to the requirements they were designed to address.
What Starting Earlier Actually Requires
Starting V&V planning early requires three organizational commitments. The first is a willingness to think about failure before the product exists — asking what could go wrong in use, and how we would know. The second is a stable requirements foundation — V&V planning cannot begin meaningfully until customer requirements and product requirements are at least preliminarily defined. The third is cross-functional coordination — V&V planning requires input from engineering, quality, regulatory, manufacturing, and the commercial team.
V&V done well is expensive and time-consuming. V&V done late, with rework cycles driven by design instability and planning gaps, is more expensive and takes longer. The investment in early, systematic V&V planning does not eliminate the work. It ensures the work that gets done is the right work, done once, producing results that hold.
MKA Insights works with life sciences, medical device, and bioprocessing organizations on V&V strategy, NPD process design, and regulatory planning. Contact us.