Ian Franklin from IdeaSmiths discussing fitting Usability Labs into Agile sprints.
Traditionally, usability labs took a long time to organise; often just a usability bug hunt and resulted in a lengthy report of recommendations that no one read and took weeks to produce.
This talk covers how to adapt the usability lab to include discovery and co-creation, yet still record results rigorously while completing analysis and reporting within a couple of days.
It also covers how to counter the common objections to user feedback (“its only 5 users”, “it’s just anecdotes”) and how to use the lab to get stakeholders on side.
2. What We Will Do
•Labs within Agile
•Why we do a usability lab
•Issues of Usability Testing
•Plan a session
•Do a session
•Analyse and report
•Questions
8. We need answers
•Can the user use it?
•From Discovery are the user needs valid?
•In Lean UX – discovery in alpha
•Is the MVP right?
•Is the new stuff (from backlog) working?
•Did we break it?
•Is the site successful?
9.
10. Create ownership
Agile team:
•Designers – design iterations
•Product Owner – improving decisions
•Delivery Manager – prioritisation
•Techies – why the solution is the solution
12. Other benefits
•Labs look good – Face Validity
•very ‘sciency’ and ‘shiny’
•Fun for the team
•Known technique – 50/60 years old
•Rigorous methodology
•Good Politics
•Can fit into two week sprint
17. Its only 5 Users Its just
what
someone
said, its
anecdotal
Its not a scientific
statistically
representative
sample
Its all subjective, we need
more hard evidence
18. Everyone knows your job better than
you…
…Because every other *&%^£)(*&^
person in your organisation
is a Scientific Einstein…
…Except YOU
40. What do we need
•Getting users
•Profile and requirements
•Market research recruiter
•Location
•Hire a lab/Hire a room
•Go to users
•Users come to you
•Props and fake data
41. What can we do?
•Usability bug hunt – usability
•Test the Concept – wireframe paper and
screenshots
•Card sort/Tree tests
•Co-creation - “show me an example”
•Discovery interviews/Contextual inquiry
•Supporting materials and processes
42. Session Plan
•Scenario versus Tasks
•How many tasks?
• 2 to 3 – must do
• 1 to 2 – nice if we can
•Don’t forget breaks
43. A simple session plan
•Background and informed consent
•About the user and device/internet usage
•Build rapport
•The tasksscenario
•Final questions
•Best thing today
•Worst thing today
•One thing we need to change
44. Typical Hour
•10 to 15 minutes background
•20 minutes: discovery and context
•20 minutes: user does tasks, uses the tech
•10 minutes debrief and final questions
45. Who owns the plan
•The Team!
•Develop with UX and content designers
•Agree with Product Owner and Delivery Manager
•Clear link to the sprint and backlog
•Clear hypotheses and aim
46. Kit
•Devices – take
your own
•Screen wipes
•Yellow stickies
– shed loads
•Sharpies - black
•Props and fake
data
•Session plan
•Roll of brown
paper
•Glue Prit sticks
– spot weld
stickies
•Blu Tack
•Scissors
49. Roles
•Facilitators – work with the user
•Observers – take notes
•Designers
•The team
•Visitors – take notes (e.g. stakeholders)
•Sticky collector(s)
•Transcribers???????
50. Observation Room – ground rules
•Snacks and refreshments
•No side meetings
•Devices off
•No phone calls
•No design decision conversations
•Split observations and quotes
52. Brown Paper Method
•A long roll for each user
•Put stickies on in timeline
•Which follows the session plan
•Roll up at end of each user
•New blank roll on wall
53. Anatomy of a Sticky: Quote
“ Yeah, no problem really
[as adult] … but my kids,
no, not sharing that”
U 01
User number.
Squarebrackets to give context.
Ellipsis… for missing words, pauses
One idea.
Cansplit over two.
Stickies must stand on their
own
If a quote use quote
marks.
NOT insights, not yet
54. Anatomy of a Sticky: Observation
User had problems
entering one time
password. Error at input
U 01
If observationno quotes,
start with User
NOT insights, not yet
User number.
One idea.
Cansplit over two.
Stickies must stand on their
own
55. If nothing else
•Put the participant code somewhere on the
sticky.
•Put quotes in “...”
•Start observations with User
•Write observations clearly
•Tear stickies from the side
•Ban biros
58. Affinity mapping
•Put stickies on wall or brown paper
•Read and have a quick think
•Group into themes (emergent!)
•Big Groups OK – so are Small
•Read, think and group again
•Use Orange stickies to label groups
•Use Pink stickies for super-groups
•Green for User Stories
59. Results Capture
•Take photos of the analysis
•it’s the evidence
•Store in a project accessible way:
•Sharepoint, Gdrive, Confluence
•Videos – again store.
62. Report
•Photo the brown paper
•Do a one pager of findings
•Illustrative video clips 25secs t0 2mins
•Show and Tell - slide set
•Store in a project accessible way
•audit trail of design decisions
63. Show and Tell Structure
•Background & Hypotheses
•What you did in the session
•With whom
•Photo of the day
•Photo of the results
•Video clips with sound
•What next – how has the project been informed
64. Next steps
•Work with UX designers and product owner to
•Propose design changes
•Propose user needs work (discovery)
•Write new hypotheses
•Then test again