IT Support & Networks · Unit 2 of 8
Unit 2: The troubleshooting method
A professional six-step method, asking the right questions, isolating the cause, and documenting so problems stay fixed.
Opens the first lesson of this unit in IT Support & Networks. Every lesson is open from the start.
Lesson 1: Six steps that solve almost anything
Goal: Use the standard troubleshooting method in order.
Good IT technicians are not magicians who know every error message. They follow a method, so they can solve problems they have never seen before. The six-step version below is widely taught, including in the CompTIA A+ certification for IT support.
- Identify the problem. Ask questions, find out what changed, and try to see or reproduce the problem yourself.
- Form a theory of the probable cause. Start with the simple, obvious causes first.
- Test the theory. If it is confirmed, move on. If not, form a new theory, or escalate to someone more senior.
- Make a plan and carry it out. Consider side effects, back up data first if anything could be lost, and fix it.
- Verify it works fully, and put measures in place to stop it happening again.
- Document what you found, what you did and the outcome.
Worked example: the six steps in action
Ticket: "The receptionist's computer can't print."
- Identify: you ask questions. It worked yesterday. Other people can print. There is no error message. The print queue shows three stuck jobs.
- Theory: a stuck job is blocking the queue.
- Test: you cancel the stuck jobs and send a test page. It prints, so the theory is confirmed.
- Plan and fix: it is already fixed. You restart the print service so nothing else is stuck.
- Verify: the receptionist prints her real document. You set the printer to show an alert when a job fails.
- Document: "Stuck jobs in queue; cleared and restarted print spooler; user confirmed."
- Troubleshooting method
- A step-by-step process for finding and fixing problems systematically.
- Escalate
- Pass a problem to someone with more expertise or authority when you cannot solve it.
Remember: Identify, theorize, test, fix, verify, document. Simple causes first.
Lesson 2: Asking the right questions
Goal: Gather the facts that point to the cause.
The fastest fixes come from good questions. Users describe symptoms ("the internet is broken"); your questions turn that into facts you can use.
- What exactly happens? Is there an error message? (Ask them to read it out, or take a screenshot.)
- When did it start? Did it ever work?
- What changed? New software, updates, a move, a new device, a password change? This one question solves a huge share of problems.
- Who else is affected? Just them, or everyone?
- Can you show me? Seeing it yourself beats any description.
- What have you already tried?
Use open questions ("What happens when you click Send?") to gather information, and closed questions ("Does the light turn green?") to confirm specific details.
Worked example: "everyone or just me?"
- User: "Email isn't working."
- You: "Is anyone else near you having trouble?" User: "Yes, the whole office."
- That one answer tells you it is not their computer. It is the email service, the network or something shared, so you check the service status instead of their laptop.
Scope (one person or many) is one of the most powerful clues there is.
- Open question
- A question that invites a full answer, such as "What were you doing when it froze?"
- Closed question
- A question with a short answer, such as yes or no, used to confirm a detail.
- Scope
- How widespread a problem is: one user, one device, a whole team or everyone.
Remember: What happens, since when, what changed, who else, show me.
Lesson 3: Isolate the cause: simple first, one change at a time
Goal: Narrow down a problem by isolating variables.
Once you have facts, narrow the problem down. Two habits do most of the work.
Check the simple things first. Is it plugged in and switched on? Is the cable firmly connected? Is the right input selected on the monitor? Is the volume up? Is Wi-Fi on? It is not insulting to check; experienced technicians check these first because they are so often the answer.
Change one thing at a time. If you change three things at once and it starts working, you will not know which one fixed it, and you may have broken something else.
Isolate by swapping and comparing. Try a known-good part or a different place:
- Try the mouse on another computer. Works there? The mouse is fine; look at the first computer.
- Try a different cable or power outlet.
- Try a different user account, or a different browser.
- Try another website. If only one site fails, the problem is probably that site, not your connection.
Worked example: no picture on the monitor
- Is the monitor on? Its light is orange, meaning "no signal", so it has power.
- Is the right input selected? It is set to HDMI 2; the cable is in HDMI 1. Switch inputs.
- Picture appears. One simple check, one change, problem solved.
Hands-on lab in the room: Help desk simulator. Work three real-style tickets from start to finish. Each step asks what a professional would do next.
- Isolate
- Narrow a problem down by testing one part or variable at a time.
- Known-good
- A part or setup you know works, used for comparison.
Remember: Check the simple stuff first, change one thing at a time, and swap in known-good parts.
Lesson 4: Restart, document and escalate
Goal: Know why restarting works, write useful notes and escalate well.
Why "have you tried turning it off and on again?" works. A restart clears RAM, stops stuck programs, resets network connections and finishes installing updates. Many problems are temporary states, and a restart wipes them away. It is a legitimate step, not a brush-off. If the problem keeps coming back, though, the restart is hiding a real cause that still needs finding.
Documenting means writing down what happened so you, or a teammate, can fix it faster next time. A good note covers: the symptom, the cause, what you did and how it turned out.
| Weak note | Useful note |
|---|---|
| "Fixed it." | "Outlook would not open for J. Rivera (Sales). Cause: corrupted add-in after update. Disabled the add-in, Outlook opens. Watching for others with the same update." |
Escalating means passing the problem to someone with more expertise or access. It is the right call when you have tried reasonable steps, when the fix needs permissions you do not have, or when the problem affects many people. A good escalation includes everything you have learned, so the next person does not start from zero.
Worked example: a good escalation
Escalating to network team.
Issue: 2nd floor (about 20 users) lost internet at 9:40.
Checked: 1st floor fine; 2nd floor PCs get 169.254.x.x addresses (no DHCP); 2nd-floor switch lights are off.
Suspect: switch lost power or failed.
Users told: working on it, update by 10:15.Remember: Restarting is legitimate but not a cure for repeat problems. Write notes a teammate could act on.
Practise it in IT Support & Networks
Each lesson ends with three questions that check you can use the idea, not just recognise it. Wrong answers explain why and come back in Review. The unit ends with a 6-question quiz; pass it with 80% or more to master the unit. Hands-on lab: Help desk simulator.
Every lesson is free: no ads, no lives and no paywall.