Netlighter Martin Braaten Grina presentation at Edge Academy in Oslo 20160218. Getting feedback on the user experience of a product can be a tedious process. How design evaluation can be fun, easy and effective, and why building relationships with your users is important. © All rights reserved.

1. Martin Braaten Grina
Edge Academy 2016
Usability and Beyond
How to evaluate your product

2. What does usability mean?

3. Easy to use
Easy to learn
Efficient
Creates Identity
Prevents errors

4. One size doesn’t fit all

5. We’re never alone

6. We work in
cross-functional teams

7. Goals and needs
(requirements)
Hypothesises and solutions
(UX designers)
Prototyping / implementation
(UX / developers)
Test / feedback / data
(end-users)
Product Development Process
How we usually work

8. Lean Startup

9. Build
MeasureLearn

10. We minimise the
risk of failing

11. Design Critique

12. I am showing [early/mid/late] work
Because [why it’s a problem]
And am looking for feedback around
[specific focus for feedback]
Around [the problem]

13. “It’s immensely helpful to reiterate
the problem being solved before
showing any work in a critique.”
– Tanner Christensen
Product Designer @ Facebook

14. Why is user insight
important?

15. What
For who
How

16. Why!

17. “Don’t have time”
“Do we really need that?”
“Way too expensive”
“We have enough data”

18. “We know that…”
“It’s reasonable to assume that…”
“We expect that…”

19. User insight protects us
from ourselves
…so we don’t get lost in space

20. QUANTITATIVE
Interviews
Focus groups
Personas
Field studies
Expert evaluations
Card Sorting
BEHAVIORATTITUDE
QUALITATIVE
Usability testing
Eye Tracking
Accessibility evaluation
Perception analysis
Survey Web analysis
Heat Map
Scroll depth
Listening in

21. QUANTITATIVE
Interviews
Focus groups
Personas
Field studies
Expert evaluations
Card Sorting
BEHAVIORATTITUDE
QUALITATIVE
Usability testing
Eye Tracking
Accessibility evaluation
Perception analysis
Survey Web analysis
Heat Map
Scroll depth
Listening in

22. What can you
usability test?

24. Paper prototypes

25. Agile Usability Testing
Save time on user-involvement

26. Guerilla
Quick
and specific
Low budget Informal

27. Gonzo
Where the
users are
Realistic Quotes

28. 5 second tests
Focuses on
first impressions
Quantitative
approach
Frequent
iterations

29. Why agile usability testing?

30. To get answers within the sprint
Why agile usability testing?

31. Why agile usability testing?
w
ithin
the
sprint
To get answers the same day

32. Traditional usability testing
takes a week…
Why agile usability testing?

33. Ain’t nobody got
time for that!

34. Why test often?

35. The obvious reasons…

36. Quality assurance

37. Prevent errors

38. Increase the
user experience

39. The best UI is no UI
“Good design is invisible. Minimum
input, maximum output, with
minimal conscious thought.”
– Oliver Reichenstein

40. Less obvious reasons

41. Innovation

42. Try out new interactions

43. netlight
Who should experience
usability testing?

44. netlight
Everyone

45. netlight
Should be experienced by
the project team

46. netlight
Designers
Architects
Developers
Project Managers

47. netlight
Management
Marketing Department
Customer Support

48. netlight
Again, and again…

49. Fail fast, fail often

50. 7 reasons why
good usability pays off

51. Users find what
they’re looking for
High performance rates
among your users
Increased sales
Increased customer
satisfaction (and they’ll
recommend to others)
Increased self-service
Competitive advantage
You avoid losing customers
because your service is
difficult to grasp