This document provides guidance on how to involve a whole team in analyzing user testing results. It recommends conducting analysis sessions where the entire team observes user tests together, takes notes on insights, and then groups the notes to identify shared understandings and next steps. The process involves preparing observers ahead of time, focusing observation notes on user behaviors rather than opinions, and recapping after each test to discuss findings. The goal is to save time, create shared understanding across teams, and increase learning through direct exposure to users.

1. How to involve your team in analysis
Kea Zhang
Head of Product/UX in Teston

2. How to analyse with your whole team
● Why?
● What it involves
● Who to bring in
● How to do it

3. How to analyse with your whole team
● Why?
● What it involves
● Who to bring in
● How to do it

4. User research = Team sport

5. How does this apply to user testing analysis?
1. Save time
2. Create a shared understanding

7. How does this apply to user testing analysis?
1. Save time
2. Create a shared understanding
3. Increase learning velocity

8. ● Single best way for teams to produce better design work
a. Direct exposure to users
● Recommendation
a. 2 hours / 6 weeks (225 hours)
b. Each person on the team
Research by UIE shows…
https://articles.uie.com/user_exposure_hours/

9. What happens in reality?

13. How to analyse with your whole team
● Why?
● What it involves
● Who to bring in
● How to do it

14. The basic process
1. Preparation work
2. During observations
a. Everyone in the room is taking notes on post its during each test
b. Group post its after observing each test
3. After reviewing all tests
a. Review groups together
b. Agree on
i. Most important insights
ii. Next steps

15. How to analyse with your whole team
● Why?
● What it involves
● Who to bring in
● How to do it

16. Everyone!

17. Especially...
● The UX team
a. UX designers
b. Visual designers
c. Copy/content people
d. Data/optimisation specialists
● Product
a. Product managers and product owners
● Front-end developers
a. Mobile
b. Web

18. Observing 1 or 2 sessions is enough to start with
● Easier to agree to watch 1 test than a whole day of testing
● Ask them to join at the start of the day if they can
Back-end too!

19. ● Someone in the observation room needs to be the facilitator
● The role
a. Preparation work and setting up the room
b. Explain instructions at the start
c. Keep the room focused during testing
d. Group findings after each test
e. Recap at the end of the day
Don’t forget the facilitator!

20. How to analyse with your whole team
● Why?
● What it involves
● Who to bring in
● How to do it

21. Prep work
HOW TO DO IT?

22. ● Schedule at least 30 min between each user test
a. Allow time to go through notes taken in between
● Book an observation room
a. Meeting room is enough
● Ensure space for writing and post it notes
a. Whiteboard
b. Or wallspace for whiteboard clingfilm
1. Preparation

25. Post it prep
● Enough post its for everyone in the room
● One colour for each participant
a. 5 participants = 5 different colours
b. Enough of each colour for each observer

26. The chart
HOW TO DO IT?

27. Review the test
A user test typically consists of…
● Intro interview questions
● Tasks
● Wrap up interview questions
Group these into overarching steps and number the steps

28. The chart:
A fictional example
HOW TO DO IT?

29. Test of vg.no
Group into overarching steps and number the steps, e.g.:
1. Intro questions
2. Find vg.no
3. Log in to VG
4. Find an article on VG
5. Etc.
6. Etc.
7. …
8. ...

30. 1 2 3
Intro questions Log into vg.no Find an article...
Steps along the horizontal axis

31. 1
Intro questions
Vertical axis
Positive
Negative
General

32. 1 2 3
Intro questions Log into vg.no Find an article...
Pos
Neg
General

33. Pos
Neg
General
1 2 3
Intro questions Log into vg.no Find an article...

34. Pos
Neg
General
1 2 3
Intro questions Log into vg.no Find an article...

35. 1 2 3 4 5
This is why you need wallspace...

36. Add a parking lot for solution ideas!
Features, content, design, etc.

37. Before the test
HOW TO DO IT?

38. Prepare the observers
● Explain the goal of testing
a. What are you testing? Why?
b. What problems are you trying to solve?
c. What hypotheses/assumptions are you testing?
● Provide instructions
a. Post it notes
i. One observation per post it
ii. Number the post it based on the chart steps
2

39. Prepare the observers
● Explain the goal of testing
a. What are you testing? Why?
b. What problems are you trying to solve?
c. What hypotheses/assumptions are you testing?
● Provide instructions
a. Post it notes
i. One observation per post it
ii. Number the post it based on the chart steps
iii. Use the right colour for each participant
Bob
Anna
Remind yourselves
of the colours!

40. Prepare the observers
● Explain the goal of testing
a. What are you testing? Why?
b. What problems are you trying to solve?
c. What hypotheses/assumptions are you testing?
● Provide instructions
a. Post it notes
i. One observation per post it
ii. Number the post it based on the chart steps
iii. Use the right colour for each participant
b. How to use the chart
1
Intro
questionsPositive
Negative
General

41. ● Behavioural
a. ‘Used different search terms than we expected’
b. Summary comment: ‘completed task easily’
● Quotes
● Attitudes and beliefs (typically go into general comments)
a. ‘I hate paying online, it doesn’t feel safe’
● Timestamps
a. For video clips or to show others later
Give some tips on note-taking

42. Focus on what users do,
not what they say

43. Focus on observations!
(No hidden agendas around solutions)

44. During testing
HOW TO DO IT?

45. Listen, observe, take notes

46. Recap after each test
● Group findings
a. Remove duplicates
b. Discuss differences in
observations
● Agree on placement in chart
a. Useful framework:
i. No problem
ii. Cosmetic
iii. Hassle
iv. Critical
1
Intro
questionsPositive
Negative
General

47. After testing
HOW TO DO IT?

48. Recap on findings
Look for patterns and critical issues

54. Agree on top 5 insights
● Why?
a. Align
b. Create shared understanding
c. No need for full blown report
i. Pictures and/or Google doc summary is enough
d. Useful as an executive summary of the test

55. Don’t forget:
Adapt the method to your needs!

56. Thanks for listening :)
Questions or comments?