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: how to describe help From:Jonathan Price <jonprice -at- AOL -dot- COM> Date:Mon, 11 Apr 1994 12:19:13 EDT
Yes, Caryn, I think you're right: guys just don't like to ask for help. But
overall, most users have been burned when they tried to get help; they are
willing to try two, maybe three times, and if they don't find what they need,
they never go back-even when you improve it in the next version. Make sure
managers know this when they suggest a "gradual approach" offering only
beginner stuff this version, and more details later. The intermediate user
will try help now, find it lacking, and never, never go back. Result: the
company has lost all that investment in help, and still has to answer the
hotline for that customer.
But to go back to your idea about us guys not wanting to ask for help:
perhaps you could use a name that Rich Coulombre thought of for the book we
did on FileMaker: Under the Hood. Or Fine-Tuning. Or: Power Tricks and
One woman I know said: "I know why DOS users keep talking about power. If
you have square wheels, you need a lot of power to move."
918 La Senda, NW
Albuquerque, NM 87107