Skip to content

Commit

Permalink
Further script modifications
Browse files Browse the repository at this point in the history
  • Loading branch information
benwerd committed Jun 24, 2014
1 parent ad3d087 commit 98495f5
Show file tree
Hide file tree
Showing 5 changed files with 48 additions and 26 deletions.
12 changes: 7 additions & 5 deletions Interviews/Email_Confirmation.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
Email Template – Confirmation for Interview
-------------------------------------------
# Confirmation email for usability study

Hi __[INTERVIEWEE NAME]__,
Hi __[participant name]__,

Thank you for your interest in having a conversation with us about __[the care and feeding of pet gerbils]__.

We want to learn more about the tools and products that __[gerbil owners]__ use, and we’d like to have a discussion with you to learn more about __[your pet gerbil]__.
We want to learn more about the tools and products that __[gerbil owners]__ use, and we’d like to have a discussion
with you to learn more about __[your pet gerbil]__.

We have scheduled you for a conversation on the following date and time:

Expand All @@ -15,7 +15,9 @@ __[10:00 – 10:30 am Pacific Time]__

If that time doesn’t fit with your schedule, please email me back, and I’ll arrange for a different time slot.

The conversation will be conducted via __[a web conference number]__, so you can call in from your phone or on your computer. I will follow up shortly with an email that contains information on accessing and using the __[web conference software]__ for the call.
The conversation will be conducted via __[a web conference number]__, so you can call in from your phone or on your
computer. I will follow up shortly with an email that contains information on accessing and using the
__[web conference software]__ for the call.

After the discussion, we’ll send you __[an awesome incentive]__ as a thank you for taking the time to talk with us.

Expand Down
3 changes: 1 addition & 2 deletions Interviews/Sample_Questions.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,4 @@
Questions for an Interview
-----------------------------
# Questions for an interview

_(Build a collection of questions to ask during your interview by taking these starters and customizing the information to fit what you’re studying. Remember, it’s better to stick with open-ended questions that can’t be answered with a simple yes or no response.)_

Expand Down
3 changes: 1 addition & 2 deletions Surveys/Sample_Questions.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,4 @@
Questions for a Survey
----------------------
# Questions for an online survey

_(Build a collection of questions to ask in online user surveys by taking these starters and customizing the information
to fit what you’re studying. While interview questions should be open-ended, survey questions are best if they're
Expand Down
54 changes: 37 additions & 17 deletions Usability_Testing/Moderator_Script.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,13 @@
Moderator's script for usability testing
----------------------------------------
# Moderator's script for usability testing

Hi, __[participant name]__. My name is __[your name]__, and I'm going to be walking you through the session today.

Before we get started, I just want to go over a little bit of information with you.

You probably already know, but let me explain why we've asked you to participate today. We're testing a website and
product to see what it’s like for web developers to use it.
You probably already know, but let me explain why we've asked you to participate today. We're testing
__[a product type (eg a website)]__ to see what it’s like for __[user type (eg developers)]__ to use it.

I want to start by saying that we're testing the website, not you. You can't do or say anything wrong, and nothing is
I want to start by saying that we're testing __[product]__, not you. You can't do or say anything wrong, and nothing is
going to hurt our feelings.

We want to hear exactly what you think so that we can improve the website.
Expand All @@ -20,35 +19,56 @@ If you have questions, just ask. I may not be able to answer them right away, si
when they don't have someone sitting next to them, but I will try to answer any questions you still have when we're
done.

If you need to take a break at any point or you’d like to quite, just let me know. That’s perfectly ok.
If you need to take a break at any point or you’d like to quit, just let me know. That’s perfectly OK.

Also, with your permission, I’d like to turn on the recording for the conference. The video will only be used by
us internally, and it will really help me with note-taking.
Also, with your permission, I’d like to record this session. The video will only be used by us internally, and it will
really help me with note-taking.

Is it all right if I turn on the conference recording?

__TURN ON RECORDING__

__[If other people are in attendance:]__

There are also a few other people observing today. They’re members of the product team, and they’re here to watch and
learn how to make the website better. They won’t be saying anything during the session, but I may check to see if they
have any questions.

Do you have any questions so far?
__[Continue:]__

Okay, to start, I’d like you to take out the participant guide that I emailed you yesterday. Do you have it handy?
Do you have any questions so far?

Okay. Now I’m going to read you the instructions for today’s session.

__READ INSTRUCTIONS__
## Instructions

On the next few pages you’ll find a list of tasks. Approach these tasks as if you were sitting alone at work or home.

As you work, please do the following:

* Read each task out loud before you begin.
* Remember to think out loud. Talk about what you are thinking, doing, experiencing, and expecting.
* Whenever you have a question or comment, please state it! You can say anything you want - positive or negative.
* You’re almost ready! Before we begin, we have a few more questions to start things off.

## Pre-task questions

_A handful of questions that set the context for the user: how they'd describe their role, which products they
currently use, and so on._

## Tasks

__READ PRE-TASK QUESTIONS__
_A series of atomic tasks that encourage the user to perform a single action with your product. Each task should have
a number of planned follow-up questions: "where would you look if you wanted to find X?" "How would you describe what
this product / feature does?"_

Okay, let’s get started. I’d like you to read each task out loud, complete the task, and remember to think out loud
throughout the process.
## Post-task questions

Please begin.
_A handful of questions that summarize the user's experience. For example, what did they like most? What did they
like least? How likely are they to recommend the product to friends or colleagues? If they could change one thing
about the product, what would it be?_

__DO TASKS__
## Conclusion

__READ FINISHING UP SECTION__
We're all done. Thank you so much for your time!

2 changes: 2 additions & 0 deletions Usability_Testing/Participant_Email.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,5 @@
# Email to individual usability study participant

__[Name of your usability study]__
__[Date and time of participant appointment]__

Expand Down

0 comments on commit 98495f5

Please sign in to comment.