• Save
Usability testing on a budget (by J Meadow)
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Usability testing on a budget (by J Meadow)

on

  • 992 views

This presentation explains how to run your own usability test sessions, within a limited budget and timeframe.

This presentation explains how to run your own usability test sessions, within a limited budget and timeframe.

Statistics

Views

Total Views
992
Views on SlideShare
716
Embed Views
276

Actions

Likes
1
Downloads
0
Comments
0

6 Embeds 276

http://www.silverstripe.com 224
http://silverstripe.com 45
http://www.silverstripe.co.nz 3
http://theoldreader.com 2
http://translate.googleusercontent.com 1
https://team.bbbart.cz 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • first slide
  • March 2011 was 30th anniversary of the ZX81 next year 30th anniversary of the ZX Spectrum
  • the following questions will be covered during this presentation
  • testing with real users... in this instance with real users of your website can use wireframes, page mockups, site being developed or current site
  • other ways to learn more about your users user focus groups & card sorting are done with real users > user research - learn about your users; their behaviour, attitudes and needs > user focus groups - meet with a group of users > personas - communicate findings from user research > card sorting - meet with users 1-on-1 to improve site structure > site statistics - understand who is using your site and how they use it
  • so, when’s best to start usability testing
  • 3 equal parts, could complete within 2 to 3 days Day 1: Plan tests, find & recruit testers Day 2: Test 6 users for about 1 hour each Day 3: Analyse findings and write up
  • tasks are more natural than direct questions or instructions - You're at a friend's house in Island Bay. When is the next bus back to town? - “ A drain on your street has burst and you need to report it urgently - find the telephone number ” better than Find the Contact Us section of the site
  • It takes only five users to uncover 80 percent of high-level usability problems source: Yakob Nielsen
  • don’t just ask anyone off the street, unless they match your target audience
  • Identify 5 user definable categories, some relating specifically to your site e.g. age, locality, life stage, income
  • add details of first possible candidate
  • add more details as you find more potential candidates now notice all in “outer suburb”, so need to find “central” and “close suburb” candidates
  • keep going, till have 8 participants balanced across all categories
  • doesn’t have to be exact, just the best you can get across all categories
  • and add another for good luck (in case someone drops out)
  • then complete contact details - usually email AND phone contact
  • and finally scheduled time and date of test sessions allow approx 40 minutes per session
  • Pre-check: - doesn't need to be perfect or finished - just make sure tasks are do-able and not dead-ends. Invite team members: - useful for them to see and learn from the session - limit to one per session, don’t overwhelm the test participant Setup the test room: - preferable to have 2 staff members present, facilitator (you) + note taker (colleague)
  • Welcome participants and make them feel at ease Get them familiar with the environment Outline what they will be doing and how long this will take: - introductions (5 minutes) - work through test tasks (20 minutes) - questions and answers (5 minutes)
  • If the participant is silent for a while, ask What are you thinking? If the participant says “hmmm” or “oops” ask What questions do you have right now? If the participant stops because they’re stuck or think they’re done: summarise what you saw them do ask what they would do next Don’t be afraid to move on if something is taking too long
  • User’s are only too happy to talk with you when the testing is over! sometimes is when you get the best feedback

Usability testing on a budget (by J Meadow) Presentation Transcript

  • 1. Usability testing on a budget
    • by Julian Meadow
  • 2.  
  • 3.  
  • 4. Questions
    • What is web usability testing?
    • When to conduct usability tests?
    • How many users to test with?
    • How to select your test users?
    • How to plan your tests sessions?
    • How many test sessions to run?
    • Who should attend?
    • How to conduct the test sessions?
  • 5. What is usability testing?
    • Web usability testing is a technique
    • for ensuring the users of your website
    • can carry out their intended tasks
    • efficiently, effectively and satisfactorily .
    • Web usability testing helps you understand
    • your audience’s needs and, in return,
    • produce more effective websites.
  • 6. Other techniques to understand your users understand your users
    • user research
    • user focus groups
    • personas
    • card sorting
    • site statistics
  • 7. When to test?
    • In a perfect world... the sooner the better
    • Start during initial development
    • Continue through the life of your site
    • Useful when making changes
    • Make iterative
  • 8. Usability testing
    • Prepare
    1 2 3 Conduct Review
  • 9.
    • Prepare
    1
    • Determine what needs testing
    • Develop user tasks to test
    • Recruit and schedule users
  • 10. How many test users?
    • one test session is better than none
    • 6 to 8 recommended to uncover the majority of issues
    • usually aim to recruit 9, in case someone backs-out
  • 11. How to select test users?
    • Important to get recruitment right
    • Represent your target audience
    • Ask colleagues, friends, family, acquaintances, etc
    • Complete usability testing matrix
  • 12. Usability testing matrix
  • 13. Usability testing matrix name sex 50% male, 50% female age 33% under 25, 33% 25 to 45, 33% over 45 locality 33% central, 33% close suburb, 33% outer suburb life stage 33% student, 33% worker, 33% retired technical ability 33% limited, 33% standard, 33% advanced Robyn M female 25 to 45 outer suburb student limited
  • 14. Usability testing matrix name sex 50% male, 50% female age 33% under 25, 33% 25 to 45, 33% over 45 locality 33% central, 33% close suburb, 33% outer suburb life stage 33% student, 33% worker, 33% retired technical ability 33% limited, 33% standard, 33% advanced Robyn M female 25 to 45 outer suburb student limited Julia H female under 25 outer suburb student standard Richard A male over 45 outer suburb worker standard
  • 15. Usability testing matrix name sex 50% male, 50% female age 33% under 25, 33% 25 to 45, 33% over 45 locality 33% central, 33% close suburb, 33% outer suburb life stage 33% student, 33% worker, 33% retired technical ability 33% limited, 33% standard, 33% advanced Robyn M female 25 to 45 outer suburb student limited Julia H female under 25 outer suburb student standard Richard A male over 45 outer suburb worker standard Ruth C female 25 to 45 central worker advanced Paul W male over 45 central retired standard
  • 16. Usability testing matrix name sex 50% male, 50% female age 33% under 25, 33% 25 to 45, 33% over 45 locality 33% central, 33% close suburb, 33% outer suburb life stage 33% student, 33% worker, 33% retired technical ability 33% limited, 33% standard, 33% advanced Robyn M female 25 to 45 outer suburb student limited Julia H female under 25 outer suburb student standard Richard A male over 45 outer suburb worker standard Ruth C female 25 to 45 central worker advanced Paul W male over 45 central retired standard Jen P female over 45 outer suburb worker advanced Brendan C male 25 to 45 close suburb worker standard Ryan M male 25 to 45 central worker limited
  • 17. Usability testing matrix name sex 50% male, 50% female age 33% under 25, 33% 25 to 45, 33% over 45 locality 33% central, 33% close suburb, 33% outer suburb life stage 33% student, 33% worker, 33% retired technical ability 33% limited, 33% standard, 33% advanced Robyn M female 25 to 45 outer suburb student limited Julia H female under 25 outer suburb student standard Richard A male over 45 outer suburb worker standard Ruth C female 25 to 45 central worker advanced Paul W male over 45 central retired standard Jen P female over 45 outer suburb worker advanced Brendan C male 25 to 45 close suburb worker standard Ryan M male 25 to 45 central worker limited Hilary J female 25 to 45 close suburb worker standard
  • 18. Usability testing matrix name contact details sex 50% male, 50% female age 33% under 25, 33% 25 to 45, 33% over 45 locality 33% central, 33% close suburb, 33% outer suburb life stage 33% student, 33% worker, 33% retired technical ability 33% limited, 33% standard, 33% advanced Robyn M [email_address] female 25 to 45 outer suburb student limited Julia H [email_address] female under 25 outer suburb student standard Richard A [email_address] male over 45 outer suburb worker standard Ruth C [email_address] female 25 to 45 central worker advanced Paul W [email_address] male over 45 central retired standard Jen P [email_address] female over 45 outer suburb worker advanced Brendan C [email_address] male 25 to 45 close suburb worker standard Ryan M [email_address] male 25 to 45 central worker limited Hilary J [email_address] female 25 to 45 close suburb worker standard
  • 19. Usability testing matrix name contact details when sex 50% male, 50% female age 33% under 25, 33% 25 to 45, 33% over 45 locality 33% central, 33% close suburb, 33% outer suburb life stage 33% student, 33% worker, 33% retired technical ability 33% limited, 33% standard, 33% advanced Robyn M [email_address] pm Tues 14th female 25 to 45 outer suburb student limited Julia H [email_address] pm Tues 14th female under 25 outer suburb student standard Richard A [email_address] pm Tues 14th male over 45 outer suburb worker standard Ruth C [email_address] 10:00 Wed 15th female 25 to 45 central worker advanced Paul W [email_address] 12:45 Wed 15th male over 45 central retired standard Jen P [email_address] 3:00 Wed 15th female over 45 outer suburb worker advanced Brendan C [email_address] 5:15 Wed 15th male 25 to 45 close suburb worker standard Ryan M [email_address] 6:00 Wed 15th male 25 to 45 central worker limited Hilary J [email_address] female 25 to 45 close suburb worker standard
  • 20.
    • Prepare
    1
    • Determine what needs testing
    • Develop user tasks to test
    • Recruit and schedule users
    • Final test preparation
    • pre-check all scenarios
    • invite team members
    • setup the room
  • 21.  
  • 22.  
  • 23.  
  • 24.  
  • 25.  
  • 26.  
  • 27.  
  • 28.  
  • 29.  
  • 30.
    • Welcome participants
    • Get them familiar
    • Outline what they’ll be doing
    Conduct
    • Introductions (5 mins)
    • Work through tasks (20 mins)
    • Questions and answers (5 mins)
    2
  • 31.
    • Remind participants you’re not testing them, you’re testing the site
    • Ask them to think out loud
    • Remember not to lead to the answers
    • Only give one task at a time
    2 Conduct - techniques
  • 32.
    • Allow a few minutes for informal discussion at the end
    • Ask what they liked and disliked
    • Ask if anything was confusing or frustrating
    • Ask if they have any suggestions for improvements
    2 Conduct - after testing
  • 33.
    • Review
    • Write-up your session notes
    • Sort into order, highlighting issues
    • Analyse and review with team
    • Add recommendations, with priorities
    1st priority - has to be fixed 2nd priority - good to fix 3rd priority - needs further review 3
  • 34.  
  • 35.  
  • 36. Questions?
  • 37. Thank you j@ silverstripe.com