Troubleshooting

Explore & Discover

Ever gotten a blue screen, a frozen app, or a Wi-Fi connection that just won't cooperate? Troubleshooting is the skill that lets you figure out *what went wrong* instead of just giving up and restarting. Spend time this week exploring how tech breaks — watch YouTube channels like Linus Tech Tips or TechQuickie for short explainer videos on common computer problems. Check out r/techsupport on Reddit to see how real people describe and solve issues every day. Notice how the best answers always start with questions: "When did it start?" and "What changed?" You're ready for the next step when you can name three common tech problems and describe what causes each one.

Learn the Basics

Good troubleshooters use a method, not just guessing. Learn the four-step process: (1) Identify the problem — write down exactly what's happening. (2) Research causes — Google the exact error message in quotes. (3) Test one fix at a time — changing multiple things at once means you won't know what worked. (4) Document what you did — so you can repeat it or undo it. Practice this on Khan Academy's "Internet 101" module or the free Google IT Support Certificate intro on Coursera. Try troubleshooting something small — maybe your phone's battery draining fast or slow Wi-Fi. You're ready for the next step when you can walk through all four steps on a real problem you've seen.

Build Your First Project

Pick one broken or misbehaving device in your home and run a full troubleshoot on it using your four-step method. Write everything down: the symptoms, what you searched, what you tried, and what happened. Common starter projects — a printer that won't connect, a game controller with sticky inputs, or Bluetooth headphones that drop audio. Use iFixit.com to find repair guides and learn how to safely open devices if needed. YouTube's "How to fix [device name]" searches are your best friend here. Keep a troubleshooting log in a notebook or Google Doc. You're ready for the next step when you've completed one full troubleshoot cycle and written down your results.

Experiment & Iterate

Now try troubleshooting something harder — a software bug, a network problem, or a device with multiple possible causes. Practice ruling things out systematically: start with the simplest fix (restart, update, re-plug), then move to more complex ones. Learn to read error logs — on Windows, open Event Viewer; on Mac, use Console app. Search the specific error codes you find. Try to intentionally break something in a safe way (like disabling a browser extension) and then fix it. You're ready for the next step when you can explain why you tried each fix in the order you did, not just what you tried.

Advanced Techniques

Level up to network and performance troubleshooting. Learn to use built-in tools: ping and tracert (Windows) or traceroute (Mac/Linux) in the command line to diagnose internet issues. Use Task Manager (Windows) or Activity Monitor (Mac) to find which app is eating your CPU or RAM. Explore Wireshark — a free, powerful network analyzer used by real IT pros — just to see what traffic looks like on your network. Utah Valley University and Salt Lake Community College post free IT videos online — search for their open courseware. You're ready for the next step when you can run a ping test, read the results, and explain what they mean.

Final Project Showcase

Create a "Troubleshooting Playbook" — a guide you write yourself for the five most common tech problems you've encountered or researched. Each entry should include: what the problem looks like, three likely causes, step-by-step fixes in order from easiest to hardest, and how to prevent it. Make it something a younger sibling could follow. Share it as a Google Doc, a simple website using Google Sites, or print it out and give it to a family member who struggles with tech. Bonus: offer to help one person in your household with a real tech problem using your playbook. You're ready for the next step when your playbook is complete and you've used it to help someone else.