Troubleshooting Routine for Kids
When something goes wrong on the computer, it can feel frustrating. But most problems have simple solutions — you just need a plan.
This page teaches a step-by-step routine that works for almost any computer problem. Facilitators can introduce it as early as Week 2, and learners can refer back to it anytime.
The 5-Step Troubleshooting Routine
Step 1: Stop and Look
Don't click anything else. Just look at the screen.
Ask yourself:
- What do I see?
- What changed?
- Is there an error message?
Sometimes just looking carefully shows you exactly what happened.
Step 2: Think Back
Ask yourself:
- What did I just click or type?
- What was I trying to do?
- Did anything unexpected happen?
Tracing your steps backwards often reveals the problem.
Step 3: Try One Small Thing
Pick one thing to try:
- Press Ctrl+Z (Undo) to reverse the last action
- Close the window or tab and reopen it
- Click somewhere else on the screen to deselect
- Scroll up or down to find what you lost
- Check if the right app or tab is in front
Important: Only change one thing at a time. Then check if it worked before trying something else.
Step 4: Try Again or Try Differently
If the first thing didn't work:
- Try a different approach
- Reread the instructions
- Check if you missed a step
- Look at the screen carefully for clues
Most problems take two or three tries to solve. That's normal.
Step 5: Ask for Help
If you've tried a few things and you're still stuck, ask an adult or a partner for help.
When you ask for help, explain:
- What you were trying to do
- What happened instead
- What you already tried
Asking for help is smart, not weak. Even professional programmers ask for help every day.
Common Problems and Quick Fixes
Here are solutions to the most common problems learners encounter:
| Problem | Quick Fix |
|---|---|
| "I can't find my file!" | Open File Explorer / Finder and check your My Projects folder. Try the search bar if you remember the file name. |
| "My work disappeared!" | Press Ctrl+Z (Undo) to bring it back. If the app closed, reopen it — some apps auto-recover. |
| "The screen looks weird" | You might have zoomed in or out. Try Ctrl+0 (zero) to reset zoom. |
| "I accidentally closed my tab" | Press Ctrl+Shift+T to reopen the last closed tab in most browsers. |
| "The page isn't loading" | Check the internet connection. Try refreshing with F5 or Ctrl+R. Wait a moment and try again. |
| "I can't type anything" | Click inside the text area first — the cursor needs to be placed before you can type. |
| "The app is frozen" | Wait 10 seconds. If it's still frozen, try closing it with the X button. If that doesn't work, ask an adult. |
| "A popup appeared" | Don't click anything in the popup. Close it with the X, or close the browser tab. Tell an adult if it seems suspicious. |
| "I saved my file but I can't find it" | Check the Downloads folder — that's where many files go by default. Also check the Desktop. |
| "Something looks wrong with my Scratch project" | Use the Debugging Checklist: What should happen? What actually happens? Change one thing and test again. |
The Troubleshooting Mindset
Good troubleshooters share a few habits:
- They stay calm. Getting upset makes it harder to think clearly.
- They observe before acting. Looking at the screen tells you a lot.
- They change one thing at a time. This way you know what actually fixed the problem.
- They're not embarrassed to ask for help. Everyone gets stuck sometimes.
- They learn from problems. Next time the same thing happens, they'll know what to do.
Introduce this routine around Week 2 when learners start interacting with apps and windows. Refer back to it whenever a learner gets stuck. Over time, learners will start using it on their own — that's one of the best signs of growing independence.
Consider printing the 5-Step Routine and posting it near the computer as a visual reminder.
Printable Version
You can copy the 5-Step Routine below onto a card or poster:
🔍 Stop and Look — What do I see?
🧠 Think Back — What did I just do?
🔧 Try One Thing — Change one thing and check
🔄 Try Again — Try a different approach
🙋 Ask for Help — Explain what happened and what you tried
For the full curriculum troubleshooting and debugging approach, see Week 11: The Debugging Lab.