“Wouldn’t it be cool…” and other bad design approaches
summary
Shows concrete failures and fixes: F‑35 touchscreens suffer ~20% failure after replacing tactile switches; Story Remix demo adds pointless explosions; a browser order-entry rewrite loses commission-driven users and is rolled back; a redesigned radiology UI drives roughly $400M in early revenue by embedding images in reports. Recommends vetting with multiple competing designs, ditching wouldn't it be cool choices, avoiding design theater and MVP-by-throwaway — prefer prototyping, usability tests and calculating ROI before committing.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:26Design failures in dev teams
- 4:14F-35 design failure
- 7:23‘Wouldn’t it be cool’ danger
- 11:41Microsoft Story Remix waste
- 16:36Animation UX disasters
- 18:01Windows 8 failure
- 25:33Copying designs blindly
- 26:373M radiology app success
- 30:49Hawaii nuclear alert flaw
- 33:37Data grids and designing for developers instead of users
- 36:48Browser vs native apps
- 37:50Vetting designs & bias
- 43:05Avoiding design theater
- 45:11Users can’t design screens
- 50:30Myth of rapid MVP iteration
- 51:32Windows 8 flawed assumptions
- 54:01Design effort ROI
- 58:16Summary of bad design
- 1:00:01Effective design practices
- 1:04:15Q&A
related talks
01h 01m“Wouldn’t it be cool…” and other bad design approaches
40mMost Expensive Design Mistakes (Ever) and how to avoid them
14mDesigning UIs without a UI designer
32mDesigning with Empathy
03m"A Story about Design and Experience"
38mEnough Design
35mDiscovering User Interactions
56mThe Shady Secrets From The Dark Corners of Web Interfaces