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.
I'm a relatively new tech writer at an engineering company that builds
a specialized type of machine. One of the newer machines has caused
some problems for our customers. A malfunctioning machine typically
exhibits one of five or six general symptoms, but the cause of the
same symptom can differ from machine to machine. Diagnosing the
problem is often complex and regularly requires our field service
engineers and customer support engineers (manning the phones) to refer
customers directly to engineers working in research and development.
I've been asked to develop a troubleshooting guide to help the field
service and customer support people better diagnose and solve the
problems they encounter with this particular type of machine.
Unfortunately, there's very little in the way of "official"
documentation for dealing with and fixing properly-diagnosed problems.
Much of the information I need is in the heads of individual
technicians and engineers, and in "unofficial" emails exchanged by
those emails (which I'm currently compiling).
In a nutshell, I need to develop a troubleshooting guide that will
allow its reader to work from a general problem to one of myriad
possible causes (which could be hardware- or software-based) and
appropriate solutions. I'm having some trouble figuring out they best
way to structure this without sacrificing its usefulness. Can any of
you share the approach you took in a similar situation? Or are there
any good articles or books out there you can recommend?
"The atmosphere of the average workplace
is to productivity what flames painted on
the side of a car are to speed."
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l