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.
Greetings all, decloaking from usual lurk mode to pose the question "How
do I convince my company that creating/distributing/maintaining a
troubleshooting guide to our software is a good idea?"
Believe it or not, certain influential people at my co. see a
troubleshooting guide as an airing of our weak points, and refuse to do
so because they say it'll get into the hands of our competitors who will
use them against us in a sales shootout. (whew, taking breath at this
point.)
I say posh! Why not help the user help him/herself? If a competitor holds
up these fixes as "weaknesses", what then is s/he hiding about his/her
product? Please reply privately your positive and negative experiences.
Thanks.
P.S. The question at this point is NOT how to create or distribute said
troubleshooting.
Kristy Lantz Astry
Columbine JDS
kastry -at- cjds -dot- com
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
