How to speed up PC diagnosis and repair

Not only do IT pros face tight budgets, personnel cutbacks, and more stringent purchasing agents, but they must safeguard their departments from wasted time and money. So it has become extremely important to keep PC systems in good running order and to attack failures with a well-coordinated troubleshooting process.


Proper troubleshooting can help cut costs and repair times, and having an effective recovery plan can lead you through times of crisis quickly, capably, and without too many headaches.

The most important thing to do in any troubleshooting situation is follow a set of basic guidelines. You need to know what to do when exposed to people of varying technical skills and machinery of varying capabilities.

Often, end users have no clue what the problem is, but IT pros know that complaints about "my computer's running slow" could be pointing to any of a vast number of problems. To reduce the time required for closing each trouble ticket and improving your overall efficiency, here is a simple troubleshooting method you can adopt.

Think like your doctor
Physicians know patients can't always discern what's wrong, which is why the patient is seeking doctoral expertise. Similarly, users expect IT pros to know what's wrong with a computer; they get paid to fix problems quickly and efficiently. Whether you're dealing with a single computer or the network for a major corporation, there are four steps you need to take to ensure that you are not overlooking obvious problems or hidden solutions.

  • Subjective approach--The first thing your doctor asks is usually something like, "So, what seems to be the trouble?" After asking your end user what the problem is, you need to carefully analyse the response. This tests your ability to quickly assess a person's technical skill and truthfulness. Many end users may exaggerate or understate what the problem is, so it's your job to figure out if what they're saying is valid.
  • Objective approach--Next, make your own observations of what's wrong. Just as a doctor is trained to see warning signs the average person doesn't, you must make your own objective conclusions, despite any guesses or assumptions the end user might have.
  • The assessment--You'll then need to form the most logical conclusion by combining the observations made in steps one and two. You may have more than one guess as to what the problem may be, but go with the one most likely to have caused the problem.
  • The plan--It's time to tackle the problem head-on in a style that will save you time, money, and some bit of mental sanity. As you begin what could be a lengthy trial-and-error process, keep in mind that there are a number of tools and software available which can make this process easier.

    What's in your doctor's kit?
    Just as a doctor can't serve a patient without proper instruments, all the technical knowledge in the world is useless if you don't have the tools to apply it in a focused troubleshooting effort. Even though you may have correctly assessed the situation and pinpointed the problem, you need to have the right tools available to provide the proper resolution.

    Your "doctor's kit" should include physical repair tools, such as screwdrivers and multimeters, and also some good diagnostic software, such as Norton SystemWorks 2002 Professional Edition, PartitionMagic, and BCM Diagnostics.

    TechRepublic is the online community and information resource for all IT professionals, from support staff to executives. We offer in-depth technical articles written for IT professionals by IT professionals. In addition to articles on everything from Windows to e-mail to firewalls, we offer IT industry analysis, downloads, management tips, discussion forums, and e-newsletters.

    ©2003 TechRepublic, Inc.

  • Advertisement

    Talkback 0 comments

    Sponsored content

    Power Centre - Content from our premier sponsors

    Blogs

    Tags

    Back to top

    Featured