Why this matters
Employers in Ghana list "troubleshooting" in almost every IT support advert, and interviewers often test it by describing a problem and asking what you would do. They are not looking for a lucky guess. They want to hear a calm, logical method. Learn it once and you can use it on a laptop, a printer, a router or a phone.
The six steps
- Gather information. Ask the user what happens, when it started, what changed, and whether anyone else has the same problem. Try to see the error yourself. Write down exact error messages.
- Form a theory. Based on the facts, list likely causes, simplest first. Is it plugged in? Is it switched on? Has the password expired?
- Test the theory. Check one cause at a time. If the test shows you were wrong, go back to step 2 with your new knowledge.
- Plan and apply the fix. Think about side effects before you act. Will a restart lose unsaved work? Does the user need to back up first? Then fix it.
- Verify. Check the whole thing works, not just the part you touched. Ask the user to try it. Think about how to stop it happening again.
- Document. Write the problem, cause and fix in the ticket or your log. Next time, you or a colleague will solve it in minutes.