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: Who's the User? (You're the user!) From:johanne -dot- cadorette -at- locusdialog -dot- com To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 4 Apr 2002 14:49:7
SIANNON -at- VISUS -dot- JNJ -dot- com wrote: Have any of you found, in your experience,
whether overt clarification of the audience with your SMEs helps them
provide you with morethorough information?
I run into this a lot, because most of our guides are destined to system
administrators who need to have a certain level of expertise with Windows,
PBXs and telephony environments. Our developers often respond to my queries
for more information with, ?oh, they?ll know how to do this.? While it?s
true that most system administrators of our system will know how to do
"this," it?s important that some process be documented. Why? Because
somewhere, someone out there might not know. And documentation, even in the
form of manuals, is about much more than explaining how to do something.
It?s also an easily accessible archive, and an organized, user-friendly
history of the product. Our marketing people and product engineers often
use our guides to compare versions, or to help a client who has an older
version, or just recall how something used to be done. If you look at it
that way, then yes, it?s important to document stuff that people reading
the guides might know.
Of course, it goes without saying that there are limits to this. As a rule,
we avoid documenting procedures that concern other software. I wouldn't,
for example, tell people how to start the computer or fix problems with
Windows, for example.
My two cents,
Johanne Cadorette
johanne -dot- cadorette -at- locusdialog -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Free copy of ARTS PDF Tools when you register for the PDF
Conference by April 30. Leading-Edge Practices for Enterprise
& Government, June 3-5, Bethesda,MD. www.PDFConference.com
Are you using Doc-to-Help or ForeHelp? Switch to RoboHelp for Word for $249
or to RoboHelp Office for only $499. Get the PC Magazine five-star rated
Help authoring tool for less! Go to 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.