Jamie,
I think this is a super plan. You might want to come up with 2-4
Big Questions that you want to observe for during the individual
sessions. This doesn't seem like very much, but the point is to
observe as much as possible rather than interviewing. Specifics
usually reveal themselves along the way during the session.
You could also consider asking the participants for artifacts that
relate to what you want to find out, like reports or forms that are
inputs to their tasks or reports, emails, or whatever that might be
outputs of their tasks. Think about looking at how your product fits
into their overall work.
Get someone to help you take notes, if at all possible. Running
these kinds of sessions and observing closely takes a lot of
concentration and effort. If you have someone else to jot down notes,
it can really free you up to ask follow-up questions and just be
present.
Consider taking digital photographs of your users' work spaces and
any forms or other artifacts that they use that you can't take copies
away with you.
Also consider recording the sessions on digital audio, even if you
do have a note taker.
Closing the day with a group discussion is a great idea. Again, I
recommend having 1 or 2 topics that you want to talk about as a group,
remembering that each person will take a minute or two to answer the
question or contribute to the discussion about each topic you ask about.
What are you going to do with the data you collect?
Dana
:: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: ::
Dana Chisnell
desk: 415.392.0776
mobile: 415.519.1148
dana AT usabilityworks DOT net
www.usabilityworks.net
http://usabilitytestinghowto.blogspot.com/
On Feb 2, 2009, at 11:06 AM, Jamie McAtee wrote:
I am being given the opportunity to visit a client of our software to
do some user research. I have never been on site with any of our
clients before.
At this client we have 3 user groups two who do different tasks and
one super user who can do everything plus config.
I only have five maybe six hours depending on flights being on time
etc.
We have full access to both groups all day but I would like to send
them some sort of schedule so they are not just sitting around
waiting on us.
Goals:
1. Understand the users and how they use the software.
2. Uncover any pain points.
3. Bring back recommendations for changes.
Right now my plan is to do a contextual inquiry and watch one member
of each group work through their tasks using the software. Then move
to either an interview or a focus group of what they think about the
software.
As far as time most of it will be spent with the individual users and
not the super user.
This is the first time the company has sent anyone to do something
like this.I am hoping it goes well and we can bring back good
information so we can do some more of these visits.
Advice is appreciated!
________________________________________________________________
Reply to this thread at ixda.org
http://www.ixda.org/discuss?post=38073
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
