Death by a thousand paper cuts
summary
Argues that UI bloat comes from early technical and design choices and shows concrete fixes: migrating legacy systems like CFEngine into interfaces, retrofitting inconsistent modules, and choosing manual Save button over hidden autosave when users feel uncertain. Recommends prioritizing user journeys, keeping a few happy paths, and spending about 80% research time on problem definition before building. Gives examples of what was changed and why, and which fixes actually reduced confusion.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:21MY CAREER IN COMPLEXITY
- 7:21COMPLEXITY IS RELATIVE
- 10:02COMPLEXITY MEANS
- 11:33WE LOVE CONSISTENCY
- 13:16MAINTAINING CONSISTENCY IS HARD WORK
- 21:11DECISIONS as CONSTRAINTS
- 25:37RUTHLESS PRIORITIZATION
- 28:26CONCLUSION
- 28:58Just like scope, complexity needs to be actively managed on all levels, from the inherent complexity of a feature to the complexity of the entire (brand) experience
related talks
25mJurassic UX: Design Best Practices for Legacy Software
32mLiving on Crotches or UI Automation Antipatterns
56mKicking the Complexity Habit
44mDeclare Bankruptcy on Technical Debt
39mYou should stop writing code
43mHow to Lose Your Feature Overload
23mFantastic UI and where it lives - creating and implementing UI without the pain
28mDesigning for Success: UX Principles for Internal Developer Platforms