IT Support Basics | The Future Market

01

The troubleshooting method

In simple words

Fixing tech is like being a doctor. First you ask "where does it hurt?", then you guess what's wrong, test your guess, fix it, check the patient is OK, and write it in the chart.

Key facts

A simple 6-step method used across IT support:

Step	What you do	Example (printer won't print)
1. Identify the problem	Ask questions, reproduce it, ask "what changed?"	"It worked yesterday. A new laptop was set up today."
2. Guess the likely cause	Start with the simple and common	Wrong printer selected on the new laptop
3. Test the guess	Check without changing too much	Look at the selected printer
4. Plan and fix	Make one change at a time	Select the right printer and set it as default
5. Verify	Make sure it fully works, prevent repeats	Print a test page; add printer setup to the new-laptop checklist
6. Document	Write what happened and the fix	Ticket notes: cause, fix, time taken

Change one thing at a time. If you change five things and it starts working, you don't know which one fixed it.
Back up before risky fixes (reinstalling, resetting, deleting).
Classic first checks: Is it plugged in and turned on? Is it connected? Have you restarted it? Is it affecting one person or everyone?
"Everyone" problems usually point to a shared thing (internet, server, a cloud service outage). "One person" problems usually point to that person's device or account.

Step by step

Ask the user: what exactly happens, when did it start, and what changed? Try to make it happen again.
Make a guess starting with the simple and common causes.
Test the guess without changing too much (for example, look at which printer is selected).
Make one change at a time, and back up first if the fix is risky.
Verify the full fix works and add a prevention step, such as a checklist item.
Write down the cause, fix and time taken in a ticket.
Ask: is it one person or everyone? Everyone usually means something shared (internet, server, cloud service).
Check: your notes could help someone else fix the same problem.

Watch on YouTube

How to troubleshoot (CompTIA A+ 5.1)Professor Messer · YouTube · youtube.com

Videos by other creators on YouTube, for reference. They are not made by or affiliated with The Future Market.

LESSON 01The troubleshooting method

LESSON 01 / ANIMATED LESSON / AI VOICE00:00 / 01:15

Voice

Read the video script

[Host] "Great IT support people aren't magicians. They follow a method."
[Text on screen: Identify, Guess, Test, Fix, Verify, Document] "Identify the problem. Guess the cause. Test it. Fix it. Verify it. Write it down."
[Screen: asking a user, what changed?] "The magic question: what changed? New update, new device, new password?"
[Host] "And one change at a time. Otherwise you'll never know what fixed it."

Try it now

Think of a tech problem you or someone you know had recently. Write it up using the 6 steps, even if you didn't solve it at the time.

ClaudeStuck? Copy a ready-made prompt for Claude

Copy this, open Claude, paste it, and Claude will walk you through the lesson step by step.

For a grown-up: Claude is for adults (18+). Copy this, paste it into Claude, and use the answer to explain the lesson to your child.

I'm learning "IT Support Basics" on The Future Market. Lesson 1: "The troubleshooting method".

What the lesson teaches:
- 1. Identify the problem - Ask questions, reproduce it, ask "what changed?" - "It worked yesterday. A new laptop was set up today."
- 2. Guess the likely cause - Start with the simple and common - Wrong printer selected on the new laptop
- 3. Test the guess - Check without changing too much - Look at the selected printer
- 4. Plan and fix - Make one change at a time - Select the right printer and set it as default
- 5. Verify - Make sure it fully works, prevent repeats - Print a test page; add printer setup to the new-laptop checklist
- 6. Document - Write what happened and the fix - Ticket notes: cause, fix, time taken
- Change one thing at a time. If you change five things and it starts working, you don't know which one fixed it.

The exercise I'm working on:
Think of a tech problem you or someone you know had recently. Write it up using the 6 steps, even if you didn't solve it at the time. ---

I'm stuck. Please:
1. Explain the main idea in plain, simple words with one everyday example.
2. Walk me through the exercise one small step at a time. Ask me what I've done so far before giving the next step.
3. Don't just give me the final answer. Help me do it myself, and check my work when I share it.

I'm a parent helping my child (about 8 years old) with a lesson called "The troubleshooting method" from the course "IT Support Basics".

Here's what the lesson says:
Fixing tech is like being a doctor. First you ask "where does it hurt?", then you guess what's wrong, test your guess, fix it, check the patient is OK, and write it in the chart.

The activity:
Think of a tech problem you or someone you know had recently. Write it up using the 6 steps, even if you didn't solve it at the time. ---

Please explain this so an 8-year-old understands: short sentences, a fun everyday example, and no hard words.
Then give me 3 simple questions I can ask my child to check they understood, and a way to do the activity together, one tiny step at a time.

Open Claude

My notes

I learned this

02