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.
RE: Why not do it ourselves? (Was: using 3rd-party books)
Subject:RE: Why not do it ourselves? (Was: using 3rd-party books) From:"Carey Jennifer (Cry)" <jennifer -dot- carey -at- cdi -dot- cerberus -dot- ch> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 19 Sep 2001 15:12:55 +0200
<<That is, it's one thing to write about how a product works, but
it's quite another to write about how people actually use it. These two
information sets can differ significantly, and I think the 3rd-party books
often cover the second scenario.>>
That's exactly it!! The thing is, as we move more and more into the
direction of "usability" and "information design" and delivery, it seems
that we are learning that maybe we should be writing to "how people actually
use it" rather than "how the product works". I guess my main concern would
be that certain important information not get excluded in the process of
what could potentially turn into the dumbing down of our manuals, which was
why I was thinking that the beginner's version would include more of the
simple stuff while the advanced one would have all the other stuff that more
sophisticated users would want with little-to-no overlap between the two.
<<The third party books are written because someone believes that the
manuals don't fill all needs. Usually, they are right.>>
<<In order to be truly objective, the bugs, (er, features,) would have to be
documented together with workarounds. Marketing gets upset when this
happens. >>
Of course, major changes in procedure/approach do require buy-in/approval
from relevant management, but is this the only thing stopping us? Do we
think that the other more "objective" manual is the way it "should" be?
A landmark hotel, one of America's most beautiful cities, and
three and a half days of immersion in the state of the art:
IPCC 01, Oct. 24-27 in Santa Fe. http://ieeepcs.org/2001/
+++ Miramo -- Database/XML publishing automation. See us at +++
+++ Seybold SFO, Sept. 25-27, in the Adobe Partners Pavilion +++
+++ More info: http://www.axialinfo.comhttp://www.miramo.com +++
---
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.