Troubleshooting Methodology

The troubleshooting methodology in full is:

1. Identify the problem
2. Establish a theory of probable cause (question the obvious)
3. Test the theory to determine the cause
4. Establish a plan of action to resolve the problem and implement the solution
5. Verify full system functionality and implement preventive measures
6. Document findings, actions and outcomes

I have simplified this into:

1. Fully Identify
2. Probable Cause (Check obvious!)
3. Test
4. Fix
5. Prevent
6. Document

Tech Toolkit

Every Tech Toolkit should have at the very least a Phillips screwdriver. Here is an example of a toolkit: