Nine Tech Troubleshooting Questions to Ask Yourself


Want the answer to your device's issue? It's time to ask some questions.

No, we're not going to interrogate it. Any time you reach out to others for technical assistance, they always ask you questions to understand the context of what is going on, to narrow down the problem, and to narrow down possible solutions. That ironically begs another question: why not ask those questions yourself?

The following nine questions should cover most issues you would experience, even if not all of them apply to your situation. By answering them, you will be well on your way to getting a resolution, and maybe even one step closer to becoming an IT professional yourself!

The Questions

1. When did this issue start? What were you doing when the issue started?

Has this issue been lingering around for a while, and it has been nothing more than a minor annoyance? Did it suddenly pop up out of nowhere? Maybe the issue was lingering around and recently worsened? Knowing the timing is important, as the root of all technical problems is change. To find out when something could have changed is to pinpoint the root cause.

2. Are there any other users with you experiencing this same issue?

It may take some asking around to find out the answer to this one. If multiple people are affected by the same problem around the same time, it is likely that you, nor your peers, had anything to do with the issue, and you will have to wait until it is resolved by your service provider.

3. Did you make any changes or updates leading up to this issue? If so, what were they?

Similar to the first question, this one asks "What?" rather than "When?" Consider recent modifications that might be related to your problem like software installations and setting changes.

4. Did you notice anything in particular about this that stands out to you? Are there any errors showing or something on your screen to make note of?

This helps fill in any gaps and provide extra details when you bring up the problem you're experiencing for the first time. Sometimes something that seems insignificant could actually provide a clue to crack the puzzle, like an error code or a minor symptom/byproduct that a device is experiencing.

5. Have you consulted any documentation or instructions regarding your issue? If so, what have you reviewed?

It can be tempting to ignore the raw documentation in favor of simply messing around with your device, spontaneously selecting random options in your settings rather than doing the proper research. When you search for documentation related to your device, application, or account, be sure you are getting the most up-to-date, relevant, and most importantly legit stuff. In addition, there are third-party websites out there that may say you should download a sketchy piece of software instead of giving a real solution.

6. What have you tried to resolve this issue?

If you are trying to get to the bottom of your problem to see if you can resolve it yourself before giving in to contacting tech support, it will do them wonders if you keep track of everything you've done. Even if you aren't planning to reach out to someone, it would be wise to at least take a mental note of what you've attempted in case you need to undo something.

7. Have you tried using your device's/application's built-in diagnostic tool(s)?

Believe it or not, there, indeed, could be built-in tools to assist you! For example, if you think your computer's RAM is not functioning properly, you can go into the BIOS and run a memory test. That's just one of several possibilities.

8. What is the model/version/tag/serial number of your device(s), operating system(s), and/or software?

Similar to questions five and six, gathering information will aid you in your quest. When you consult a support page, it may be referencing a specific version or model of something. Looking up such specifics can also reveal known bugs or issues, as well as fixes, for your specific situation.

9. Have you tried updating, restarting, or power cycling your application(s)/device(s)?

Last but definitely not least, there are times when all it takes is testing the simple solutions to avoid any gotchas. You'll be surprised how many things can be fixed or aided by a simple update, reboot, or power cycle. Note that there is a difference between rebooting/restarting and power cycling. Rebooting/restarting involves turning a device off and back on, while power cycling involves physically removing a device's power source and adding it back. If you own a smart TV, try restarting it with your TV remote, then turn it back off, unplug the power cable, plug the power cable back in, and turn the TV back on. You should notice a difference each time it boots up!

Conclusion

...the root of all technical problems is change.

What's great about asking questions is that you don't have to know what the answer is, yet questions help get you started in the right direction to obtaining it. Whether you decide to go all in on resolving your issue or pass it on to someone else, you will have significantly progressed the troubleshooting process and even gained some digital literacy along the way.