The wiki will be unavailable from 7am until 9am on Thursday, 24 August, 2017.
When you're setting up a user test, make sure you've done:
- Define what you're checking and get it agreed with PO and stakeholders - the scope should not be too great and should cover important interactions
- Decide on a venue out a venue and book a room (best to book for entire day to allow for setup)
- Decide on a timescale, anything from 15-30 minutes depending on the scope and the amount of user you want to test (aim for 4+)
- Call for volunteers - ideally regular users of the section in question that match target demographics.
- Publicise on appropriate landing pages
- Contact Faculty/Prof Services Marketing people for promotion
- Use Twitter/Facebook channels if appropriate
- We maintain a list of past participants that are happy to participate in user testing
- Draft a set of question/tasks
- Get stakeholder input and agreement
- Do a test run, and tweak if you go over/under allotted time.
- Write out a script which should include:
- An introduction of who you are
- What you're hoping to accomplish, e.g. "we want to see whether the Library website is meeting needs"
- The reassurance: "You're not being tested, the site is. If you get stuck, we've got it wrong and we need to know how to fix it"
- Get the room set up:
- Get the MBP
- Get an external keyboard and mouse
- Invert the mouse wheel for "normal" users
- Fire up Silverback
- Fire up Virtualbox
- Set it to full screen
- Fire up Internet Explorer
- If you're connecting a second monitor set the Display to Mirror displays (otherwise Silverback won't record the second screen!)
- Print out scripts
- Make sure Silverback has started recording before each session starts
- Run your test as per your script
- Get authorisation to record (or don't record)
- Take plenty notes
- Output the Silverback videos and stick them somewhere if you need to keep them
- Write up your notes
- Summarise key concerns and create an action plan and proposed next steps