How to do a user observation
•Download as PPTX, PDF•
0 likes•500 views
Slides from the Transylvania Foresight Camp workshop "DIY User Observation," by Tracy Rolling
Recommended
Recommended
More Related Content
Similar to How to do a user observation
Similar to How to do a user observation (20)
Recently uploaded
Recently uploaded (20)
How to do a user observation
- 2. 2 Bugs © 2013 HERE | Title | Author | Company confidential
- 3. 3 Paths and flows bugs © 2013 HERE | Title | Author | Company confidential
- 4. 4 Human Emotion Paths and flows Bugs © 2013 HERE | Title | Author | Company confidential
- 5. 5 A Moderator You will need… © 2013 HERE | Title | Author | Company confidential
- 6. 6 Device(s) Moderator You will need… © 2013 HERE | Title | Author | Company confidential
- 7. 7 Innocent people Device(s) Moderator You will need… © 2013 HERE | Title | Author | Company confidential
- 8. 8 Notebooks and pens Innocent people Device(s) Moderator You will need… © 2013 HERE | Title | Author | Company confidential
- 9. 9 Your team Notebooks and pens Innocent people Device(s) Moderator You will need… © 2013 HERE | Title | Author | Company confidential
- 10. 10 Cookies Your team Notebooks and pens Innocent people Device(s) Moderator You will need… © 2013 HERE | Title | Author | Company confidential
- 11. 11 This is not a test or a puzzle There are no wrong answers You cannot hurt our feelings The Preamble © 2013 HERE | Title | Author | Company confidential
- 12. 12 Do exactly what you would really do. Imagine yourself in the situation. Give up. The Preamble © 2013 HERE | Title | Author | Company confidential
- 13. 13 New features What to observe © 2013 HERE | Title | Author | Company confidential
- 14. 14 Core flows New features What to observe © 2013 HERE | Title | Author | Company confidential
- 15. 15 You are going to visit your friend who lives at 66 Elm Street in London. Use category search to find a restaurant to take your friend to and then find a route from their house to the restaurant. Scenarios © 2013 HERE | Title | Author | Company confidential
- 16. 16 You are going to visit your friend who lives at 66 Elm Street in London. You want to take them out to a nice restaurant to thank them for letting you stay at their place. Scenarios © 2013 HERE | Title | Author | Company confidential
- 17. 17 When you still have time to make changes Right before starting the next version When to do an observation © 2013 HERE | Title | Author | Company confidential
- 18. 18 15-20 minutes is enough 1 scenario, 2 people Some details © 2013 HERE | Title | Author | Company confidential
- 19. 19 Let it cook How do you get your learnings into your product © 2013 HERE | Title | Author | Company confidential
- 20. 20 Let it cook Talk about it How do you get your learnings into your product © 2013 HERE | Title | Author | Company confidential
- 21. 21 Let it cook Talk about it Track it How do you get your learnings into your product © 2013 HERE | Title | Author | Company confidential
- 22. 22 Let it cook Talk about it Track it Prioritize it How do you get your learnings into your product © 2013 HERE | Title | Author | Company confidential
- 23. 23 Let it cook Talk about it Track it Prioritize it Care about it How do you get your learnings into your product © 2013 HERE | Title | Author | Company confidential
- 24. 24 Recruit users Recap © 2013 HERE | Title | Author | Company confidential
- 25. 25 Figure out what to test Recruit users Recap © 2013 HERE | Title | Author | Company confidential
- 26. 26 Write your scenarios Figure out what to test Recruit users Recap © 2013 HERE | Title | Author | Company confidential
- 27. 27 Set up devices & space Write your scenarios Figure out what you need to test Recruit users Recap © 2013 HERE | Title | Author | Company confidential
- 28. 28 Do a test run Set up your devices and your space Write your scenarios Figure out what you need to test Recruit users Recap © 2013 HERE | Title | Author | Company confidential
- 29. 29 Take Notes Do a test run Set up your devices and your space Write your scenarios Figure out what you need to test Recruit users Recap © 2013 HERE | Title | Author | Company confidential
- 30. 30 Meet, talk, prioritize Take Notes Do a test run Set up your devices and your space Write your scenarios Figure out what you need to test Recruit users Recap © 2013 HERE | Title | Author | Company confidential
- 31. 31 Repeat Meet to talk and prioritize improvements Take Notes Do a test run Set up your devices and your space Write your scenarios Figure out what you need to test Recruit users Recap © 2013 HERE | Title | Author | Company confidential
- 32. Now, let’s play!
- 33. 33 Bonus Slide! • Silverback (costs about 50 euros) http://silverbackapp.com/ • Rocket Surgery Made Easy, Steve Krug • Survey Monkey © 2013 HERE | Title | Author | Company confidential
Editor's Notes
- What do you get out of a user observation? EMOTIONS. Your users’ emotions and your own emotions. Everyone on the team knows deeply that you are making the product for people. You may not find out what you are doing right, but you will definitely see what you are doing wrong. Paths through the app Bugs will get fixed faster You will see the human suffering that your bug causes and it will get fixed.
- What do you get out of a user observation? EMOTIONS. Your users’ emotions and your own emotions. Everyone on the team knows deeply that you are making the product for people. You may not find out what you are doing right, but you will definitely see what you are doing wrong. Paths through the app Bugs will get fixed faster You will see the human suffering that your bug causes and it will get fixed.
- What do you get out of a user observation? EMOTIONS. Your users’ emotions and your own emotions. Everyone on the team knows deeply that you are making the product for people. You may not find out what you are doing right, but you will definitely see what you are doing wrong. Paths through the app Bugs will get fixed faster You will see the human suffering that your bug causes and it will get fixed.
- Must PRACTICE ahead of time. Must understand and learn how to make the user comfortabl Has to be aware of the dangers or leading or guiding the user while still helping get information from them Has to be capable of behaving in a neutral manner Has to be capable of shutting up
- —should PRACTICE ahead of time.
- Should not be developers or designers unless you are building something for developers or designers Friends in other start ups Should already be users of your platform so that you know you are testing your own UX and not the platform UX If you work in a larger company, recruit from Finance, marketing, and HR. They will be excited to be heard.
- No laptops.
- --Three observers max NO TALKING NO SIGHING Ideally, you should have a monitor that shows the screen facing away from the user so that your team can easily see both the screen and the person’s face. If you cannot, it is also ok to have people stand behind the person to watch. Not more than two in that case.
- So that the people feel appreciated
- People want to be liked. They want to be nice. They want to succeed. If you fail to get a person to overcome their better social nature you will not learn as much. You need people to be honest, not nice.
- People tend to treat the scenarios as problems on a math test to be solved. You need the person to transcend the lab-like environment and the fact that they have three eager developers taking notes so that they behave the way that they really would.
- You should know what your core use cases are. You should always test these, to make sure that you haven’t broken them with your new features. Then you want to test your new features. Create imaginary scenarios
- You should know what your core use cases are. You should always test these, to make sure that you haven’t broken them with your new features. Then you want to test your new features. Create imaginary scenarios
- Be just specific enough. It has to be a situation that the person can imagine themselves in, not a set of instructions Don’t tell the person how to do tell them what to do.
- Be just specific enough. It has to be a situation that the person can imagine themselves in, not a set of instructions Don’t tell the person how to do tell them what to do.
- The user observation should not be the only testing you do. You should validate your designs and your concepts with users by other means before you spend the energy to build a product. Hallway tests, paper prototypes, click flows Do your user observation when you have frozen feature development, but before you release, so that you have time to make some improvements before you release. It is very frustrating for a team to see a user observation, identify issues, and then release without getting a chance to fix them.
- In 15 minutes you will get a lot of information. You want different people to do the same scenarios so that you can see more than one approach. Also, it is interesting for people on team discussion afterward, to understand that different people have different approaches to your product.
- Schedule the rehash meeting a week after the observation Because emotions Let yourself forget some things, it will help you prioritize
- Team meeting Can have beer Post it notes Limit what goes on the notes, but let everyone go over their lists of issues Track it
- This is the hardest part. Put it in your team’s KPIs. 20% of team capacity will be spent each release making improvements based on user feedback. Measure it. Save a sprint for it.
- This is the hardest part. Put it in your team’s KPIs. 20% of team capacity will be spent each release making improvements based on user feedback. Measure it. Save a sprint for it.
- This is the hardest part. Put it in your team’s KPIs. 20% of team capacity will be spent each release making improvements based on user feedback. Measure it. Save a sprint for it.