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:Troubleshooting From:Alexander Von_obert <avobert -at- TWH -dot- MSN -dot- SUB -dot- ORG> Date:Fri, 27 Oct 1995 19:03:00 +0200
Hello Elizabeth,
* Antwort auf eine Nachricht von elizabeth_huth -at- gilbarco -dot- com an All am 23.10.95
ee> I'm working on a hardware service manual that will include a
ee> Troubleshooting
ee> section. I am interested to learn how others organize this
ee> section.
I like to do troubleshooting a bit different from your ideas:
- First, I offer some measures to do before checking *anything*:
All screws fastened, all connectors settled...
- Then, I prefer the ten most often needed troubleshooting tips.
- If this doesn't help, I start with conventional troubleshooting.
This way, I have the most promising help in front, where even less educated
personel might find it. This is my excuse to write on a higher level for the
rest of the manual: Don't touch anything if you don't understand what I'm
writing about.
Greetings from Germany,
Alexander
--
|Fidonet: Alexander Von_obert 2:2490/1719
|Internet: avobert -at- twh -dot- msn -dot- sub -dot- org
| Standard disclaimer: The views of this user are strictly his own.
| From TechWriter's Home, Nuernberg Germany
| phone 49+911+591530, FIDOnet 2:2490/1719
