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: Documentation Correctness was Re: How many levels ofindentsandheads are reasonable?
Subject:Re: Documentation Correctness was Re: How many levels ofindentsandheads are reasonable? From:"Gene Kim-Eng" <techwr -at- genek -dot- com> To:"Butler, Darren J Ctr 584 CBSS/GBHAC" <Darren -dot- Butler -dot- ctr -at- Robins -dot- af -dot- mil>, <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 17 Oct 2007 11:18:43 -0700
Well, I suppose there's always the exit interview...
Actually, it is sometimes possible for Technical
Publications to help effect change in the development
process. Usually, though, it is preceded by someone way up
on the food chain observing your effectiveness and either
holding you up as an example that the rest of the company is
expected to follow or formally designating you as a lead
resource in some executive-driven process improvement
initiative. If you've ever gotten one of those emails from
your company's CEO that say "I know you will all provide....
with your full support in this effort," with its implied "or
else" message, that's the sort of thing that you'll need
backing you up.
Gene Kim-Eng
----- Original Message -----
From: "Butler, Darren J Ctr 584 CBSS/GBHAC"
Would it be fair to say that a company's TW department has
some level of
responsibility in (at least attempting to) point out any
short-comings
and errors of the developmental process? The TWs may be the
only "canary
in the coal mine" to alert that things are going horrible
wrong -- just
before we pass out.
I guess it all depends on whether or not the documentation
is parallel
to product development or an after - (w-a-a--y after) -
thought.
Have any of you successfully fostered process-change?
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-