Troubleshooting Techniques: What to do with bad information | Tech, No Babel

Troubleshooting Techniques: What to do with bad information

Listen to the audio:

Join the conversation; call 1-877-763-3246, leave a comment below the video, or hit me up on Twitter (@PaulAlanClif)

On today’s Tech, No Babel: Troubleshooting Techniques: What to do with bad information

Troubleshooting Techniques: What to do with bad information

How to know you have bad information:
-The problem doesn’t make sense.
-Fixes don’t seem to work
-The piece doesn’t normally break this way
-The symptoms seem odd

[tweet “Troubleshooting can sometimes be hard, but when you get the wrong information, it’s much harder. Here’s how to fix that:”]

How to clear up bad information:
-Ask about the location of the gear (is it close, is it in a well-lit area?).
-Ask for a description of the problematic piece, including any displays, or UI.
-Go back to basics, eliminate everything you can from the situation (aka “simple it down”)

Look for anomalies:
-What is present that shouldn’t be?
-What’s missing that should be present?
-What’s it doing that makes some of the information you’re getting wrong?

Design a test to figure out what is happening.
-How can you prove that the information you’re getting is bad?
-If you’re talking to someone else, how can you help them save face, while getting the right information?

For more, watch the video above.

If you’d like to chip in a few bucks, anything you do is appreciated. Just click this link to donate.

About this show:

If you do video or graphic design to advance your church’s mission, this show is for you.

How to Subscribe to the show (for free):

For more questions, comments, or snide remarks, comment below or contact me at:
Facebook or Twitter
More video can be found on YouTube.com
Also check out my Google+ page

Comments are closed.