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 am now a lone techwriter in a fast-paced start-up. We need everything
done
> - from templates to documents needed to Help to training to document
> numbering system and file naming conventions. Also, we need to keep
informed
> about new technologies.
> I'm not focused right now. I don't know what to tackle first. I know
> day-to-day documents have priority, but what about everything else?
Welcome back. :-)
I'm in your exact position; I've been the lone tech writer at a small
company since this summer. I've been blazing a lot of new trails, and
stamping down existing ones. It can be an awful lot to tackle all at once,
but the good news is that you don't need to. Here's a practical approach...
Templates, processes, etc. are there for only one reason: to make the
process of delivering documentation easier...That's your primary focus. So
focus on that for now. Plan out what docs need to be done first, and what
needs to be done to make that happen.
For example, if your first project is putting together a document, help
system, and training presentation for a new product, you'll need to choose
and acquire tools, create 3 functional (not necessarily perfect) templates,
choose a default style guide, find a blank sheet of paper to use as an
in-progress in-house style guide, and find another blank sheet of paper to
document the process you follow as you create these three deliverables. Now
get down to business--learn the product and write. If you find that you're
getting stuck on a step--like choosing a tool--just start writing in
whatever you have on hand until you decide. Do your best to come up with a
reasonable, repeatable, extensible framework, but really and truly, no one
will care about things like what the files are named. Besides, you can
re-name them later if you absolutely need to.
Everything else can wait 'til later. When the current project is done, a
byproduct of the three docs is the tools, templates, styleguides, and
processes you chose. As new projects and needs come by, just create the
framework as needed...There's no need to have it all done up front.
So take a deep breath and relax... and have fun!
-Sarah
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Check it out! Get some cool freebies when you buy RoboHelp! You'll receive
SnagIt screen capture software and a 10% discount voucher for RoboHelp
Consulting. This special offers expires March 29, 2002.
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.
