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: Convincing a Client He Needs a User Manual From:"Huber, Mike" <mrhuber -at- SOFTWARE -dot- ROCKWELL -dot- COM> Date:Mon, 15 Jun 1998 13:04:00 -0400
What does he propose instead?
You are right that the product is worthless if people don't know how to use
it, but a User Manual is not necessarily the answer.
Go back to all the basic questions. Who is the audience, what level of
expertise, what kind of product...
---
Office:
mike -dot- huber -at- software -dot- rockwell -dot- com
Home:
nax -at- execpc -dot- com
> -----Original Message-----
> From: Gina Hertel [SMTP:Ghertel -at- ALPHA88 -dot- COM]
>
> Hi all. I need to *convince* a client that he needs a User Manual to go
> with an application that my company developed for him.
>
> My whole argument, basically, is that if people don't know how to *use*
> what
> you've developed, it's worthless. Does anyone have any canned language to
> this effect? Does anyone have any stats on the topic? Any help would be
> much appreciated. I'd be happy to post results if you're interested.
>
