why you should always test with users

49
#UXPond Why you should always test with users and why gorillas are better than nothing ‘guerrilla’ is @quiffboy @DigitalPondUK #UXPond Thursday, 26 Sept 2013

Upload: barry-briggs

Post on 27-Jan-2015

112 views

Category:

Design


3 download

DESCRIPTION

...and why ‘guerrilla’ is better than nothing

TRANSCRIPT

Page 1: Why you should always test with users

#UXPond

Why you should always test with usersand why gorillas are better than nothing

‘guerrilla’ is

@quiffboy @DigitalPondUK #UXPond

Thursday, 26 Sept 2013

Page 2: Why you should always test with users

#UXPond

Leisa is Head of User Research @ GDS, GOV.UK

Page 3: Why you should always test with users

#UXPond

“Testing with customers” Me

Customers have a monetary value

Page 4: Why you should always test with users

#UXPond

Page 5: Why you should always test with users

#UXPond

Page 6: Why you should always test with users

#UXPond

• In 2013, Amaze ranked at number 22 in UK’s top 100 agencies

• Ranked #1 in the North West

• Ranked #4 in Design & Build

Don’t just take my word for it…

Page 7: Why you should always test with users

#UXPondASICS – International websites / Global E-commerce

Page 8: Why you should always test with users

#UXPondLexus V10 – Building award-winning pan-European luxury

Page 9: Why you should always test with users

#UXPond

The Saucy Fish Co – Increasing brand worth to £60m in 2 years using digital, social and PR as springboards

Page 10: Why you should always test with users

#UXPond

Unilever - Strategic co-ordination and implementation support across Unilever’s global digital operation

Page 11: Why you should always test with users

#UXPond

Toyota - Strategic brand, creative, technological and feature-rich functional development for multi-lingual websites across 28 European markets

Page 12: Why you should always test with users

#UXPond

Common types of usability testing

• Moderated lab testing• Remote testing• Eye tracking (in a moderated lab)

Page 13: Why you should always test with users

#UXPond

Moderated lab testing

“Observe people using the product to discover…how well test subjects respond in four areas: efficiency, accuracy, recall, and emotional response.” Wikipedia

cabinetoffice.gov.uk

Page 14: Why you should always test with users

#UXPond

Page 15: Why you should always test with users

#UXPond

Remote usability testing

Page 16: Why you should always test with users

#UXPond

Eye tracking

“Eye tracking is the process of measuring either the point of gaze (where one is looking) or the motion of an eye relative to the head.” Wikipedia

grokdotcom.com

Page 17: Why you should always test with users

#UXPond

Eye tracking: complex & intrusive hardware, right?

fffff.at

acuity-ets.com

Not so scary anymore

Page 18: Why you should always test with users

#UXPond

Eye tracking: findings are still scary though

• Generates lots of complex graphs and diagrams • Needs experts to interpret results• Time consuming & expensive

Heatmap fromkunocreative.com

Gaze plot from uxmatters.com

Page 19: Why you should always test with users

#UXPond

But it’s a no brainer, right?

You should test your stuff with real people

Page 21: Why you should always test with users

#UXPond

Why test?

Page 22: Why you should always test with users

#UXPond

Why test?

Improve decision making

Remove guesswork

Remove experience

bias

Page 23: Why you should always test with users

#UXPond

So why don’t we always test?

Page 24: Why you should always test with users

#UXPond

So why don’t we always test?

Too expensive

Time or resource

consuming

Not a primary concern

Page 25: Why you should always test with users

#UXPond

£15 for 15 minutes

• Based on moderated lab testing• Uses think-aloud protocols• Test in guerrilla environments• Recruit “in the wild”• Prototype “good enough”• Focus on key tasks• Report on problem areas• Client expectations are focussed

Page 26: Why you should always test with users

#UXPond

http://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/

5 = 85%

Page 27: Why you should always test with users

#UXPond

Case StudyASICS America

Page 28: Why you should always test with users

#UXPondCase study: ASICS America

Page 29: Why you should always test with users

#UXPond

+

+

Axure RP Pro Silverback

(optional)

Page 30: Why you should always test with users

#UXPond

Page 31: Why you should always test with users

#UXPond

What we did

Prep• Recruit from same office building – posters in lobby• Identified 2-3 key user journeys & features• Prototype new features for journeys – medium fidelity

Test• Test in spare meeting room in Amaze office• Slots 12-2pm and 4-6pm

Report• Brief, focussed report - bullet point list• Export & upload videos & prototype• Talk client through findings

Page 32: Why you should always test with users

#UXPond

What we did

Prep • 3 days

Test • 1 day

Report • 1 day

Page 33: Why you should always test with users

#UXPond

What we did

Prep • 3 days

Test • 1 day

Report • 1 day

1 week start to finish

Easily digestible

report

Actionable findings

Page 34: Why you should always test with users

#UXPond

10 Considerationsand/or gotchas

Page 35: Why you should always test with users

#UXPond

1) Avoid recruiting experts

Page 36: Why you should always test with users

#UXPond

2) Test small, test early, test often

Page 37: Why you should always test with users

#UXPond

3) If you can, test in real environments

Page 38: Why you should always test with users

#UXPond

4) Focus on what needs fixing (or refining)

Page 39: Why you should always test with users

#UXPond

5) Give tasks, not instructions

Page 40: Why you should always test with users

#UXPond

6) Rotate order of tasks

Page 41: Why you should always test with users

#UXPond

7) Fidelity matters, but it’s not critical

Page 42: Why you should always test with users

#UXPond

8) 5 people’s opinions are not conclusive proof

Page 43: Why you should always test with users

#UXPond

9) People say the darndest things

Page 44: Why you should always test with users

#UXPond

10) “Testing with 1 person is 100% better than testing with none”

Steve Krug“Don’t Make Me Think”

Page 45: Why you should always test with users

#UXPond

Useful links

• Why You Only Need to Test with 5 Usershttp://www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/

• The Art of Guerrilla Usability Testinghttp://www.uxbooth.com/articles/the-art-of-guerilla-usability-testing/

• Remote Usability and UX Research Toolshttp://remoteresear.ch/tools/

• New to Usability Testing? You’re not alone!http://userexperiencerocks.wordpress.com/2013/07/16/getting-started-with-usability-testing/

• User Experience Survey 2013http://econsultancy.com/uk/reports/user-experience-survey-report

http://northern-user-experience.org/2013/09/05/ux-challenge-choose-right-approach-guest-blog-ian-franklin-freelance-ux-consultant

• Steve Krug: “Don’t make me think” & “Rocket Surgery Made Easy” and more…http://www.sensible.com

Page 46: Why you should always test with users

#UXPond

One more thing…

Page 47: Why you should always test with users

#UXPond

Page 48: Why you should always test with users

#UXPond

NUX2uxmanc.co.uk

Friday 25th October£25 day ticket

Page 49: Why you should always test with users

#UXPond

Thank you

e: [email protected]

t: @quiffboy

w: www.amaze.com