DIY Usability Testing When You Have No Time and No Budget | Bekah Rice | ng-conf 2024

Start testing as early as possible in the design phase, ideally at wireframing stage to prevent issues later

5 users is typically enough to identify key patterns and issues - testing with more users tends to reveal the same findings

Create realistic scenarios and tasks that match how users would actually use the product in real life - avoid leading questions or telling users exactly what to do

Don’t test with power users, developers, or stakeholders - recruit actual target users who aren’t familiar with the product

Test sessions should be around 45 minutes with 10 or fewer prioritized tasks - give users context but don’t overload them

Stay neutral during testing - don’t show emotion, answer questions, or lead users. Let them struggle and figure things out naturally

Have users think aloud and narrate their actions/thoughts. Ask “What are you thinking right now?” when they go silent

Record sessions if possible - seeing user behavior and facial expressions provides valuable insights beyond just voice/notes

Look for patterns and themes across tests rather than just pass/fail metrics. Note where multiple users struggle

Create clear reports documenting findings, but discuss results with stakeholders rather than just handing off documents

Testing with accessibility tools and users with disabilities requires special considerations and more setup, but is valuable

DIY testing is possible with minimal budget - you just need users, basic equipment, and a quiet space