Are you only testing your design in production?
summary
Practical recipe for catching design failures before deploy using simple sessions on a laptop not a lab. Uses Cockpit server console with a moderator, audio/video and laptop and screen-share setup; schedules about 60 slots but the first real finding comes from the first three participants who all think the UI has crashed. Fixes: caching tweaks and replacing a spinner with a progress bar, after which afternoon testers no longer hit the problem. Rule of thumb: 5–10 users finds ~80–90% of issues.
AI-written summary · about
chapters (11)
- 0:00Testing design in production
- 1:16Hawaii missile alert failure
- 4:59Misconceptions about usability testing
- 7:28Usability testing without researchers
- 10:03Participants needed for testing
- 13:30Choosing test participants
- 15:18When to run usability tests
- 16:46Conducting a usability test
- 20:24Reusing participants and phases
- 21:30Testing at design stages
- 23:19Summary
related talks
12mDevelop better software with usability testing
01h 04mDiscount Usability Testing for Agile Teams
39mUsability Testing Without a UX Specialist
44mPanel: What are the Best Ways to use Tools to Bring Data into Design?
03m"A Story about Design and Experience"
33mInvolving Stakeholders in User Testing
01h 01mDesign thinking: why you should always include UX processes
09m"QA & UX"