Data on who uses Help?

Subject: Data on who uses Help?
From: "Hart, Geoff" <Geoff-H -at- MTL -dot- FERIC -dot- CA>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Mon, 25 Mar 2002 08:55:28 -0500


Steve Rudman wonders: <<Who uses help? Is there a typical profile for
someone who uses online help?>>

The only typical profile of any use is "someone who needs to know how to do
something", and the characteristics of that someone and the "what" vary from
audience to audience. But in all cases, these people may need overview
information (the steps required to complete a task), nitpicky detail (all
the switches or options for each step in the process), or a combination of
both at different times.

<<I'm also interested in articles that address whether the profile of the
target user for a software application is the same as the target
user of the help.>>

You won't like this answer, but any such information is going to be highly
audience-dependant, and what you read might bear no relationship to your
actual audience. The target user of the help must obviously be the same as
the software user, since nobody is going to open the help unless they're
using the software. The only way to get a good impression of their needs is
to talk to them or perform some other form of audience analysis.

<<My impression is that most help targets a "beginner" user (here, beginner
means someone with minimal experience with the type of
application being used).>>

That's too simplistic, and moreover, may have the overall situation
backwards. Ginny Redish, for instance, reported at the last STC conference
that in some of her surveys of help users, it was actually the experts who
used the help system; beginners often didn't know that it existed, didn't
know how to use it if they did know of its existence, or rapidly got
frustrated in trying to use it and went to bug the experts.

<<Is there a rationale for having "advanced" topics in online help, if the
people interested in such topics are not those who would typically use an
online help system?>>

The goal of any help system must be to provide assistance as rapidly and
directly as possible. If the user needs advanced information, that
information must be available. The problem with putting such information
outside the application (e.g., in a printed manual) is that users must then
seek out that manual and once it's found, go looking for the help topic; in
contrast, a good help system should present all topics relevant to the
current task at the click of a button. That's what makes the help context
sensitive or embedded.

--Geoff Hart, FERIC, Pointe-Claire, Quebec
geoff-h -at- mtl -dot- feric -dot- ca
"User's advocate" online monthly at
www.raycomm.com/techwhirl/usersadvocate.html

"With Linux, customers end up being in the operating systems business,
managing software updates and security patches while making sure the
multitude of software packages don't conflict with each other."--Microsoft
spokesperson in a News.com article

"And just how would that be different from Windows?"--Adam Engst, TidBITS

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PC Magazine gives RoboHelp Office 2002 five stars - a perfect score!
"The ultimate developer's tool for designing help systems. A product
no professional help designer should be without." Check out RoboHelp at
http://www.ehelp.com/techwr
---
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.



Follow-Ups:

Previous by Author: Use of photos in documentation?
Next by Author: Example of a comprehensive sign-off sheet?
Previous by Thread: Re: Data on who uses Help?
Next by Thread: Re: Data on who uses Help?


What this post helpful? Share it with friends and colleagues:


Sponsored Ads