Why Every Company Should Adopt the Testing Mantra

248 views

Published on

What is testing all about? Is it just QA or something much-much more? When to test? How to test? Who are the people you should run your tests on? These are just some of the questions answered in the presentation.

This presentation was originally made in August 2013 and presented at the Tallinn Technopolis Ülemiste Business Breakfast event.

Published in: Design, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
248
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
2
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Why Every Company Should Adopt the Testing Mantra

  1. 1. WHY EVERY COMPANY SHOULD ADOPT THE TESTING MANTRA Rene Rebane Senior UX Architect 2013
  2. 2. 2013 Today’s topics • What is usability testing? • Why to test? • Good time for testing • What to test? • Testing process and hands on • Cherry.ee example
  3. 3. 2013 User testing? Never heard of it!
  4. 4. 2013 What is usability testing?
  5. 5. 2013
  6. 6. 2013 Observing the user while they use the webpage, product or service through tasks you have given them.
  7. 7. 2013 Why to test?
  8. 8. 2013 “If you want a great site, you’ve got to test. After you’ve worked on a site for even a few weeks, you can’t see it freshly anymore. You know too much. The only way to find out if it really works is to test it.” – Steve Krug, Don’t Make Me Think
  9. 9. 2013 Why to test? • Find out usability problems • Why products, services and websites fail • Understand how users think • Risk reduction • No surprises
  10. 10. 2013 Does not help to answer • Do people like it • Will people buy it • How people will use it mostly • What kind of people will use it • What solution is better A or B
  11. 11. 2013 Good time for testing
  12. 12. 2013 Beginning of the project End of the project Possibility of changes
  13. 13. 2013 Beginning of the project End of the project Cost of changes
  14. 14. 2013 What to test?
  15. 15. 2013
  16. 16. 2013
  17. 17. 2013
  18. 18. 2013
  19. 19. 2013
  20. 20. 2013
  21. 21. 2013 Testing process
  22. 22. 2013 Set goals and red routes Prepare tasks Prepare object, service or website Gather people Test session Analysis & report
  23. 23. 2013 Where to find people?
  24. 24. 2013 Where to find people? • Friends and acquaintances • Coffee shops • Shopping centres • Streets • Amongst clients
  25. 25. 2013 0 How many tests to conduct? 3 6 9 12 15 0% 50% 100% 75% 25%
  26. 26. 2013 One test with 8 users First test with 8 users Found 5 problems
  27. 27. 2013 Two test with 3 users First test with 3 users Second test with 3 users Found 9 problems
  28. 28. 2013 How to analyze?
  29. 29. 2013 How to analyze? • Write down what happened • Why it is unexpected • Why it is bad (longer process, wrong element usage) • Remember it is not statistics
  30. 30. 2013 Does problem occur on a red route? Is the problem difficult to overcome? Is the problem persistent? low Is the problem difficult to overcome? Is the problem persistent? Is the problem persistent? Medium Serious Critical
  31. 31. 2013 Next steps • What to keep • What to change • What to test more • What to measure later
  32. 32. 2013 Let’s try it
  33. 33. 2013 Cherry.ee case
  34. 34. 2013 Q & A
  35. 35. Thank you Rene Rebane Senior UX Architect 2013 rene.rebane@trinidad.ee www.trinidad.ee

×