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.
First, show them a model topic. Spend a short amount of time with them
(together or individually) describing WHAT you want (i.e., not HOW to do
it). For example, if you have an easy-to-complete topic
outline/template, and if they are at least a little bit familiar with
things like paragraph styles, you might tell them that you want them to
use the correct styles and follow the provided outline. If they are
totally unprepared for that kind of requirement, you might suggest they
just write the procedures in an email to you. Or something in between.
You know them; I don't.
Second, tell them WHEN you need the deliverables (spaced out over the
next week, not all bunched up on day 10). Don't waffle; don't give them
a soft deadline. Explain what the word _deadline_ means in a publication
office, as opposed to what it means in an engineering office. (This is a
Whorfian ambiguity that has sunk many a project; so be explicit).
Third, tell them you are available if they want advice or instructions
on HOW (to organize the information, use the template, whatever), but
that you expect them, as professionals, to meet the deadlines you just
gave them.
Once you've given them their marching orders, relax. Breathe slowly and
deeply. Stock up on whatever gets you in a good mood (chemical,
spiritual, whatever), and pitch in. Write as many of the topics yourself
as you can while you're waiting for the others to start delivering their
drafts. When the drafts do start rolling in, just make the edits
yourself and highlight any point you need technical clarification on.
Finally schedule a short vacation for the day after the deadline.
Dick
julie brodeur wrote:
Hi,
I have a tight deadline coming up (12 working days) in which to coordinate
4 inexperienced writers (they are technical experts, not writers, but are
writing due to the time constraint).
Do any of you have recommendations on how I can make sure I get the
documentation from these "writers" in time for me to format and edit the
data? (And run it past reviewers and update it.)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PC Magazine gives RoboHelp Office 2002 five stars - a perfect score!
"The ultimate developer's tool for designing help systems. A product
no professional help designer should be without." Check out RoboHelp at http://www.ehelp.com/techwr
---
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.