The calm, repeatable way to troubleshoot almost anything

1. Write down the symptom

Record the exact error, time, affected device, and what you were doing. Take a photo or screenshot. "Email is broken" is vague; "Outlook asks for a password every time, but webmail works" is actionable.

2. Find the scope

• Does it affect one person or everyone?
• One device or every device?
• One website or the whole internet?
• Wi-Fi only, or wired connections too?

Test from a second device or account when possible. A single-device issue usually lives on that device. A company-wide issue points toward the network, provider, or shared service.

3. Ask what changed

Check for a recent update, new application, moved cable, password change, power outage, or vendor maintenance. Do not immediately uninstall security tools or updates; first establish whether timing and symptoms actually connect.

4. Check the simple physical layer

Confirm power, cable seating, indicator lights, available disk space, and that airplane mode is off. For network gear, photograph cable positions before moving anything. Avoid factory-reset buttons: they erase configuration and often turn a small problem into an outage.

5. Restart the smallest affected thing

Save work, then restart the affected app. Next restart the device. Restart shared network equipment only when everyone has been warned and you know how it should reconnect. Never repeatedly power-cycle a failing drive.

6. Change one thing, then test

Use the safest reversible test first. Try another browser, cable, port, or known-good device. Record what happened. If you change five things at once, you will not know what fixed it—or what caused the next problem.

7. Know when to escalate

Stop when the next step risks data loss, requires administrator credentials you do not understand, involves production servers or line-of-business databases, or the problem keeps returning. Give the technician your notes, screenshots, timeline, and tests. That history saves paid troubleshooting time.