Hacking usability
summary
Usability testing is cheap to start, fits into every development stage, and catches big failures early — an IoT juicer wasted $120,000 by skipping it. Follow a hypothesis→goals→script→think‑aloud→compile workflow, test with 5–10 tasks, recruit real users not “professional” testers, and prioritize fixes on post‑its. Use tools like Hotjar, UserTesting, TryMyUI, 5‑second tests or Usabilla, configure remote/session settings and languages, and spend ~10% of design budget to get measurable, actionable changes.
AI-written summary · about
chapters (26)
- 0:00Intro
- 0:29Who am I
- 0:47Usability
- 1:14User Needs
- 2:24Tin Cans
- 3:58Explanation
- 5:23Why test usability
- 5:56Core components of usability
- 7:05Technicality works
- 8:25Usability testing
- 11:11DIY testing
- 12:02Budget on usability
- 13:34Different types of testing
- 14:53Framework
- 15:54Budget
- 18:18Hypothesis
- 19:05Goals
- 20:12User script
- 22:15Tasks
- 24:13Emotion
- 27:45Feedback
- 28:48Compile
- 30:07Remote testing
- 33:31Things to consider
- 36:23Tools
- 38:50Outro
related talks
25mThe hacker's guide to usability testing
24mUsability Testing for Developers
39mUsability Testing Without a UX Specialist
28mDIY Usability Testing When You Have No Time and No Budget
24mDIY Usability Testing With No Money and No Time
29mEasy and Affordable User-Testing
46mPractical UX When You Have (almost) No Time or Money
12mDevelop better software with usability testing