Re: Moving upstream

Subject: Re: Moving upstream
From: Peter Neilson <neilson -at- alltel -dot- net>
To: Beth Agnew <Beth -dot- Agnew -at- senecac -dot- on -dot- ca>
Date: Fri, 19 May 2006 11:09:34 -0400

Beth Agnew wrote:

In a reply on the Troubleshooting? thread, Geoff Hart noted:
"Why leave to chance something you can automate for the
user? For that matter, why not test whether the user created a known
problem after each step, and if so, pop up a note telling them how to
fix it?"

Why not, indeed? These and a hundred other good ideas for making life better
for the user are things best handled at the analysis and design stage,
rather than in documentation. Unfortunately, this upstream position is often
a place where techwriters are not welcome. The few of us who successfully
insinuate ourselves into the design process find that we can make useful and
cost-effective changes that improve the product long before it gets to the
QA or Customer Support Complaint stage.

The sad thing is that so few companies understand that prevention is less
expensive than rehabilitation.

They do understand, but they cannot justify paying mere tech writers
to do that when they already have the plan completed and signed off.
The tech writer comes in later and does the documentation.

Just wondering, how many of you have the opportunity to provide input on
behalf of the user at earlier stages in the development process?

Is there even one among us who has not been tasked with
writing a workaround for a bad design, or been the one
to discover the blocking bug that resulted from a design
failure? Or been told to stop reading the code? Or been
told to stop finding bugs?

WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content delivery. Try it today!.
Doc-To-Help includes a one-click RoboHelp project converter. It's that easy. Watch the demo at

You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-
To unsubscribe send a blank email to techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.


Moving upstream: From: Beth Agnew

Previous by Author: Re: Let's make a difference
Next by Author: Re: Is there a formal name for an inspection process
Previous by Thread: Moving upstream
Next by Thread: RE: Moving upstream

What this post helpful? Share it with friends and colleagues:

Sponsored Ads