Re: Not Being Included

Subject: Re: Not Being Included
From: George Mena <George -dot- Mena -at- ESSTECH -dot- COM>
Date: Tue, 26 May 1998 13:20:28 -0700

I don't see that listing the tech writer's name adds any value to the
product documentation. Yes, I can see where maybe it would've been
*nice* to add the writer's name and signature to those who'd signed the
form letter, but I think that's more of a marketing idea to have the
signatures than anything else. As a practical matter, it makes better
sense to add a Reader Response card to the documentation and have it
generically addressed to the manager of product documentation. A
separate product registration card should also be in the documentation
and generically addressed to product support.

The one thing we all need to remember is that while we create and
upgrade the product documentation, we don't own the product that we're
documenting: the company does. If *we* have our own products and
create the documentation for it, then we're right to say it's "our"
documentation. But that's not the case here.

> -----Original Message-----
> From: Steve Arrants [SMTP:stephena -at- COMPBEAR -dot- COM]
> Sent: Tuesday, May 26, 1998 11:36 AM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Not Being Included
>
> I don't know how relevent this is to the list....God knows I've raised
> flames about frivolous topics, but....
>
> We bought a new Whirlpool dishwasher over the Memorial Day weekend.
> Included in the plastic Owner's packet (along with coupons and
> samples...)
> was a form letter asking new owner's about how easy it was to set up
> the
> product, were all parts included, was there any damage to the
> dishwasher,
> and how useful was the Use and Care Guide. It *was* nice that
> Whirlpool
> asked. They even included the names and signatures of the folks who
> made
> the dishwasher, along with job titles. But...no technical writer for
> the
> documentation! I mean, even the Human Resource contact was listed,
> but no
> technical writer.
>
> The Use and Care Guide was well-designed and easy to use; I just
> think the
> person responsible should've been included...
>
>
> steve arrants
>
> &^~~~
> Send commands to listserv -at- listserv -dot- okstate -dot- edu (e.g., SIGNOFF
> TECHWR-L)
>




Previous by Author: America v. Japan
Next by Author: Re: Teaching Technical Writing
Previous by Thread: Re: Not Being Included
Next by Thread: Re: Not Being Included


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


Sponsored Ads