The Design Control Process in New Product Development
A quality system is not paperwork added before launch. Here are the standards that apply, the design controls behind them, and how much formality a startup actually needs.
January 26, 20164 min read
Written by Onega Ulanova, IRCA Lead Auditor, MS Eng. & Tech. Management, Executive MBA
Co-Founder, Quality Management Executive & Lead Auditor
Published January 26, 2016Updated September 2, 2026
A quality management system is not paperwork you add before launch. It is the set of decisions, reviews and records that make a product repeatable — and retrofitting it after the design is frozen is where programs lose months.
The design control process is the documented chain from user needs to design inputs, outputs, verification, validation and transfer to manufacturing. This guide compares ISO 9001, ISO 13485 and IATF 16949, walks the design controls stage by stage, and shows how testable requirements, FMEA and design verification and validation keep quality problems out of production.
Which standard applies to your product
Standard | Applies to | What it mainly governs | Certification typically needed? |
|---|---|---|---|
ISO 9001 | Any manufactured product or service | General quality management, process control, continual improvement | Often required by industrial customers |
ISO 13485 | Medical devices | Design controls, risk management, traceability, records | Yes, for most regulated markets |
FDA 21 CFR Part 820 | Medical devices sold in the US | Design controls and the design history file | Regulatory requirement, not a certificate |
IATF 16949 | Automotive supply chain | APQP, PPAP, defect prevention | Yes, to supply tier-one customers |
AS9100 | Aerospace and defence | Configuration management, counterfeit-part control | Yes, for the supply chain |
ISO 14971 | Medical devices | Risk management across the lifecycle | Applied alongside ISO 13485 |
Consumer products usually need none of these formally — but they still need the underlying discipline, because a contract manufacturer will ask for specifications, tolerances and acceptance criteria regardless of whether an auditor ever will.
Design controls, stage by stage
Stage | What it means in practice | Evidence produced |
|---|---|---|
Design inputs | Turn user needs into measurable, testable requirements | Requirements specification with acceptance criteria |
Design outputs | Drawings, models, BOM, software and specifications | Released design package under revision control |
Design reviews | Cross-functional checkpoints at planned milestones | Signed review minutes with actions and owners |
Verification | Did we build the product right, against the spec? | Test protocols and reports with pass/fail data |
Validation | Did we build the right product, for real users? | Usability and field validation reports |
Design transfer | Hand the design to manufacturing so it can be built repeatably | Work instructions, inspection plan, first-article report |
Verification and validation are not synonyms, and confusing them is the most common quality failure in early-stage programs. A part can meet every dimension on the drawing and still be unusable in the field.
Verification asks whether the product matches the specification. Validation asks whether the specification was right.
Requirements that can actually be tested
Weak requirement | Testable requirement |
|---|---|
The housing should be durable | Survives 10 drops from 1.2 m onto concrete with no loss of function |
The device should be easy to use | 90% of untrained users complete setup in under 3 minutes without assistance |
Battery life should be good | Delivers 8 hours of continuous operation at 25 °C after 300 charge cycles |
The finish should look premium | Gloss level 60±5 GU, no visible sink marks over 0.05 mm |
Every requirement should name the measurement, the condition and the threshold. If nobody can write a test for it, it is a wish, not a requirement — and it will be argued about during production.
Risk management, in proportion
- Start a design FMEA at concept, not at tooling. Its value is in changing the design, which is only possible early.
- Rank by severity first. A rare failure that injures someone outranks a frequent cosmetic defect.
- Tie each high risk to a control and a test. An unmitigated row in an FMEA is a promise you did not keep.
- Run a process FMEA before design transfer. Most field failures come from assembly variation, not from the design.
- Revisit after every significant change. A material substitution invalidates the analysis that justified it.
What manufacturing needs from the quality system
Deliverable | Purpose |
|---|---|
Controlled drawings with GD&T | Defines what is inspectable and what is cosmetic |
Inspection plan and sampling criteria | Tells the factory what to measure and how often |
First article inspection report | Proves the first parts off tooling meet the drawing |
Work instructions and assembly aids | Makes the build repeatable across operators and shifts |
Non-conformance and CAPA process | Turns a defect into a fixed root cause rather than a rework pile |
Supplier qualification records | Prevents an unvetted second-source part entering the line |
Our design for manufacturing work covers turning a validated design into a build package, and choosing a manufacturer covers how to judge whether a factory's own quality system is real.
How much quality system does a startup need?
Situation | Sensible level of formality |
|---|---|
Consumer product, first run under 1,000 units | Requirements spec, drawing control, inspection plan, FAI |
Industrial product sold to businesses | The above plus ISO 9001-aligned processes and CAPA |
Medical device | Full ISO 13485 and ISO 14971 from day one — retrofitting is far more expensive |
Automotive or aerospace supplier | Customer-mandated system, in place before you quote |
The minimum viable quality system is the one that lets you answer three questions with records rather than memory: what was specified, what was verified, and what changed since.
The design history file, section by section
Section | Contents | Created during | Common gap |
|---|---|---|---|
Design and development plan | Scope, responsibilities, review points | Concept | Never updated after the first revision |
Design inputs | User needs translated into testable requirements | Concept to design | Requirements written as wishes, not measurements |
Design outputs | Drawings, specifications, code, labeling | Design | Uncontrolled drawing revisions |
Design reviews | Minutes, attendees, action items and closure | Every phase gate | No evidence actions were closed |
Verification | Test protocols and results against inputs | Late design | Testing done but protocol never written |
Validation | Evidence the device meets user needs in use | Pre-launch | Run on prototypes rather than production units |
Design transfer | Manufacturing procedures, inspection plans | Pre-production | Tribal knowledge never documented |
Design changes | Change records with impact assessment | Throughout | Changes made in CAD without a record |
Writing requirements that can be verified
- Weak: 'The enclosure shall be durable.' Verifiable: 'The enclosure shall survive 26 drops from 1.0 m onto concrete per IEC 60068-2-31 with no loss of function.'
- Weak: 'Battery life shall be long.' Verifiable: 'Runtime shall exceed 8 hours at 25 °C with the radio transmitting once per minute.'
- Weak: 'The device shall be easy to clean.' Verifiable: 'External surfaces shall withstand 200 wipe cycles with 70% IPA with no crazing or legend loss.'
- Weak: 'Assembly shall be efficient.' Verifiable: 'Final assembly shall complete in under 90 seconds by a trained operator using documented fixtures.'
Scaling the system to the product
Product class | Minimum system | Typical documentation effort |
|---|---|---|
Consumer accessory | Controlled drawings, incoming inspection, change log | 1-2 weeks |
Connected consumer device | Above plus verification protocols and CAPA log | 3-6 weeks |
Industrial equipment | ISO 9001-aligned procedures and supplier controls | 2-4 months |
Class I medical device | 21 CFR 820.30 design controls, DHF | 3-6 months |
Class II medical device | Full QMS, ISO 13485, risk file per ISO 14971 | 6-12 months |
Key takeaways
- Design control is a record built during development, not documentation written before an audit.
- Every design input should name a measurement, a condition and a limit.
- Validate on production-equivalent units, not prototypes.
- Scale the quality system to the product's risk class rather than adopting the heaviest template available.
Running the design control process without drowning the team
The design control process fails in two directions: teams that document nothing and teams that document everything twice. The workable middle is a single traceability spine that links user needs to design inputs, inputs to outputs, outputs to verification evidence, and the whole chain to validation with real users.
Keep it in one system, review it at each gate, and treat the design history file as a by-product of doing the work rather than a separate writing project at the end.
- One requirement, one ID. Every input gets a stable identifier used in tests, drawings and reports.
- Verification before validation. Prove you built it right, then prove you built the right thing.
- Change control from first tooling. Informal changes after T1 are where traceability breaks.
- Risk file is living. Update FMEAs when test results contradict the assumed severity or detectability.
- Gate reviews with evidence. A gate that accepts promises instead of data is not a gate.
Work with LA NPDT: if you are moving from here to execution, start with our our product development process or talk to us about end-to-end product development.
Frequently asked questions
What is a quality management system in product development?
It is the documented set of processes, reviews and records that control how a product is specified, designed, verified and transferred to manufacturing. In development it shows up as requirements with acceptance criteria, design reviews, verification and validation testing, change control and a traceable record of what was decided and why.
What is the difference between verification and validation?
Verification confirms the product meets its written specification — dimensions, performance, safety limits. Validation confirms the specification was correct by testing the product with real users in real conditions. A design can pass verification completely and still fail validation if the requirements were wrong.
Does a startup need ISO 9001 before manufacturing?
Usually not for a first consumer product run — controlled drawings, an inspection plan and a first-article report cover the practical need. Certification becomes important when industrial or enterprise customers require it in purchasing terms, and it is mandatory in effect for medical, automotive and aerospace supply chains under their own standards.
What is a design history file?
A design history file is the compiled record demonstrating that a device was developed according to its design plan and design controls: inputs, outputs, reviews, verification and validation results, and change records. For medical devices it is a regulatory requirement; for other products the same compilation is simply good evidence during audits, disputes or recalls.
When should quality planning start in a new product program?
At concept, when requirements are first written. Design inputs, the initial risk analysis and the review schedule cost very little at that stage and shape the design. Introduced after design freeze, the same activities generate rework, retesting and tooling changes rather than better decisions.
Filed under:Education
Tagged:Product Development
Related articles
All articles
Consumer Product Design: Process, Costs and Timeline
From discovery to production launch: how consumer product design is actually run, what it costs at each complexity level and how long it takes.
Medical Device Design Companies: Who Fits Which Device Class
Which medical device design companies fit Class I, Class II and Class III programs, what design controls and ISO 13485 actually cost, and when a general product firm is the wrong call.
Consumer Product Design Firms: Who Fits Which Product
A buyer guide to consumer product design firms - housewares, sporting goods, personal care, toys and electronics - with costs, retail realities and honest hand-offs.
Services related to this guide
- Product design servicesIndustrial design and CAD taken all the way to manufacturable files.
- Rapid prototypingWorking prototypes in days, from 3D printing to vacuum casting.
- Electronic design servicesSchematic, PCB layout, firmware and bring-up, through to production handoff.
- Product development examplesReal projects we designed, prototyped and shipped.