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.
This is how things were when I started out here, as that was how the
previous tech writer did things. And I came in as a contractor, so my
position wasn't in the regular work flow. And there had been no tech
writer, so we have 2 years to catch up on.
How I'm changing things:
The first thing that I do when assigned to a new project is ask the
Project manager who the contact people for various issues are. Then, I
figure out who's actually doing the work (the PM refers me to the lead
programmer, who then refers me to the appropriate programmer). And I
batch my questions, and find out who wrote the specs, and get original
copies, and all these things. I make sure that all these people know that
I care, and I ask them to review whatever I wrote using them as a SME.
Then, the NEXT time the PM is working on a project, I go right over and
ask to be included in the development meetings - maybe not the first one,
but as the product evolves, I want to be there. If he forgets me, I
forgive him, but carefully walk him through what I need and WHY I've asked
to be included. I make sure that the programmer(s) know that I'm part of
the project.
We product hardware and associated software, so there is a dedicated
installer for each project. When he installs the prototype, I hang out in
the demo room with a camera, and ask lots of questions. Then I go back to
my desk, link into the prototype, and take lots of screen shots. I also
tape lots of these conversations, and I actually transcribe the ones that
are valuable.
They get used to you, after a while.
Part of their job is to get you the information you need. Use the PM as
your leverage point, be as flexible as possible in scheduling (I try to
have a couple of projects going at one time, so that I always have
something I can pick up on), and be sweetly persistent.
I guess the most important thing is, when you're starting out, NEVER
ACCEPT BEING OVERLOOKED. Be nice about it, but be firm.
ROBOHELP X5: Featuring Word 2003 support, Content Management, Multi-Author
support, PDF and XML support and much more!
TRY IT TODAY at http://www.macromedia.com/go/techwrl
WEBWORKS FINALDRAFT: New! Document review system for Word and FrameMaker
authors. Automatic browser-based drafts with unlimited reviewers. Full
online discussions -- no Web server needed! http://www.webworks.com/techwr-l
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.
