Re: Culture, or What it means to be a Technical Writer

Subject: Re: Culture, or What it means to be a Technical Writer
From: "Eric J. Ray" <ejray -at- RAYCOMM -dot- COM>
Date: Fri, 8 May 1998 13:32:00 -0600

At 02:59 PM 5/8/98 -0400, you wrote:
>But don't you see, the engineer communicates through the design of the
>product. 1,203 page user manuals result from writers trying to explain what
>engineers have done.
<snip>

And effective user manuals result from writers explaining to users
how users can do what they want to do. From my perspective,
awful manuals usually result from explaining what the product
does and how it does it, while effective manuals--of any length--
result from explaining to users how to accomplish something
that users care about accomplishing.

Eric



*********************************************************
* Eric J. Ray, ejray -at- raycomm -dot- com, http://www.raycomm.com/
* TECHWR-L Listowner, co-author _Mastering HTML 4.0_
* _HTML 4 for Dummies Quick Reference_, and others.
* RayComm, Inc., currently accepting contract inquiries.




Previous by Author: JOB: Shelton, CT, USA
Next by Author: Interview Questions (deliberately veering from techie vs non-techie...)
Previous by Thread: Re: Culture, or What it means to be a Technical Writer
Next by Thread: Re: Culture, or What it means to be a Technical Writer


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

Sponsored Ads


Sponsored Ads