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.
I agree with your points except for part of Number 5. Never offer to take
notes for them--they all too easily assume TW's are glorified typists, such
a thing is too easily misconstrued as proof of that assumption. I'd offer
to make my notes available if there were questions, but I'm not going to be
the project secretary.
MTC
Connie Giordano
-----Original Message-----
From: Justin Cascio [mailto:justin-paul -dot- geo -at- yahoo -dot- com]
Sent: Monday, May 22, 2000 12:20 PM
To: TECHWR-L
Subject: RE: them engineers
1. Get buy-in from management. Let them know that in order for you to do
your job, you need a few hours of the engineers' time. They have to make
sure that they are freed up enough to make talking to you one of their job
priorities.
2. Schedule short meetings with the engineers. Be prepared so you don't take
more of their time than you need.
3. Bribe with chocolate.
4. Send reminders of due dates for their edits, etc.
5. Be helpful to them-- for instance, you can write out a few nice little
methodologies for them on their internal processes, offer to take notes in
their meetings
[snip]
