Test facilitator checklist.

Pre-test.

• Know the objectives of the test.
• Know the scenarios.
• Practice facilitating in a pilot test.
• Make sure the room is set up properly. Turn on the computer and bring up the web site.
• Make sure all the materials for the session are in a folder marked for that particular participant. It should include:
  • Consent form.
    See an example consent form.
  • Pre-test questionnaire.
    See sample pre-test questionnaire.
  • Your scripts.
    
    • Pre-test intro. script.
      See an example pre-test script.
    • Pre-test interview script.
      See an example pre-test interview.
  • The task scenarios.
    See an example task transformed into scenario form.
  • Post-test questionnaire.
    See sample post-test questionnaire (part 1)
    and post-test questionnaire (part 2).
  • Participant incentive or gift.
• Have a pad and pens or pencils for taking notes.
• Have a pen for the participant to sign the consent form.

During the test.

• Greet the participant.
• Introduce yourself and the other team members.
• Offer refreshments.
• Show the participant where to sit.
• Establish rapport and context.
  Take some time to establish a rapport so that the participant will feel comfortable during the test. Explain how usability testing the current UMD web site is part of the redesign process.
• Do not brief the participant from memory.
• To insure that all participants are treated alike, read the same script for each participant. Try to do it in the same manner for each participant.
• Use a tone that is professional and warm when you read the scripts.
• Ask the participant to fill out the pre-test questionnaire. Compare it to the recruiting questionnaire, if their are major discrepancies you may want to cancel the session.
• Ask the participant to read and sign the consent form.
• Conduct the pre-test interview.
• Conduct the test.
  • Sit slightly back from the participant in a chair that is lower than his.
  • Remind the participant to wait for you to say when to start the first task, to tell you when he or she has finished the first task and then wait for you to say when to start the second task.
  • Remind the participant to think out loud.
  • Don't help! If asked for help, say that the goal is for the participant to try to solve the problems on their own. If needed you can answer their question with a question. If they ask, did I do that correctly?" Say, "Do you think you did that correctly?" Of if they ask, "What should I do?" Say "What do you think you should do?".
  • Listen! Do not lead. Be sure to stay neutral in your words and body language. Be careful not to ask leading questions that may skew the participant's responses. It's about their opinions, not yours.
  • Do not indicate if a task is failing or succeeding.
  • When a participant is frustrated or confused, don't belabor the point. We only need to see if the participant can complete the task under "normal" conditions in a reasonable amount of time.
  • Do not probe for a design solution. However, make a note of it, if a participant spontaneously offers one.
  • Keep discussion minimal, defer this to the post test interview.
  • Take notes when relevant.

Post-test.

• Ask the participant to fill out the post-test questionnaire.
• Debrief the participant. Start with a question like "so what did you think?". Go over the post-test questionnaire. Go into specific comments or problems. Try to find out why problems occurred. Do not rush. Do not solicit design solutions from the participant. Note them if they are offered.
• Thank the participant for their participation and contribution.
  Emphasize how the knowledge we gain from this process will help UMD make a more usable web site.
• Give them the parting incentive/gift.
• Put all the forms in the participant's folder.
• Shutdown the computer.