The Chips and Pickle Story: What's Really Behind Infamous, Historic UI Failures?
summary
A cash register uses a single chips-and-pickle button so orders automatically include pickles and the mobile app truncates special requests to 25 characters, so “no pickles” often fails; Hawaii’s emergency system sends a false missile alert and takes 38 minutes to live to correct it because test and live messages share the same dropdown and there’s no preview; Three Mile Island’s PORV light shows command sent not valve position causing near meltdown; Florida 2000 punch‑card ballots create hanging chads and weeks of recounts.
AI-written summary · about
chapters (14)
- 0:00The Chips & Pickle Story: What's Really Behind Infamous, Historic UI Failures
- 2:39Jason's deli
- 10:3438 Minutes to Live
- 14:50Poor Computer Software design?
- 15:02Human Factors?
- 18:06Process Breakdown
- 19:19Meltdown (Almost)
- 25:25Function Foremost
- 25:57Process Failure
- 26:25Energy Legacy
- 37:14Slapdash Process
- 39:31Minor things have a major impact.
- 40:21Process is equally vital.
- 41:03A Broader Purpose
related talks
55mThe Chips & Pickle Story: What is Really Behind Infamous, Historic, UI Failures
51mThe Chips and Pickle Story: What's Really Behind Infamous, Historic UI Failures?
50mThe Crisps and Pickle Story: What's Really Behind Infamous, Historic UI Failures?
35mDiscovering User Interactions
13m404 Fire Alarm Not Found
01h 05m“Wouldn’t it be cool…” and other bad design approaches
16mThe parable of the blender
40mMost Expensive Design Mistakes (Ever) and how to avoid them