The top IT failures in history
summary
Lists begin with a Mars probe lost to a meters vs feet mismatch between European and American subsystems, escalate to the Boeing 737 MAX where MCAS software overrode pilots and two crashes kill 346 people and cost tens of billions, and include a rushed SAP rollout that destroys product and trust. Research-backed remedies center on a learning culture with high psychological safety and high accountability, plus processes like anonymous incident reporting and a Triple-A error management loop: assess signals, acknowledge errors, act quickly.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:23Satellite launch
- 2:35Ethiopian Airlines crash
- 2:58What was the problem
- 5:40What can we learn
- 9:22Strategic errors
- 13:56Managing errors
- 15:44Learning culture
- 19:45Embed culture in organizational processes
- 21:31Proactively manage strategic errors
related talks
53mMayday Mark 2! More Software Lessons From Aviation Disasters.
22mBugs That Made Headlines – and What They Reveal About How We Build Software
56mLearning from Disaster
46mPlanning for and handling failures from open hardware, aviation, to production at Google
30mPilot your Project: Avoiding Anti-Patterns While Handling Incidents and Planning
34mTaking the 737 to the Max
29mThe Most Bizarre Software Bugs in History
26mThe software bug all stars - and what we can learn from them