Troubleshooting Techniques: Introduction

When something breaks somebody needs to fix it and when they do gratitude is typically sent in that person’s direction. The very nature of engineering is to create new things. During this process, the creations are inevitably passed around to different people during design, prototyping, testing, and manufacturing phases. As products progress through these steps (or whatever sequence is used in your specific situation), it is rare that everything goes smoothly.

As such, something will break along the way, somebody will receive accolades for fixing them, and those kudos will appear on that persons performance evaluation. It might as well be you. Few things enhance a work reputation like being the person who fixes broken stuff. This series examines the essential attributes of successful troubleshooting as well as provides a common set of steps to increase the odds of finding a solution as quickly as possible.

Advertisements

12 Responses to “Troubleshooting Techniques: Introduction”

  1. Pete Johnson Says:

    Jed Daniels over at http://www.itsnotthenetwork.com has a nice extension to some of the ideas in this guide here:

    http://www.itsnotthenetwork.com/how-to-troubleshoot/

    His advice: DEFINE THE PROBLEM FIRST. That’s a great point. Unless everyone agrees on what it is you are trying to solve, you’re bound to have trouble when you think you’ve fixed it and others don’t share that opinion.

  2. Nerd Guru » Blog Archive » Troubleshooting Techniques: Wrath of Khan Anecdote Says:

    […] Troubleshooting Techniques: Introduction (older) (newer) Happy Holidays! […]

  3. Nerd Guru » Blog Archive » Troubleshooting Techniques: Knowledge, Access, and Creativity Says:

    […] Introduction […]

  4. Nerd Guru » Blog Archive » Troubleshooting Techniques: Step 1 - Were all the instructions followed correctly? Says:

    […] Introduction […]

  5. Nerd Guru » Blog Archive » Troubleshooting Techniques: Step 2 - Is this happening here or is it happening everywhere? Says:

    […] Introduction […]

  6. Nerd Guru » Blog Archive » Troubleshooting Techniques: Step 3 - Something changed recently, what is it? Says:

    […] Introduction […]

  7. Nerd Guru » Blog Archive » Troubleshooting Techniques: Step 4 - What isn’t broken versus what is? Says:

    […] Introduction […]

  8. Nerd Guru » Blog Archive » Troubleshooting Techniques: Step 5 - It’s fixed, now what? Says:

    […] Introduction […]

  9. Nerd Guru » Blog Archive » Troubleshooting Techniques: Final Thoughts Says:

    […] Introduction […]

  10. Get unstuck by enlisting a moron (me) | Nerd Guru Says:

    […] Despite my lack of knowledge, I encouraged her to explain to me what the problem was. She knows as much about Java programming as I do about making curtains, but I’ve found over the years that by trying to explain a problem to somebody with no prior knowledge of the material, it forces you to think through your steps more precisely. Often, you discover your own mistake with a step you didn’t realize you missed because your expertise clouded your troubleshooting approach. […]

  11. Pressure Makes Diamonds | Nerd Guru Says:

    […] my line of work that usually means meeting a deadline, troubleshooting some big problem that’s broken, or presenting a new and perhaps controversial idea to the people in charge. I came […]

  12. Jed Daniels . com|net|org » Blog Archive » How to Troubleshoot Says:

    […] Nerd Guru has an excellent Introduction/Refresher on Troubleshooting and it happens to be an entertaining read as well (with a site named “Nerd Guru” would […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: