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: Drafts -- some people not clear on the concept...
Subject:RE: Drafts -- some people not clear on the concept... From:"Bill Swallow" <wswallow -at- nycap -dot- rr -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Sat, 21 Sep 2002 01:23:21 -0400
::: There must be some personality type (or types) on the
::: Myers-Briggs schema
::: that simply cannot grasp, cannot appreciate that some
::: things (documents,
::: songs, rough cuts of films) come in rough, provisional
::: form, and are simply
::: preliminary expressions of initial stream-of-consciousness
::: creativity. ... These people, with these personality
::: types, should be banned from all management positions. Or,
::: at the very
::: least, they should be barred by law from looking at
::: anything until it's in at least its third draft.
I'll agree that people should understand the difference between draft
and release copy, but I disagree with what you have stated above.
Technical writing (IMO) is not a stream of consciousness endeavor; there
should very little room for creative expressions as far as content is
concerned. Managers who cite problems with this type of "technical
writing" should be encouraged to do so and should be applauded. As a
technical writer, I do not work to entertain. I work to provide need to
know info to those who need to know. My definition of a draft is a
document that contains the required technical/procedural data but has
not been proofed by SMEs/QA for accuracy.
I can agree that some managers need to learn how to approach conflict
with tact (as do most people). I can agree that the creation of a draft
is a "necessary evil". But, and again this is IMO, the definition of
draft in technical writing is pretty narrow; either the content is there
or it isn't, and it's either accurate or it isn't. And, it's either
factual or it's not technical writing.
Given all this, I'd throw a red flag if I saw a "draft" of a technical
document displaying what appears to be "preliminary expressions of
initial stream-of-consciousness creativity" regardless fo rank/position.
Either it's a finished document, or it's a solid draft, or it's an
outline, or it's not technical writing. (Hmmm, that should keep the list
server warm for quite some time. *lol*)
:)
B I L L S W A L L O W
Information Design & Development Professional
tel/fax: 518.371.1867
wswallow -at- nycap -dot- rr -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FrameMaker-to-PDF TimeSavers Assistants let you enhance & automate navigation
in PDF doc sets (chapter tabs, next/prev chapter/pg, bookmarks, popup menus);
create interactive PDF forms, rollover popups; presentations: http://www.microtype.com
Experience RoboHelp X3! This new RoboHelp release combines single sourcing,
print-quality documentation, conditional text and much more, into the most
monumental release of RoboHelp ever! http://www.ehelp.com/techwr-l
---
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.