Advanced Product Quality Planning was designed to guarantee quality at launch. The framework, formalised by AIAG, aims to bake quality into the product from the first concept sketch rather than debugging it on the production floor. The intent is that you do not proceed to the next phase until the deliverables of the current one are genuinely complete and reviewed.
Here is what usually happens instead. A cross-functional team kicks off the project, and phase one deliverables get done on time. Then the timeline compresses. Engineering changes pile up, and supplier parts arrive late. Suddenly, the team is racing through the later phases, checking boxes to hit the launch date rather than using each gate as a genuine quality decision point. The PPAP submission goes out with a mix of real data and hopeful assumptions, production starts, and problems surface within weeks.
Everyone sits in a war room wondering why the same launch failures keep recurring. The framework is sound, but the failure is almost always in execution. When the customer demands parts by Q3, every gate review becomes a rubber stamp. Programs that skip APQP discipline to save time always spend that time later firefighting defects.
Timeline Pressure Overrides Quality Logic
APQP follows a logical sequence. Designs must be verified before tooling is committed. Processes must be validated before production is approved. But program timelines are typically set by commercial priorities, not engineering reality. When the launch date is fixed, the schedule dictates the engineering rather than the other way around.
I have seen phase three deliverables compressed into a fraction of the time they actually require across dozens of programs. Phase four production trials run once, fail partially, and get signed off anyway because there is no time for a second attempt. The team enters production with unresolved risks that show up as scrap rates, customer complaints, and warranty claims within the first few months.
These risks do not disappear. They surface exactly when correction is most expensive. A launch delay caused by thorough validation is measured in weeks. A launch that proceeds on schedule but fails in production causes months of customer escalations and recovery efforts that dwarf the original time savings.
FMEA Treated as Paperwork, Not Engineering
Design FMEA and Process FMEA are central APQP deliverables. Done well, they force the team to systematically identify potential failure modes and address them before they occur. Done poorly, which is most of the time, they are retrospective documents filled out after the design is frozen. They list risks everyone already knows about with RPN scores that never drive action.
I have reviewed hundreds of FMEAs over my career. The pattern is remarkably consistent. The severity, occurrence, and detection ratings are calibrated to produce acceptable RPNs rather than to reflect actual risk. High-severity, high-occurrence failure modes get detection scores of 2 or 3, implying the defect is almost certain to be caught. The actual detection mechanism is often a visual inspection by an operator at the end of the line.
A meaningful FMEA identifies failure modes the team genuinely had not considered. It generates action items like design changes, process controls, and additional testing that are tracked to completion. The document must be updated when new information arrives during testing or trials. If your FMEA is filed and never touched again, it is compliance theatre, not risk management.
Supplier Validation Left Too Late
Modern products depend on dozens of suppliers, and APQP requires that supplier parts are validated to the same standard as in-house components. In practice, supplier APQP status often becomes a blind spot. Tier 2 and Tier 3 suppliers submit PPAP packages that are incomplete or based on different test conditions than the final application requires.
Issues with material properties, dimensional conformance, or process capability surface during phase four, or worse, during launch. Corrections at this stage are expensive and slow because the supply chain is already committed. Strong programs assign supplier quality engineers to monitor Tier 1 APQP progress monthly and audit critical Tier 2 suppliers directly.
Weak programs send a spreadsheet asking for status updates and accept whatever comes back. Critical suppliers must be selected during phase one, not phase three. Their APQP progress should be monitored with the same rigour as internal work. Site visits, capability studies, and trial runs at supplier facilities must happen in parallel with internal development, not as an afterthought two weeks before launch.
Effective Supplier APQP Integration Timeline
- 01Phase 1: Supplier SelectionCritical suppliers chosen based on capability assessments, not solely on purchase price.
- 02Phase 2: Joint APQP KickoffExpectations, timelines, and specific testing requirements are established and agreed upon.
- 03Phase 3: Parallel DevelopmentProcess FMEA and control plan reviews conducted at supplier facilities alongside internal builds.
- 04Phase 4: Capacity and Capability RunsTrial runs at supplier sites verify Cpk and process stability before full PPAP submission.
The Cost of Skipping Validation
Organisations that treat APQP as bureaucracy rather than engineering discipline pay a predictable price. The data from manufacturing sectors is consistent. Launch scrap and rework costs are significantly higher for programs that compressed or skipped phase three and four activities. Warranty claims in the first twelve months correlate directly with the thoroughness of design FMEA and validation testing during APQP.
Time to stable production is a critical metric. The period from launch to achieving consistent Cpk greater than 1.33 takes two to three times longer when process capability was not proven during phase four. Engineering change volume in the first six months of production is another direct indicator of upstream APQP quality.
Impact of Disciplined APQP on Launch Metrics
Programs with disciplined phase gates typically issue 60 to 70 percent fewer post-launch changes. The irony of skipping APQP to save time is that it costs more time overall. The schedule always bows to engineering reality eventually. Quality problems find the timeline, and the resulting delays are far longer than the validation weeks that were skipped.
Building Cross-Functional Discipline
APQP demands involvement from design engineering, manufacturing engineering, quality, purchasing, and supply chain. In reality, each function often works in its own silo and presents finished work at gate reviews. Manufacturing engineering sees the design for the first time at the phase two gate. Quality sees the control plan at phase three. Purchasing has already committed to suppliers based on price, not capability.
The dashboard showed green status on all deliverables. It did not show the control plan was copied from a previous program.
I have seen companies implement sophisticated Product Lifecycle Management systems and still produce poor launches because team behaviour did not change. The software tracked that a design FMEA existed, but it did not track whether the FMEA was any good. Genuine cross-functional collaboration means manufacturing and quality are involved in concept reviews. It means purchasing sits in on design FMEAs to flag supplier feasibility concerns early.
The team must operate as an integrated unit, not a relay race where each runner hopes the previous one did their job. Start with gate reviews. Make them meaningful. Require evidence, not assertions. If a deliverable is not complete, the gate stays open. This will cause discomfort the first few times it happens, but leadership must support the decision to hold gates or the entire system collapses.
APQP Adaptation Across Industries
While APQP originated in automotive, its principles apply to any complex product introduction. I have helped adapt the framework for medical device manufacturers, aerospace suppliers, and industrial equipment builders. The underlying logic of planning quality early, verifying at each stage, and validating before commitment is universal across regulated manufacturing.
| APQP Phase | Automotive (AIAG) | Medical Device (ISO 13485) | Industrial Equipment |
|---|---|---|---|
| Phase 1: Plan | Voice of customer, design goals | User needs, design inputs | Customer specs, performance targets |
| Phase 2: Product Design | Design FMEA, prototyping | Design controls, verification | Concept testing, feasibility |
| Phase 3: Process Design | Process FMEA, control plan | Process validation, IQ/OQ/PQ | Manufacturing plan, tooling design |
| Phase 4: Validation | Production trial run, PPAP | Process qualification, validation lots | Site acceptance test, commissioning |
| Phase 5: Launch | Lessons learned, continuous improvement | Post-market surveillance | Warranty tracking, field performance |
The terminology shifts, but the engineering rigor remains identical. A medical device manufacturer must validate their process under ISO 13485 just as strictly as an automotive supplier must run a PPAP. An aerospace supplier building to AS9100 standards uses the same risk-based thinking. The specific regulatory deliverables change, but the failure modes of poor planning are exactly the same.
Organisations that take phase five seriously maintain a structured database of launch issues, root causes, and preventive actions. New programs start by reviewing relevant lessons from prior launches. This single practice can prevent repeating the same mistakes across successive programs. Every launch produces lessons. Capture them, categorise them, and build them into the next program's APQP checklist to create an organisational memory that prevents avoidable failures.