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: No one reads the manuals From:AlQuin <cbon -at- WXS -dot- NL> Date:Tue, 22 Dec 1998 23:11:48 +0100
On 22-12-1998 19:34 Suzanne Gerrior wrote:
>I don't want to beat a dead horse here, but I need some information - fast!
>I was just in a meeting with my boss who made this very innocent comment to
>me and my co-worker:
>"It must be very frustrating to be in a profession where no one reads what
>I have searched the archives and not found the type of info that I'm looking
>for. Can anyone tell me if they know "for a fact" that user's read the
>documentation (skimming is included as reading). By this I mean have you
>done a usability test, have you talked to customers. Does anyone have facts
>that I can use to back up my belief that user's do read the manuals.
My users read manuals when they NEED them: when something went wrong or
something doesn't work as expected.
That's why I crusade to design processes and products into such a
self-evident result, it can only be used as intended. Design manuals as a
In my practice this works best.
Kees de Bondt
* Occasionally, things really do work right (Murphy's law 2)