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:Lone Writer Rant "You don't need to know that..." From:John David Hickey <jdavid -at- FARABI -dot- COM> Date:Wed, 30 Sep 1998 17:30:41 -0400
Greetings!
<grumble>
I gotta tell ya... If I wasn't such a professional and committed to finding
the right information for the manuals, half my instructions would read
"We're not really sure what this does, but as long as you don't select it,
you'll be fine" or "I don't really know what that button does, but all I
know is that it works" or "Just follow dese instructions and don't ask why,
or da cute wittle bunny gets it, see?".
Every time I've got a question on a procedure that challenges the
developers, it's the same old tune:
"The user would never do that, so it won't ever be a problem"
"Why do you want to know that?"
"You don't need to know that information."
"Nobody ever reads the manuals anyways, so what's the difference?"
"Who cares?"
So I have to keep hammering away with questions until I get the answers I
need, but it annoys the developers and it discourages me. It's like what I'm
doing is a necessary evil, but not that important. So my deadlines get
blown, documentation is moved to the bottom rung on the priority ladder, and
the books never see the pubishing light. At least I still get paid, right?
Ahhhh... I know, it's part and parcel of the job. But have any of you ever
been able to promote documentation in your companies so that it becomes
more important? Have you ever been able to convince your clients that
documentation should be given more of a priority? If so, how did you do it?