The Worst Car Plant in America: What NUMMI Teaches Us About PRINCE2 7’s People Element

The NUMMI story shows why PRINCE2 7 moved People into the method itself. Same workers, different system, completely different results.

In 1982, General Motors closed its assembly plant in Fremont, California, and few tears were shed. By GM's own accounts it was among the worst plants in the company: absenteeism ran around 20%, so managers overstaffed every shift just to keep the line moving. Workers drank in the car park, settled scores on the shop floor, and, in the most famous act of sabotage, dropped loose bolts and the odd Coke bottle inside door panels, so the finished car would rattle forever and nobody would ever find out why.

Two years later, the same plant reopened with mostly the same workers, the same union, and the same badge on the gate. Within a couple of years it was building cars with quality levels matching Toyota's plants in Japan, and absenteeism had collapsed into low single digits.

Nobody swapped the people. Somebody swapped the system.

That plant was NUMMI, New United Motor Manufacturing, Inc., the GM-Toyota joint venture, and it is the best case study I know for why PRINCE2 7 promoted People to a full integrated element, and why PRINCE2 Agile 2 wraps its entire model inside mindset. It's also, in its sad final act, the sharpest lesson about lessons learned ever recorded.

In this blog, we'll explore:

• How Toyota re-motivated a workforce GM had written off, without changing the workforce
• What PRINCE2 7's People element formalises, and why culture sits inside it
• Where PRINCE2 Agile 2 takes the same idea further, from the Agile Onion to CALMS
• The uncomfortable ending: GM had the answer in-house for 25 years and never learned it

Man in a hole

Same workers, different system

The story shape here is the oldest one in the book: a character falls into a hole and climbs out changed. Except at Fremont, the workers hadn't dug the hole. The system had dug it for them, and then management blamed the men in it.

When NUMMI opened in December 1984, Toyota did something GM's executives found baffling: it rehired the great majority of the old workforce, the very people GM considered unmanageable. Then it flew group after group of them to Toyota City in Japan to work on Toyota's own lines and learn the Toyota Production System first-hand.

What they found there upended everything Fremont had taught them. Under kaizen, continuous improvement, the person doing the job is the person expected to improve the job. Ideas flowed up, not just orders down. Any worker could pull the andon cord and stop the entire line to fix a defect at source, an act that at old Fremont would have been a disciplinary matter. One returning worker famously described being moved to tears in Japan: for the first time in decades on an assembly line, someone had asked for his opinion and then acted on it.

The workers came home and built some of the best cars in America. The lesson is brutal in its simplicity: motivation wasn't a property of the workers. It was an output of the system they worked in. W. Edwards Deming had been saying it for years, a bad system will beat a good person every time, and Fremont proved both halves of the sentence in the same building.

People, promoted

Why PRINCE2 7 made it the fifth element

For six editions, PRINCE2 treated people the way old GM did: as a resourcing question, tucked inside organisational structures. PRINCE2 7 changed that. The method now has five integrated elements, principles, people, practices, processes, and project context, and People is a standalone element in its own right, worth a full 14% of the Foundation exam.

Look at what the element actually covers: culture, leadership, collaboration and co-creation, effective teams, communication, change management, and the wider organisational ecosystem the project sits in. That list is a NUMMI checklist. Toyota didn't succeed at Fremont with a better Gantt chart; it succeeded with a deliberately designed culture in which collaboration was structural, communication ran in both directions, and the change was managed as an experience the workers went through, Japan trips included, rather than a memo they received.

PRINCE2 7 even gives you the management products to do this properly: a change management approach and a communication management approach, both now formal parts of the method. If your project's answer to culture is "we sent an email", the 7th edition politely disagrees.

The onion wears its power on the outside

PRINCE2 Agile 2 goes further still

PRINCE2 Agile 2, built on the PRINCE2 7 base, pushes the same argument to its logical end. Its Agile Onion has five layers: processes at the visible centre, then practices, principles, values, and finally mindset as the outermost layer. The orientation is the message. The things you can see and buy, the tools, the daily stand-ups, sit small in the middle, while the layer with the real power is the largest, the least visible, and wraps around everything else. Any organisation can purchase the centre of the onion. The outer layer has to be grown, which is precisely what changed for the Fremont workforce and precisely what never changed for GM's wider management.

Version 2 also brings co-creation, growth mindset, and Organizational Change Management in as explicit named concepts, and its reworded DevOps definition is built on the CALMS acronym: Culture, Automation, Lean, Measurement, Sharing. Note the order. Culture is the C, and the C comes first. Toyota would nod. Old GM would ask which vendor sells Culture and whether it integrates with Excel.

The ending GM chose

Learn from experience, or don't

Here's where the story turns from inspiring to instructive. "Learn from experience" is one of PRINCE2's seven principles, unchanged across editions, and NUMMI is history's most expensive demonstration of what happens when an organisation ignores it.

GM had a fully working proof, inside its own company, staffed by its own former "problem" workers, from 1984 onwards. And for the better part of two decades it failed to spread the lesson across its other plants. Visiting managers took photographs of the factory floor and went home to copy the artefacts, the team boards and the cords, without the mindset wrapped around them, then wondered why nothing improved. The centre of the onion photographs beautifully. The outer layer doesn't show up on film. They captured lessons. They didn't learn any. Those are different activities, and only one of them changes behaviour.

GM entered bankruptcy in 2009. NUMMI itself closed in 2010. The Fremont site now builds Teslas, which is either poetry or cruelty depending on your mood.

Warning: you might be running old Fremont if…

• Improvement ideas require a form and a committee to be ignored properly.
• Stopping work to fix a defect is career-limiting, but shipping the defect is invisible.
• Your lessons log is immaculate, and has never once altered how the next stage was run.
• "Culture" appears in your project documentation exactly once, in a slide nobody presents.

Building your NUMMI

• Treat the People element as work, not garnish. Draft the change management approach and communication management approach early, and resource them like you mean it, PRINCE2 7 made them formal products for a reason.
• Put improvement authority where the work is. The person doing the task owns the first draft of how the task gets better. That is kaizen, and it costs nothing but managerial ego.
• Apply "learn from experience" as a verb. A lesson only counts as learned when a plan or a behaviour changes because of it. Audit your lessons log against that test and brace yourself.
• Start with mindset, not artefacts. Copying NUMMI's team boards without NUMMI's culture is cargo-cult project management, you've photographed the centre of the onion and missed the layer that holds it together.

Fremont's workers didn't change. Their system did, and everything else followed. If your project has "difficult people", PRINCE2 7 would like a quiet word about what else it might have.