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.
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.
Just wondering, how many of you have the opportunity to provide input on
behalf of the user at earlier stages in the development process?
--Beth
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!. http://www.webworks.com/techwr-l
