GM: The Ignition Switch and Organizational Silence
Featuring Mary Barra
Engineers at General Motors documented a faulty ignition switch in the mid-2000s. It could cut engine power and disable airbags in a crash, and they proposed fixes. The knowledge sat inside the company for years. The fixes were rejected, the defect stayed in production cars, and over a decade later people died and millions of vehicles were recalled. No single villain explains it.
For operators, this is a quieter and more uncomfortable case than the headline recall. It is about why information stops traveling up, why agreement in a meeting does not become action, and what it actually costs when no one owns a decision. The diagnosis of whose failure this really was, and what you would have to change to prevent it, is the part the app makes you sit with.
Frequently asked questions
What is the GM ignition switch scandal about?
Engineers at General Motors documented a faulty ignition switch in the mid-2000s that could cut engine power and disable airbags in a crash. The proposed fixes were rejected, the defect stayed in production cars for years, and over a decade later people died and millions of vehicles were recalled.
Why did GM fail to fix the ignition switch defect for so long?
No single villain explains it. The knowledge sat inside the company for years because information stopped traveling up, agreement in meetings did not become action, and no one clearly owned the decision, so the defect stayed in production cars even after engineers proposed fixes.
Why is the GM ignition switch case important for understanding organizational silence?
Because it shows how a deadly problem can be known internally yet never acted on, not through one bad actor but through diffuse ownership and broken escalation. It is a quieter, more uncomfortable case than the headline recall, focused on why signals fail to climb the org and what that costs.
What can managers learn from the GM ignition switch failure?
The lesson is that information stops traveling up and decisions go unowned unless someone deliberately designs escalation and accountability into the organization. Identify where agreement in a meeting fails to become action on your team, and who actually owns the call. CaseBook turns this into a move you apply to your own company, with an AI coach that reads your answer.