One of my favorite parts of my job is troubleshooting. I enjoy troubleshooting issues for users, and I enjoy helping my coworkers troubleshoot issues they encounter. There’s just something satisfying about seeing a mysterious problem and picking it apart until you find the cause.
As a result, people sometimes ask me how to get better at troubleshooting. It’s a hard skill to explain — sometimes it feels like I just know the correct solution to a problem, and sometimes it feels like I’m just intuiting where the issue lies. Those aren’t really helpful to someone who wants to improve, and the truth is that I didn’t walk into this job with all of the answers or intuition I have today. So where does it come from?
One key that I realized is that to be good at troubleshooting, you have to be curious. Specifically, you have to ask questions (either literally asking another person or just asking yourself as a step in the process) with the intent to learn, not just the intent to get an answer for the one problem you are currently facing. Whether you’re getting help or you’re eavesdropping on someone else who’s troubleshooting an issue (also a great way to learn!), here are things to consider:
- How did someone else break down the issue I’m looking at and approach or investigate it?
- What is the general subject underlying this issue, and what information can I brush up on (with further reading, classes, conversations with experts) that will help me solve an issue related to that subject later on?
- What keywords (error messages, feature names, descriptions of the problem) can I use to search for past occurrences of this issue?
- What tools do I have access to that could possibly give me more information about the problem that underlies this issue?
A lot of the time, my troubleshooting is a lot of trial and error. I might pop open my browser console to discover it’s completely blank, and later find out that my terminal could have given me more useful information. Or I’ll be absolutely sure I’m encountering a theme bug, only to discover that the problem is solved by changing a widget. That’s ok.
Learning to troubleshoot is learning how to approach a problem, and going down the wrong path is bound to happen in that process. But the more practice you get, and the more techniques and information you learn, the better you’ll become at identifying the likely cause of any given issue and figuring out how to resolve it — without having to rely on someone else handing you the right answer.