It's easy to create good looking products, but how about useful ones?
summary
Argues that measurable UX work must come before pretty UI and gives a concrete workflow: define scope, pick heuristics, run evaluations, log and prioritize findings. Recounts the 10 Usability Heuristics (Jakob Nielson and Don Norman), shows specific fixes — add undo, surface status, explicit error messages, readable typography and white space — and cites simple examples and apps (Coursera, Trello, Slack) as models for visibility of system status and error recovery.
AI-written summary · about
chapters (9)
- 0:00Start
- 12:421.Visibility of System Status
- 13:28Match Between The System And The Real World
- 14:06User Control And Freedom
- 15:47Error Prevention
- 17:29Flexibility And Efficiency of Use
- 18:50Aesthetic And Minimal Design
- 19:49Help Users Recognize, Diagnose, And Recover From Errors
- 20:38Help And Documentation
related talks
41mIt’s easy to create good looking products, but what about useful ones
28mIt’s Easy to Create a Good looking Product, but What About a Useful One?
28mIt’s easy to create a good looking product, but what about a useful one?
44mIt’s Easy To Create A Good-Looking Product, But How About A Useful One?
28mEleftheria Batsou-UX vs UI: It’s easy to create a good looking product, but what about a useful one?
33mBeyond Buttons: Crafting Satisfying & Easily Marketable Products
20mThe Power of UX Heuristics in Open Source Projects
41mUX Problems Hidden Behind a Pretty UI