Boeing has stood up new 737 assembly capacity, and the press coverage reads exactly the way these announcements always read: capacity, jobs, delivery confidence, recovery narrative. What none of it mentions is the single most dangerous assumption inside that facility right now — that because the 737 is a mature product, the new line building it is also mature. It is not. It is a prototype wearing a production line's clothes.
I have lived this assumption from both sides. At SNOP, I built a greenfield QA/QC department for 900+ employees from a bare concrete floor. The product portfolio was transferred from sister plants. The standards were written. The control plans existed. The PFMEA was inherited, reviewed, signed off. None of it mattered for the first six months — because none of it had been validated against the reality of new tooling, new operators who had never seen a defect escape, and new process signatures that did not match the originating plant's data.
Today at Airbus, where I hold manufacturing engineering technical authority across North America, I see the same pattern whenever capacity expands. The product is proven. The line is not. And the quality system — the living, breathing operating discipline that catches deviations before they become escapes — has to be rebuilt and re-validated from first principles every single time.
The maturity trap
Here is the error that catches every organisation. Engineering looks at the drawing package, the existing control plan, the years of field data, and concludes the risk is low. Finance looks at the same evidence and budgets the new line as a transfer, not a development project. Operations staffs accordingly — lean team, tight ramp-up curve, production targets that assume week-eight stability.
The tooling disagrees.
New fixtures have tolerance stacks their predecessors didn't. New torque tools have different calibration drift. New autoclaves — or presses, or resistance spot welding guns, depending on your industry — carry thermal signatures that produce different mechanical properties in the same material spec. The product drawing hasn't changed. The physical part coming off the end of the line has.
At SNOP, we saw defect modes in the first quarter that the originating plant hadn't seen in five years. Not because our operators were worse. Not because our standards were weaker. Because the process was physically different, and the inherited PFMEA described someone else's process. We ran daily quality stand-ups for the first 90 days, revised over 40 control plan entries, and accepted that the first revision of any new line's documentation is a draft — not a finished article.
At Airbus, the principle scales but doesn't soften. When you stand up new manufacturing capacity for an aircraft programme, the maturity of the airframe is irrelevant to the maturity of the specific build sequence on that specific tooling set. You validate the line as if the product were new, because from the quality system's perspective, it is.
Operator qualification is the bottleneck nobody plans for
When I opened the SNOP plant, the single longest pole in the tent was not equipment installation. It was operator qualification. We had 900+ people, most hired within a compressed window, and the training matrix looked healthy on paper. A matrix is a document. Competence is an observable state.
You can transfer a work instruction in an afternoon. You cannot transfer tacit knowledge — the sound a press makes when tonnage drifts, the visual cue that tells an experienced operator the surface finish is trending, the feel of a fastener that isn't seating correctly. That knowledge lives in people, and new people don't have it, regardless of how many modules they've completed in the LMS.
The result is predictable. Deviation rate spikes. Containment activity surges. Your quality team spends its days not on continuous improvement but on triage — sorting signal from noise in a process that hasn't reached steady state.
Your deviation rate will spike — absorb it, don't fight it
The worst response to a new-line deviation spike is to treat it as a performance failure. It is not. It is the quality system doing exactly what it was designed to do — catching variation before it reaches the customer.
At SNOP, I told my team in the first month: we will find problems the originating plant never reported. We will find them because our system is new and sensitive, and because our tooling is generating different variation. Our job is not to explain away the deviations but to characterise them, feed them back into the PFMEA, and close them systematically with 8D and A3. We achieved a 70% reduction in defect costs and 98% customer satisfaction — but not in the first quarter. Those numbers took disciplined work over time, starting from the honest admission that month-one quality would be worse than the mature plant we'd inherited the product from.
A new assembly line does not inherit quality maturity. It earns it, one validated parameter at a time.
The pressure to declare victory early is enormous. Production wants to hit rate. Finance wants the ramp-up curve to bend. Customers want delivery certainty. And somewhere in that pressure, someone will suggest the quality team is being overly conservative — that the deviations are within tolerance if you interpret the spec charitably, that the escapes are minor, that the line is basically stable.
Resist that pressure with data, not argument. Run the A3. Complete the 8D. Update the PFMEA with what the new tooling is actually telling you. The cost of absorbing a deviation spike for 90 days is trivial compared to a field escape on a product that customers believe is mature and predictable.
Key takeaways
- Budget every new line as a prototype validation project, not a product transfer — staff quality engineering for discovery, not just oversight.
- Revise the inherited PFMEA against actual new-line process data within the first 30 days; the originating plant's failure modes are a starting point, not a complete picture.
- Plan operator qualification as the critical path, not a parallel workstream — build in time for tacit knowledge to develop, not just certification milestones to tick.
- Set leadership expectations that deviation rates will spike and containment is the correct response — do not let production pressure suppress the quality system's sensitivity during ramp-up.
A quality system is not a document library you copy to a new building. It is an operating discipline — the accumulated knowledge of how a specific process fails, validated against specific tooling, executed by specific people. When you move the product to a new line, you have moved the documents. You have not moved the discipline. That discipline has to be rebuilt, tested under load, and proven again from zero. Boeing's new line will either learn this the disciplined way or the expensive way. The 737 is mature. The line is not. And in aerospace, the quality system is the only thing standing between that distinction and a problem that reaches the customer at 35,000 feet.