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: Not Being Included From:"John W. Sliger" <jsliger -at- PDQ -dot- NET> Date:Tue, 26 May 1998 20:30:31 -0700
You know, it doesn't bother me at all not being included in the "call list" for a product. I don't want the end user, the customer (or whatever you feel comfortable calling the person putting dishes into the dishwasher, or other product) calling me at all hours of the day and night with troubleshooting questions. That is the job of the repair technician. Rest assured that is exactly what would happen if the technical writer were added to the list. I know, because I've been both the technical writer and the technician for several products.
John W. Sliger
Phone: (281) 353-0567
E-mail: jsliger -at- pdq -dot- net
From: Tracy Boyington [SMTP:tracy_boyington -at- OKVOTECH -dot- ORG]
Sent: Tuesday, May 26, 1998 1:48 PM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: Re: Not Being Included
> 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: (snip)
Ah, but neither does the Human Resources contact (who was listed). :-)
I'd tell Whirlpool how much you liked their documentation and mention
that they must have an excellent technical writing staff. In fact, I
think it would be a good idea for any of us to do this whenever
possible. Why not let companies know that customers notice and
appreciate good technical writing?