$30 off During Our Annual Pro Sale. View Details »

[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.

Rachel Krause

October 14, 2017
Tweet

More Decks by Rachel Krause

Other Decks in Technology

Transcript

  1. View Slide

  2. View Slide

  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.

    View Slide

  4. User Research
    Information Architecture
    Content Strategy
    Interaction Design
    Visual Design
    Prototyping
    Front-End Development
    Usability Testing

    View Slide

  5. You get to use a badass testing facility.

    View Slide

  6. View Slide

  7. Users are plentiful and easy to find.

    View Slide

  8. View Slide

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

    View Slide

  10. View Slide

  11. All sessions are recorded and transcribed.

    View Slide

  12. View Slide

  13. View Slide

  14. View Slide

  15. View Slide

  16. Easy prep work
    Small sample size
    Entire team involved
    User’s current environment

    View Slide

  17. DIY guide to
    finding and
    fixing usability
    problems

    View Slide

  18. View Slide

  19. View Slide

  20. Choose a feature that needs validation.
    Doesn’t have to be complete to be tested.
    Focus on a specific workflow.

    View Slide

  21. View Slide

  22. Match your personas as closely as possible.
    No matches? Others can be used for baseline usability.
    Sweet spot is 3-5 users.

    View Slide

  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

    View Slide

  24. View Slide

  25. Clearly define each person’s role.
    Remind team why they should care.
    Set expectations of the day ahead of time.

    View Slide

  26. View Slide

  27. Try to replicate conditions that user is familiar with.
    Provide an incentive for team and/or users.
    Plan for breaks in the process.

    View Slide

  28. View Slide

  29. Brief participants before each session.
    Don’t ask for design opinions.
    Don’t ask leading questions.
    Know when to move on.

    View Slide

  30. View Slide

  31. Each observer should debrief individually.
    Make note of any observed confusion or issues.
    Narrow down to top 3 usability issues.

    View Slide

  32. View Slide

  33. View Slide

  34. Compare notes as a team.
    Be open to the team’s observations.
    Issues are the fault of the design, not the user.

    View Slide

  35. View Slide

  36. Identify quick wins.
    Weigh the needs of the user vs. the business.
    You don’t have to solution during this meeting.

    View Slide

  37. View Slide

  38. Wrap up the session.
    Facilitate a retrospective.
    Plan the next usability test.

    View Slide

  39. View Slide

  40. View Slide

  41. SPRINT 4 BACKLOG
    Hook up login API
    Create login screen
    Data migration
    Support for import
    Create export API

    View Slide

  42. USER 1
    USER 2
    USER 3

    View Slide

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

    View Slide

  44. View Slide

  45. Show me how you
    would log in to an
    administrator
    account. Think aloud.


    View Slide

  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

    View Slide

  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

    View Slide

  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

    View Slide

  49. This went really well…
    We should try this
    next time…

    View Slide

  50. View Slide

  51. View Slide

  52. Start small.
    Facilitate frequent retrospectives.
    Keep focus on the team value.

    View Slide

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

    View Slide

  54. View Slide