Troubleshooting in General
Troubleshooting in General
4 Phases Of Troubleshooting
Discovery
Discover what the root of the problem is with well aimed questions, determine what is
NOT the problem.
Hypothesis
From the answers gathered formulate a Hypothesis, what the problem possibly is.
Testing
Once you have the Hypothesis, you have to test it, so you can determine if you are
right about the problem or not.
Possible more Hypothesis and Testing
Resolution
Your theory has been tried and tested. If you know the solution but not able to solve
it or you dont know it at all, gather all troubleshooted information, the questions
you asked and the given answers and dispatch it to the appropriate second level
unit.
1. Questioning
In order to find out what the problem is you have to ask questions
The question must be case specific, that is constructed for the task at hand
IE The computer wont start:
Is it plugged in?
Is the switch down?
Is the switch on the back of the unit ON?
And so on.
2. Fault Reproduction
Fault reproduction is the same as reconstructing the scene of a crime
The aim is to reconstruct precisely the same actions the user performed prior to the
fault occurrence
This may not be possible, so a plan of similar action to the ones that the user may have
performed would be:
Re-enacted in a specific order
Each stage of the testing would be noted
Any faults found would also be noted
4. Elimination of components
By eliminating a component and re-testing the system it is possible to find a
piece of faulty equipment
By removing one component at a time out of the equation systematically a
problem part can be detected, and a new part replaced
This method however is a time consuming
Points to remember
No fix is complete without confirmation by the customer that the job is done!
Make sure that the problem no longer exists
Ask the user to test the solution and confirm customer satisfaction
If a fix cannot be found then ensure that the customer is aware of your pending
actions