TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:RE: User research From:Sean Hower <hokumhome -at- freehomepage -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 15 Jan 2003 10:07:16 -0800 (PST)
One thing about interviews versus observations.
People do not always have a clear understanding of what they do and why. Their perceptions often do not match what is actually going on. During an interview, you may ask something like "What are the steps you use to get your job done." The interviewee might respond with six steps. If you were to put that same interviewee into his/her own working environment and observe the steps they follow to complete their task, the reality may actually be different. This is due to a number of different reasons, including the interviewee's own perception of the kind of information the interviewer is looking for. The interviewee will selectively filter out information because they think it's not important or they are not even aware of it.
The questions you ask can and will influence the answers you get, and that in turn will have a dramatic effect on your results. That's why observations are usually the best route to go. You can watch and note exactly what the interviewee is doing. You can then ask questions as they go along. You'll find that the interviewee may not have answers to simple questions about why they do what they do, mostly because they probably haven't even thought about it themselves.
And don't forget to try to get a good cross sampling of people to observe and interview. The common mistake is to interview only power users or only newbies. You want to get a broad spectrum of participants to really understand what's going on. This will cost you time and money though. So it becomes a balancing act.
********************************************
"And in the morning, I'm makin waffles." ~ Donkey
Sean Hower - tech writer http://hokum.freehomepage.com
_____________________________________________________________
Create your own web site for FREE at http://www.freehomepage.com
_____________________________________________________________
Select your own custom email address for FREE! Get you -at- yourchoice -dot- com w/No Ads, 6MB, POP & more! http://www.everyone.net/selectmail?campaign=tag
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A new book on Single Sourcing has been released by William Andrew
Publishing: _Single Sourcing: Building Modular Documentation_
is now available at: http://www.williamandrew.com/titles/1491.html.
Help Authoring Seminar 2003, coming soon to a city near you! Attend this
educational and affordable one-day seminar covering existing and emerging
trends in Help authoring technology. See http://www.ehelp.com/techwr-l2.
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.