"In a troubleshooting situation, I approach it like a maze and work backward. There are usually multiple factors contributing to any one issue, so I try to discern what they are, weigh those out and try to conclude what the potential best solution is. As far as technically speaking, my go-to in many situations, as rudimentary and childish as it may be, is often turn it off and turn it back on. Ha. I know it sounds too simple, but it often works best."

"One horrific day at work, our systems went down entirely. We had no backup for how to check customers out, so I had to dig in the deep recesses of the back room and find the card imprint machines, and we wrote out tickets by hand and made imprints of the cards. I tried all the usual tricks to get our registers up, but couldn't get them to come online as it was a network error. I found the way around it with the handprint cards and then opening the cash drawer with a key."

"I do everything I can to test out the technology before I bring it into the classroom- the day is so packed that we don't have any time to spare on figuring out technology if it acts up. I also always have a backup plan in mind in case the smart board or whatever we're utilizing that day doesn't cooperate, so we don't lose precious learning time."

However, I believe that troubleshooting applies to more than just technology. Problems that occur offline also need troubleshooting as they arise, including figuring out a lesson plan and how it works or doesn't. It's all about working backward to see what issues, if any, may arise in its implementation during a dry run. By preparing in advance and being aware of what issues may come up, I'm able to flush out problems that would have otherwise arisen during the class time.

"I do everything I can to test out the technology before I bring it into the classroom- the day is so packed that we don't have any time to spare on figuring out technology if it acts up. I also always have a backup plan in mind in case the smart board or whatever we're utilizing that day doesn't cooperate, so we don't lose precious learning time."

"We had a major complication in our system and our entire production line shut down. Our network administrator could not be reached so I had to go old-school and manually enter the orders so that my team could continue with production. The entire debacle lasted half of a day, and my system worked well as a placeholder."

"One of our clients called me in a panic, saying that Facebook rejected their ad campaign that we so carefully crafted. I researched on ad policy forums and learned that it was not approved because we did not set our demographic targets to people only over the age of 21. The ad was for a craft beer company, and we did not put into consideration the legal age in most states. Once I was able to narrow down the issue, I tweaked the ad, and it was approved."

Troubleshooting is like reverse engineering - it takes skill, effort, and patience. You have to understand the problem to know how to work backward from it to find a solution.
Knowing how to solve problems with technical equipment is always a solid skill, and a great way to demonstrate your example. Show that you are insightful in your approach.

"Last week, while operating the ultrasound machine, I was receiving a repeated error. I entered in a few different codes, but that didn't solve the issue. I then did a hard reset, removing all power sources. Then, I referred to the online manual for additional suggestions. It took a little time and patience, but I was able to resolve the issue without calling a technician."