It would be hard to believe that any user of technology has not faced this question at one time or another. Something stopped doing what it is supposed to do, and we’re wondering whether to raise the white flag or try to fix it. In many cases, the answer is a long way from clear-cut. Part of us wants to take a crack at it. That same part of us doesn’t want to come across as less than knowledgeable. Also, that same part of us might not want to wait for someone to come in and fix it. After all, we are very busy.
On the other hand, just as a horse can perceive a nervous rider, technology issues often have an uncanny ability to go from bad to worse when someone with just a little knowledge goes “under the hood.” But depending on your skill level, there are certain things you might be able to do in order to try to get things up and running again.
I don’t want to insult anybody’s intelligence by saying the first step is to reboot. You knew that, didn’t you? Similarly, the next step is to make your best effort to isolate the problem. Very often, this involves plugging in different devices, checking the efficacy of software running on the same system, and similar commonsense efforts to drill down on the glitch. Even if you’re not actually able to “right the ship,” your channel partner or tech support person will appreciate your diligence, as well as any information that you can provide to help them correct the matter more quickly.
Once you get past this point, things get a bit more dicey, and your actual technology expertise becomes more crucial. Because now we enter the realm of checking configurations, and perhaps even making changes to what you find. Do this correctly and you’re a winner. Do this incorrectly, and you might cause bigger problems than the one you started with. And if you make such changes on the network itself, you might impact a lot more people than just your self. So tread carefully. Always take copious notes on any changes that you make. Right down the configuration that was in place before you changed it, and also write down the changes that you made. Again, be sure to write it down. Don’t trust it to memory because once you start tinkering, it’s amazing how quickly those details will flee from your mind.
Anything beyond this level of response probably involves a screwdriver. Even if you really do know what you’re doing, looking up any corresponding warranties is a necessary first step. And with warranties or, in essence, insurance policies, it often doesn’t take a whole lot to invalidate them. So key things to consider here, aside from your own expertise, include the status of the warranty, (assuming it’s under warranty), the complexity of the device, the replacement cost of the device, and the mission criticality of the device. Though if the devices networking anyway, that mission criticality thing kind of slides down a notch.
All of these elements will help you select the point at which to engage help. But keep in mind that though tech-support people do appreciate those who can take care of themselves, they also tend to appreciate people who refrain from making more work for them. So be a responsible colleague, but don’t feel an overwhelming urge to be a hero, either!