• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Why every company should adopt the testing mantra
 

Why every company should adopt the testing mantra

on

  • 471 views

Why every company should adopt the usability testing mantra. Quick overview how and why to test your website, product or service.

Why every company should adopt the usability testing mantra. Quick overview how and why to test your website, product or service.

Trinidad Consulting 2013
http://www.trinidad.ee/

Statistics

Views

Total Views
471
Views on SlideShare
471
Embed Views
0

Actions

Likes
2
Downloads
2
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Adobe PDF

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

    Why every company should adopt the testing mantra Why every company should adopt the testing mantra Presentation Transcript

    • WHY EVERY COMPANY SHOULD ADOPT THE TESTING MANTRA Rene Rebane Senior UX Architect 2013
    • 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
    • 2013 User testing? Never heard of it!
    • 2013 What is usability testing?
    • 2013
    • 2013 Observing the user while they use the webpage, product or service through tasks you have given them.
    • 2013 Why to test?
    • 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
    • 2013 Why to test? • Find out usability problems • Why products, services and websites fail • Understand how users think • Risk reduction • No surprises
    • 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
    • 2013 Good time for testing
    • 2013 Beginning of the project End of the project Possibility of changes
    • 2013 Beginning of the project End of the project Cost of changes
    • 2013 What to test?
    • 2013
    • 2013
    • 2013
    • 2013
    • 2013
    • 2013
    • 2013 Testing process
    • 2013 Set goals and red routes Prepare tasks Prepare object, service or website Gather people Test session Analysis & report
    • 2013 Where to find people?
    • 2013 Where to find people? • Friends and acquaintances • Coffee shops • Shopping centres • Streets • Amongst clients
    • 2013 0 How many tests to conduct? 3 6 9 12 15 0% 50% 100% 75% 25%
    • 2013 One test with 8 users First test with 8 users Found 5 problems
    • 2013 Two test with 3 users First test with 3 users Second test with 3 users Found 9 problems
    • 2013 How to analyze?
    • 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
    • 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
    • 2013 Next steps • What to keep • What to change • What to test more • What to measure later
    • 2013 Let’s try it
    • 2013 Cherry.ee case
    • 2013 Q & A
    • Thank you Rene Rebane Senior UX Architect 2013 rene.rebane@trinidad.ee www.trinidad.ee