Place holder for the User acceptance testing process.
Basic steps for a UAT session:
- make sure people are on the right team to see the feature
- find LP pages that make sense to the people participating in the UAT (i.e. a page that they would normally use)
- Email people requesting participation in the UAT session and schedule calls with them
- Record the conversation to help with note taking
- Compile notes from all participants and write report
- Schedule call with feature squad team lead to talk over the report
Meanwhile, here are some tips from Dan (context was a UAT session with Chris Gregan):
- About recording - phrase it as a question, so it's more of a choice for the person, eg: 'do you mind if I record this to make note-taking later on easier?' - Ask people to think out loud - he said 'nice' quite early on, then went quiet, it would have been good if he'd said what he was thinking all the way through - initial thoughts can be very useful - When people are silent, just say 'tell me what you're thinking, think out loud' - Phrase questions from a one-to-one angle, eg: 'Can you see everything you need to?' Rather than 'other people have said…' - He goes off target a bit by talking about the side panels and shading - but some interesting points - Technical issues - test links before-hand and make sure people are in the right groups before-hand, saves time, especially if people only have 5-10 minutes - Nice friendly, relaxed tone and manner throughout which is great!