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.
Subject:Re: WinHelp structure comes first? From:Win Day <winday -at- IDIRECT -dot- COM> Date:Sat, 6 Jan 1996 09:52:35 -0500
At 02:53 PM 1/5/96 EST, Tim Altom wrote extensively about the pros and cons
of planning WinHelp projects. He believes planning is important, even
though he states writers would generally prefer to begin writing immediately.
I can't speak specifically about WinHelp projects, having never done one.
But I'm a firm believer in planning EVERY project, in as much detail as
possible, and in updating the plan as often as necessary.
I'm a freelancer with several clients. Planning each project enables me to
give my clients solid cost estimates and schedules. As projects develop and
change (which they always do!), I can easily revise the estimates and
schedules because they were based on solid planning to begin with.
Careful planning also allows me to budget my time between multiple clients
and multiple projects. How else could I manage my efforts?
I can't control much on my clients' end of things. So sometimes schedules
slip because their review cycles take more time than we originally allotted.
But once I know about the slips, I can work them into my plans, and switch
to another project if necessary.
Planning may not be most writers' favourite task. But it is vital to every
project, especially larger ones. Careful planning BEFORE you start writing
will reduce the revision cycle, as you'll catch problems with structure and
organization early. The earlier problems are found and corrected, the less
I highly recommend Hackos's book _Managing Your Documentation Projects_.
She explores the topic of early planning thoroughly.
Email: winday -at- idirect -dot- com