The hacker's guide to usability testing
summary
Claims a tiny, low-cost process finds the real problems: run 40 minute sessions, give printed scenarios, record with screen sharing and screencasts and sit with a clipboard to prompt think-aloud. Run 3–5 users per round, repeat a few rounds until issues saturate; one credit-card flow test surfaces a billing "leak." Results: four or five actionable fixes from a day of testing, big ROI versus guessing at design.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:37Usability Testing
- 14:19Setup
- 15:26What Is It Test
- 16:14The Please Do this Test
- 23:38Return on Investment
related talks
39mHacking usability
24mUsability Testing for Developers
48mUser testing on any budget
27mResearch Like You're Wrong
37mHow to Run 100 User Tests in Two Days
28mFind friction in your developer experience by user testing with developers
38mNo Traffic, No Users, No Problem! - Usability Testing for New Apps
34mAgile UX Research Practice in Android