Download as PDF, PPTX
![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]](https://image.slidesharecdn.com/20160218usabilityandbeyondenglishcompressed-160222085759/75/Usability-and-beyond-How-to-Evaluate-Your-Product-12-2048.jpg)
Uploaded byNetlight Consulting
Usability and beyond: How to Evaluate Your Product
The document discusses the principles of usability in product design, emphasizing the importance of user insight and cross-functional teamwork throughout the development process. It advocates for agile usability testing to improve efficiency and quality, allowing for rapid feedback and iterations. Additionally, it outlines the benefits of good usability, such as increased customer satisfaction and competitive advantage.
More Related Content
Similar to Usability and beyond: How to Evaluate Your Product
Usability and beyond: How to Evaluate Your Product
- 1. Martin Braaten Grina EdgeAcademy 2016 Usability and Beyond How to evaluate your product
- 2. What does usabilitymean?
- 3. Easy to use Easyto learn Efficient Creates Identity Prevents errors
- 4. One size doesn’tfit all
- 5.
- 6.
- 7. Goals and needs (requirements) Hypothesisesand solutions (UX designers) Prototyping / implementation (UX / developers) Test / feedback / data (end-users) Product Development Process How we usually work
- 8.
- 9.
- 10. We minimise the riskof failing
- 11.
- 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 helpfulto reiterate the problem being solved before showing any work in a critique.” – Tanner Christensen Product Designer @ Facebook
- 14. Why is userinsight important?
- 15.
- 16.
- 17. “Don’t have time” “Dowe really need that?” “Way too expensive” “We have enough data”
- 18. “We know that…” “It’sreasonable to assume that…” “We expect that…”
- 19. User insight protectsus from ourselves …so we don’t get lost in space
- 20. QUANTITATIVE Interviews Focus groups Personas Field studies Expertevaluations 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 Expertevaluations Card Sorting BEHAVIORATTITUDE QUALITATIVE Usability testing Eye Tracking Accessibility evaluation Perception analysis Survey Web analysis Heat Map Scroll depth Listening in
- 22.
- 24.
- 25. Agile Usability Testing Savetime on user-involvement
- 26.
- 27.
- 28. 5 second tests Focuseson first impressions Quantitative approach Frequent iterations
- 29. Why agile usabilitytesting?
- 30. To get answerswithin the sprint Why agile usability testing?
- 31. Why agile usabilitytesting? w ithin the sprint To get answers the same day
- 32. Traditional usability testing takesa week… Why agile usability testing?
- 33. Ain’t nobody got timefor that!
- 34.
- 35.
- 36.
- 37.
- 38.
- 39. The best UIis no UI “Good design is invisible. Minimum input, maximum output, with minimal conscious thought.” – Oliver Reichenstein
- 40.
- 41.
- 42. Try out newinteractions
- 43.
- 44.
- 45. netlight Should be experiencedby the project team
- 46.
- 47.
- 48.
- 49. Fail fast, failoften
- 50. 7 reasons why goodusability pays off
- 51. Users find what they’relooking 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