[Midwest UX 2017] Lean Usability Testing for Teams

[Midwest UX 2017] Lean Usability Testing for Teams

Usability testing is a critical step in creating a successful product. However, we may find ourselves hitting roadblocks when trying to do it. “UX doesn’t have enough time to create the design AND test the product,” and “we don’t want to test too early in the process,” are both excuses we’ve used or heard for not doing usability testing. The solution? Lean usability testing.

Lean usability testing introduces lean UX principles — testing early and often, reducing waste and collaboration, to name a few — to the traditional usability testing process. In this session, we’ll explore the value behind going lean and explain what a sample lean usability test looks like. You’ll leave knowing how to facilitate your own usability tests and why it’s important to include your team and stakeholders in the process.

30958b9299cfc3e606a1f2b559add92f?s=128

Rachel Krause

October 14, 2017
Tweet

Transcript

  1. None
  2. None
  3. We don’t have the time. We don’t have the resources.

    We can’t afford to change what’s done. We’re scared of what users will say.
  4. User Research Information Architecture Content Strategy Interaction Design Visual Design

    Prototyping Front-End Development Usability Testing
  5. You get to use a badass testing facility.

  6. None
  7. Users are plentiful and easy to find.

  8. None
  9. Everything goes smoothly and your participants know exactly what to

    expect.
  10. None
  11. All sessions are recorded and transcribed.

  12. None
  13. None
  14. None
  15. None
  16. Easy prep work Small sample size Entire team involved User’s

    current environment
  17. DIY guide to finding and fixing usability problems

  18. None
  19. None
  20. Choose a feature that needs validation. Doesn’t have to be

    complete to be tested. Focus on a specific workflow.
  21. None
  22. Match your personas as closely as possible. No matches? Others

    can be used for baseline usability. Sweet spot is 3-5 users.
  23. Elaborate usability tests are a waste of resources. The best

    results come from testing no more than 5 users and running as many small tests as you can afford. Jakob Nielsen
  24. None
  25. Clearly define each person’s role. Remind team why they should

    care. Set expectations of the day ahead of time.
  26. None
  27. Try to replicate conditions that user is familiar with. Provide

    an incentive for team and/or users. Plan for breaks in the process.
  28. None
  29. Brief participants before each session. Don’t ask for design opinions.

    Don’t ask leading questions. Know when to move on.
  30. None
  31. Each observer should debrief individually. Make note of any observed

    confusion or issues. Narrow down to top 3 usability issues.
  32. None
  33. None
  34. Compare notes as a team. Be open to the team’s

    observations. Issues are the fault of the design, not the user.
  35. None
  36. Identify quick wins. Weigh the needs of the user vs.

    the business. You don’t have to solution during this meeting.
  37. None
  38. Wrap up the session. Facilitate a retrospective. Plan the next

    usability test.
  39. None
  40. None
  41. SPRINT 4 BACKLOG Hook up login API Create login screen

    Data migration Support for import Create export API
  42. USER 1 USER 2 USER 3

  43. HALL MONITOR NOTE TAKER FACILITATOR OBSERVERS USER 1 USER 2

    USER 3
  44. None
  45. Show me how you would log in to an administrator

    account. Think aloud.  
  46. USER 1 OBSERVATIONS Tried to log in as regular user

    Wasn’t sure if he should log in with username or email address Was confused by the error message when login information was incorrect Made a comment about using active directory as universal login
  47. OVERALL USER OBSERVATIONS Tried to log in as regular user

    Wasn’t sure if he should log in with username or email address Was confused by the error message when login information was incorrect Made a comment about using active directory as universal login
  48. OVERALL USER OBSERVATIONS Tried to log in as regular user

    Wasn’t sure if he should log in with username or email address Was confused by the error message when login information was incorrect Didn’t check the ‘Remember Me’ box
  49. This went really well… We should try this next time…

  50. None
  51. None
  52. Start small. Facilitate frequent retrospectives. Keep focus on the team

    value.
  53. www.sensible.com > Downloads Usability Test Script Checklists Instructions for Observers

    Demo Test Videos
  54. None