Database Reference
In-Depth Information
Greeting and
introduction
"Thank you for coming. I'm Carolyn Snyder.
I'm an independent consultant, and I
specialize in conducting sessions like this
one. Here at [company] we're working on a
product for [target market] that will help them
to [basic functionality]. I'll go over the main
points in this form we sent you. The purpose
of today's session is for you to help us figure
out how to make this interface more user-
friendly before we finish developing it. But
believe it or not, we aren't going to use a
computer. As you'll see, we've actually
created paper versions of the screens, and
this guy named Carl will be playing the
computer."
Welcome the users
(hang up coats, offer
a beverage, ask if the
directions were
okay).
Introduce yourself
and the company.
Describe the
interface being
tested.
Give users the
informed consent
form (ideally, they
brought the copy you
sent ahead of time).
Explain the goals of
the session.
Introduce the notion
of paper prototyping.
Their role
"Frank, this is Ernest. The two of you will be
working together. We'll give you some tasks
that we think are representative of what
people might do in real life. [Give example.]
Your job is to tell us what makes sense,
what's confusing, whether it works the way
you'd expect it to, etc. You are here because
you know [area of expertise], so your
perspective will help us make this product
more useful."
If using co-discovery,
introduce the two
users.
Explain what's
expected of them.
Remind them of their
qualifications.
Social
concerns
"About half a dozen members of the
development team will be sitting in the same
room, observing quietly and taking notes.
We're not going to be videotaping. Keep in
mind that we're testing the interface—we're
not testing you—so if you run into any
problems it's not your fault and it means that
there's something we need to change. I'll be
sitting next to you, and I can help you if you
want. We held our first session this morning,
and we learned a lot; in fact, we've already
made some changes. We really appreciate
having you come and help us out."
Explicitly mention in-
room observers
and/or videotaping.
Explain that you're
testing the interface,
not them.
Reassure users
about what will
happen if they
encounter any
difficulties.
Reiterate how
valuable this is and
how much you
appreciate their help.
Search WWH ::




Custom Search