Troubleshooting Techniques: Final Thoughts
December 19th, 2007A great bullet point to be able to place on your performance evaluation reads something like this:
“Led the team of people that solved the Tractor Beam escalation, which was costing the company $X per day in schedule slippage, and communicated progress to a wide variety of upper management personnel throughout the troubleshooting process.”
Something like this speaks for itself and shows you to be a valuable commodity as someone who can save the day, setting you apart from the people you are being compared with for rewards. Demonstrating a knack for troubleshooting tends to help you develop a reputation. The more you are successful at it, the more often you will be asked to become involved in them.
While that does come with its pressures it also brings its rewards, the least of which is a strong statement to be able to make to your boss when it is time to pass out raises. It can lead to something more immediate too, like being first in line for personal equipment upgrades. Regardless, performing well under these kinds of circumstances demonstrates you to be a knowledgeable and dependable employee who truly defines grace under pressure.
- Introduction
- Wrath of Khan Anecdote
- Knowledge, Access, and Creativity
- Step 1 - Were all the instructions followed correctly?
- Step 2 - Is this happening here or is it happening everywhere?
- Step 3 - Something changed recently, what is it?
- Step 4 - What isn’t broken versus what is?
- Step 5 - It’s fixed, now what?
- Final Thoughts
Are you kidding me? Take a look at my picture. If I’m not a genuine, bona fide nerd I’m not sure who is. I'm currently employed as the Marketing and Internet Platform Solutions, Portals and Applications Chief Architect at Hewlett Packard (try saying that 5 times fast) and write here about career best practices for techies. Why? Because I wish I'd had this kind of free advice earlier in my own career and now I'm trying to "pay it forward". See more in