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: Do I have a right to feel POed?? From:"whitedh" <whitedh -at- attbi -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 22 Aug 2002 12:43:36 -0400
Do you have a 'right' to be upset? Yes.
However, and I don't intend to be cute or unsympathetic, this is a
'normal' situation in our field. So many have commented upon it on this
forum and in other venues.
There's the classic development model in which technical communications
is an integral part of a development and deployment project. We seek
this; we promote this. However, those who run such projects are
designers or engineers, or a combination thereof, and they are primarily
concerned with what they see as the most important aspects of the
project: design, test, & implementation.
How many times have technical writers, as independents or as contract
consultants, come into an assignment to find that they have to prepare
documents that should have been done months (or years) before. The
application or tool may be just ready for testing and deployment when
the manager remembers that company policy requires a CMM or ISO9000
audit; at this point, he (or she) scurries to find a writer and editor
who will do the feasibility study, concepts document, requirements, and
design specs in the week prior to testing. And, by the way, please write
up the formal test documents for all stages of testing, too! Of course,
we probably ought to have a programmer's reference and, maybe, a guide
for users--but that would be 'gravy.'
Okay, so I may be a bit sarcastic. It happens. There's a schedule change
and there's your impending absence from the documentation team; come up
with and offer a plan to accommodate both and make that manager's job
easier. That person should have thought of this before and should have
invited you to that meeting. But, keep in mind that no company or MBA
program develops leadership; all seek merely to turn out 'managers.'
Don White
804.795.2914
whitedh -at- attbi -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Check out the new release of RoboDemo, our easy-to-use tutorial software.
Plus, buy RoboHelp Office in August and save $100 with our mail-in rebate.
Get details and download free trial versions at 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.