Your best plant sets no standard. Your worst one sets your reputation.

Jim Farley told the world that Ford's best factories aren't in America. Read that sentence again. A chief executive publicly ranked his own plants by geography — and nobody found that strange. I've walked into plants on Monday mornings where the weekend shift left first-off scrap on a pallet marked "hold" with no tag, no owner, no timestamp. I've also walked into plants where the andon board updates faster than the morning news and the floor supervisor can quote you last week's FPY by line, by shift, by part number. Both plants belonged to the same company. Same logo above the gate. Same quality manual in the rack. Different planets.

That gap — the distance between your best plant and your worst — is the only quality metric that matters at the executive level. Not your average PPM. Not your aggregated customer score. The spread.

A best plant means your quality system has a standard deviation problem

If you can rank your factories, your system has failed. Full stop. A CEO should not be able to tell his plants apart by output quality. He should look at KPI dashboards from three sites on three continents and see the same number plus or minus noise. When he can point at a map and say "our best are here," what he's saying is: we have no system. We have a collection of local outcomes, and some of them got lucky with leadership, culture, or supplier base.

I lived this. When I took on the North American manufacturing engineering role at Airbus, the task wasn't to import a playbook and staple it to a wall in Mobile. It was to find the irreducible core of the process — the non-negotiable control points, the response logic when something drifts — and make it location-agnostic. PFMEA doesn't have a passport. 8D doesn't perform better in one time zone.

What changes is discipline. Execution. Whether the morning huddle reviews the top three deviations or just drinks coffee and waits for the shift to start.

At SNOP, I built a QA/QC department for 900 people from bare concrete and a fencing perimeter. Greenfield. No legacy culture, no entrenched habits — and no existing competence either. The advantage of starting from nothing is that you can't accidentally inherit someone else's standard deviation. The disadvantage is that every protocol, escalation path, and reaction plan has to be designed, written, trained, audited, and reinforced until it becomes muscle memory. We got there. 70% defect-cost reduction, 98% customer satisfaction, clean audits. But the point isn't the headline number. The point is that it happened because the system was uniform by design, not heroic by accident.

Your worst plant ships your next recall

Here is the problem with averages: customers don't experience them. A person who buys a vehicle built on a Tuesday afternoon at your worst plant doesn't care that your flagship facility across the ocean runs at 12 PPM. They got the Friday car. Their steering column has a tolerance stack-up that your best plant would have caught at sub-assembly, but your worst plant's operator was covering for someone who called in sick, and the poka-yoke was bypassed last month because it kept stopping the line.

Your best plant proves what's possible. Your worst plant proves what's real.

I've sat in QRQC rooms where the question wasn't "what went wrong" but "which site let this through." That's the wrong question. The right one: why did our system allow one site to let it through while another wouldn't have? The answer is always the same — variance in discipline, variance in escalation, variance in what "stop the line" means when a supervisor is three hours behind takt.

External auditors know this. When EASA walks into a facility, they don't average your sites. They judge the one standing in front of them. We cut audit findings by 50% in a single cycle — not because we had a hero plant, but because we systematised the response to every structural weakness we'd found across the network and applied it everywhere. The boring, repetitive, unglamorous work of making every plant behave identically under stress.

Multi-site excellence isn't having a flagship — it's making variance boring

The most dangerous plant in your network isn't the worst one. It's the best one. Because the best one gives you cover. It lets you stand in front of analysts and point at a dashboard and say "we have sites performing at world-class levels." Three time zones away, a different plant is shipping parts that will cost you a customer, a contract, or a recall campaign that erases a quarter's margin.

I've led quality initiatives across a 2,000+ workforce, multi-site. The work that matters isn't celebrating the top performer in a quarterly review. It's pulling the bottom up so aggressively that the gap disappears. Standard work. Daily verification. Escalation triggers that fire automatically regardless of who's on shift. Routing Verification KPIs that don't care about geography — I used these to compress internal lead time by 97%. Not at one site. Across the scope I controlled.

If your best plant sets no standard that your worst plant can follow, it's not a standard. It's a tourist attraction.

The companies that sleep well at night aren't the ones with a plant they can brag about to the press. They're the ones where the quality director gets a call at 2 AM and genuinely cannot guess which site it's about. That flat, unremarkable uniformity across geography and shift and culture — that is the only standard worth building.