Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

HCID 2017 - Smart usability testing

192 views

Published on

Talk by Swetha at System Concepts and Georgi at Kingston University

  • Be the first to comment

HCID 2017 - Smart usability testing

  1. 1. Smart usability testing Deliver real user insights on a budget HCID 2017 Swetha Sethu-Jones and Georgina Cox @systemconcepts and @KUEnterprise
  2. 2. About us Swetha Sethu-Jones Georgina Cox Senior UX Consultant, at System Concepts 7+ years experience Co-organise the Research Thing meetup @swethas Business Engagement and Marketing Manager, at Kingston University B2B marketing for the University @kuenterprise
  3. 3. About System Concepts
  4. 4. What we’ll cover in this talk Formal usability testing approach 05 Our ‘smart usability testing’ approach 07 Case study: Kingston University 12 Implementation 18 Takeaways 19
  5. 5. Formal usability testing approach Kick-off Meeting Recruitment Testing with ~10 users Analysis and Reporting Debrief 2 weeks lead time 2 – 3 Days About a week
  6. 6. The challenges: Usability testing • Takes several weeks • Limited stakeholder involvement • Difficult to fit into a rapid iterative development cycle • Can be expensive
  7. 7. Our ‘Smart usability testing’ approach What is it? • Rapid usability testing in one day • Live and collaborative note-taking process • Analysis and debrief workshop on the same day • Cost effective due to small sample and collaborative analysis Challenges addressed • Takes several weeks • Limited stakeholder involvement • Difficult to fit into a rapid iterative development cycle • Can be expensive
  8. 8. Rapid usability testing in one day • Run 4 to 5 sessions in one day • Each session to last 45 to 60 minutes • Agree on clear research objectives - focussed on up to roughly 3 core user journeys
  9. 9. Live and collaborative note-taking • Clear instructions and good facilitation with observers • Large printouts of screenshots • Colour coded post-it notes • One finding per post-it note. Notes should include the ‘what’ and ‘why’ • Tidy and annotate post-it notes as you go
  10. 10. Analysis and debrief workshop • Go through post-it notes and discuss findings as a team • Discuss and prioritise findings • Discuss potential solutions • Optional next step: Report illustrating key findings and solutions
  11. 11. Smart usability testing approach Kick-off Meeting Recruitment Testing with ~5 users + Workshop Reporting (optional) ~1.5 weeks lead time 1 Day
  12. 12. Case study: Kingston University How we collaborated with Kingston University to plan, conduct and deliver rapid usability testing on a budget.
  13. 13. Case study: Background Services for business Short courses
  14. 14. Case study: Project objectives • Inform a rewrite / reorganisation of our content and navigation • Gain better insight into what our target audience(s) were looking for in terms of ‘services for business’ • Gather valid evidence for business case to ‘sell’ internally • Short timeframe
  15. 15. Case study: Approach
  16. 16. Case study: Outcome
  17. 17. Case study: Outcome Clearer links to other sites Language / Terminology Contact email more visible Bringing in other areas of the University Key information made more visible and upfront Still in Progress!
  18. 18. Challenges with implementation Internal barriers • Change of priorities • Change of staff (web and management) • Development work required was not going to be possible Next steps • Now internal ambassadors for UX! • Would definitely use again - users always at forefront of our minds
  19. 19. Takeaways of this approach • Just one day of usability sessions per iterative round • Involve stakeholders to get the most value and make decisions based on it • Provide a quick turnaround of insights, rather than waiting for a massive report. • Teams can spend one day focusing on an aspect of your product. • Discussions are helpful for the researcher to understand internal priorities and contribute.
  20. 20. Swetha Sethu-Jones (swetha@system-concepts.com) Georgina Cox (G.Cox@kingston.ac.uk)

×