True: Say "Show me what 'not working' looks like." to identify a problem., Blame the computer, not the user when troubleshooting., Test one thing at a time to whittle down possibilities., Chips often come loose due to the computer repeatedly heating and cooling., Escalate problems you can't solve or that are time sensitive., After fixing a problem, check to be sure to verify functionality., A good bedside manner builds rapport with users., Asking coworkers for help can build camaraderie., False: "What did you do?" is a good first question when a user reports a problem., Change two or three things at a time when troubleshooting in order to save time., A competent tech doesn't need to consult the manual or company website., Start with the most complex possibility first., Reseating chips means pulling them out of their slots and putting them back in., Keeping your solutions to yourself makes you a more valuable employee., The final step of the troubleshooting process is to verify functionality., No need to document a solution. You'll remember.,

Using the Troubleshooting Best Practice Methodology

Print
Embed

Leaderboard

Visual style

Options

Switch template

Continue editing: ?