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.
> 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.)
If everyone's reasonably cooperative, here's a simple, friendly, low-tech
way to handle it...
Gather everyone together for a 15-minute meeting pronto. Explain the
situation like you just did, express that you can only do it as a team, and
with pencil & paper in hand, say "let's work out a plan of action." Working
from a list of every topic you need, and ask everyone to start claiming
ownership and giving you a date by which they can have the topic completed.
You're the scribe--just write.
When the list is completed, organize it by person and/or date, and post it
on your door. Make checkmarks as each topic comes in to you, and follow up
that day if one isn't in to you by 3pm. A visible list helps keep everyone
updated...you might even get someone volunteering to take on add'l topics if
theirs took less time than they anticipated.
It may also help to create a quick & dirty "template" for everyone to use.
Forget styles--just make it a quick attempt at structure. For example, for a
command reference guide, you might have listed:
COMMAND NAME
PURPOSE OF COMMAND
PARAMETERS
NOTES
That way, no one has to start from a blank piece of paper, and (hopefully)
no one is tempted to get creative/verbose...There isn't time for that! Then
format & edit as topics come in--it'll help prevent a last-minute crunch on
you.
Good luck and HTH,
Sarah
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.
