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.
1. If you were to list the five most stressful aspects of being a
technical writer (from most to least stressful), what items would you
list?
(for example: 1. high work load, 2. tight deadlines,.....)
2. Are there any specific strategies you use to cope with work stress?
I have to agree with Darren that I find the job of technical communicator
not terribly stressful where I am. Of course, previously I worked as a
project manager for a small start-up computer consulting firm for 3 1/2
years prior to this, so just about anything would be low stress compared to
that!
There are 2 things that have caused me stress in this job though. First, I
am the soul technical communicator, and I am "owned" by the communications
department. That puts me way out of the loop with the development team. As
a result, I find myself sometimes battling to get the information I need to
create the documentation (including a fully functional copy of the software
I am creating user manuals for!). I get things like "What do you need that
for?" or "I'll take the screen caps and send them over to you." Like all I
need to do is place some pictures and write about them without knowing how
they flow, what did the end user do to create the result, what's the
logic...so forget any insight about the product. Now, that is not the norm.
I completed another project where the staff I worked with was very helpful
and forthcoming with information. The other stressful element is when they
give me no deadline and then, a few days or a week later, in passing mention
that it will be ready to go out in 2 weeks, right?
To cope with the lack of shared information, like Bill answered in his
reply, I commiserate with individuals in the same boat. For instance, the
group that supports the clients on the software get stressed because they
are introduced to new functionality in upgrades a day or 2 before it is
sent to the clients. They really don't have time to review it before they
have to start supporting it.
To cope with deadlines being sprung on me, I ask up front when I am given a
project. And if I don't get an answer from the primary individual, I find
out who else is involved with the project and what their expectations are.
Then I have a better idea of how to plan the work.
Kristin D. Field
Technical Communicator/Proofreader
Law School Admission Council
215.968.1141
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
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/
---
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.
