Skip to content
jefferydutra edited this page Nov 15, 2014 · 4 revisions

Usability Testing in (Design)

The best way to uncover errors in the user interface is to observe actual users trying to use the system while you observe. A simple setup will enable you to do this more often. All you really need is a room, some tasks, something to test and a few potential users.>

Why


  • Our assumptions are often wrong
  • Observations are better than opinions
  • Use insight to remove errors in user interface functionality
  • Assumptions are based on our view of the usage

What


Use people from your target group Get the user to think out loud Ask questions: What is that button for Was what happened what you expected Use stakeholders as observers (less room for debate after the fact)

How


  • Recruit Users 4-6
    • 50% from low domain knowledge, low computer skills
    • 25% from low domain knowledge, high computer skills
    • 25% from high domain knowledge, low computer skills
  • Create realistic tasks
    • Based on user stories, use cases, or functional descriptions
    • Do not use the words from the UI in the task description (Don't plant thoughts in their head) *Observe
    • Stay quiet
    • Note what happens, not solutions
    • Describe what users do, not what they say *Analyze
    • Try to separate observation, interpretation, and solution
    • Prioritize the findings
    • Involve Stakeholders

Clone this wiki locally