Your next launch inherits your current quality debt

I've stood in enough launch war rooms to recognise the pattern. Rivian is pushing toward R2 production while the R1 platform still carries a reputation for drivetrain faults, panel inconsistencies, and firmware patches deployed like field dressings on a wound that needs surgery. The press speculates about pricing and timelines. Nobody asks the question that actually determines whether R2 succeeds: what did the organisation learn on R1, and has that learning been institutionalised—or merely survived?

Your quality system is organisational, not per-project

Organisations don't reboot their quality culture between programs. When I built a greenfield quality department at SNOP for over 900 employees, the most important decision wasn't which gauge to buy or which standard to frame in the lobby. It was whether stop authority would be treated as real or performative. Whether QRQC meant a structured response within hours or a form completed three days late to satisfy a customer audit. Whether 8D was a closure tool or a parking lot for issues everyone hoped would fade quietly.

70% defect-cost reduction. 98% customer satisfaction. Those results at SNOP didn't come from a cleaner second product line. They came because the first line was held to a standard and the discipline transferred. The organisational muscle you build on day one is the only thing the next program genuinely inherits. Fixtures, software, even experienced talent—those can be procured. Discipline cannot. It has to be demonstrated until it becomes the thing people do without being asked.

The Airbus portfolio I walked into had critical customer escalations as routine. Within a quarter we drove that to zero. Not by launching something new—by closing open issues, tightening the stop-authority threshold, and treating escalation prevention as a daily operational discipline rather than a quarterly review slide. That system now supports the next program phase. Had we launched into it carrying open wounds, we'd have been firefighting on two fronts instead of stabilising one.

Rivian's situation isn't unique to EVs or to American manufacturing. I've watched the same pattern at plants across Europe and North America. Leadership gets excited about the new platform. Resources shift. The current line quietly degrades. Escapes that were "contained" become baseline. PFMEA entries that were never updated become the reference standard for the new model. The 8Ds still "in progress" get reclassified as resolved because nobody has the appetite to argue during a launch.

APQP should capture lessons learned. It usually captures wishful thinking

Advanced Product Quality Planning exists to feed experience forward. Every escape, every near-miss, every customer complaint from the prior program should inform the risk analysis of the next. I've reviewed APQP packs that contained more optimism than engineering data.

At WITTE Automotive we ran QRQC with rigour. Issues closed, not parked. Every A3 had to answer the mechanism question: not just what failed, but why the system allowed that failure to reach the customer. If the team couldn't answer that, the 8D stayed open and the issue stayed visible on the Q-Wall. When we launched the next program, those closed A3s were the single most valuable input into the new PFMEA. The understanding was real, tested, earned. The documentation was almost incidental.

Manufacturers who get this right treat their current quality escapes as prepaid tuition. You've already paid for the lesson—in warranty costs, customer complaints, line stoppages. Fail to transfer that learning into the next program's risk analysis and you're buying the same lesson again at full price.

Rivian's R1 issues—drivetrain noise, electronic anomalies, build inconsistencies—are a curriculum, not a customer-satisfaction scorecard. Every one of those escapes should be generating a specific PFMEA entry, a control plan revision, a manufacturing process review for R2. If those entries don't exist in the planning documentation, the organisation is betting that the new platform is somehow immune to the old platform's failure modes. That's hope dressed up in a milestone chart.

The launch schedule doesn't wait for quality maturity. The customer does.

The most dangerous phrase in manufacturing is "we'll resolve it during launch." No. You'll resolve it after launch, under commercial pressure, with customers watching, at roughly ten times the cost of addressing it beforehand.

Launch schedules are set by commercial teams who understand market windows. Quality maturity is achieved by engineering teams who understand failure modes. Those two timelines rarely align. The role of quality leadership is to make the gap visible—quantified, costed, escalated—so the decision to launch is an informed one, not a default driven by calendar pressure.

Quality debt compounds. The interest is paid in customer trust, and the principal is never forgiven—only refinanced into the next program.

The 50% reduction in EASA audit findings I delivered in a single cycle at Airbus wasn't about working harder during the audit window. It was about resolving systemic issues before they could compound across the next production milestone. Same principle governs any launch. Your current line has unresolved escapes, weak stop authority, PFMEA entries untouched since the last model year? Those problems won't resolve themselves when you add the complexity of a new program. They will multiply.

Rivian doesn't have a manufacturing problem unique to EVs. It has a quality debt problem that will follow R2 directly from R1 unless the organisation decides—deliberately, visibly, before the launch gates open—that the next program starts with a settled balance on the current one. Every manufacturer faces this choice eventually. The ones who make it deliberately succeed quietly in the market. The ones who don't succeed loudly in the headlines for all the wrong reasons.