Special Series: The IT Agenda
F E A T U R E  
11 Questions to Help You Select the Best Service & Support Provider

  April 15, 2002
  By Dave Molta

  >> continued from previous page

Executive Summary

TOC Issue TOC
Printer Print full article
Printer Print this page
Printer Download as PDF
E-Mail E-Mail this URL
 
  In this article
arrow
Executive Summary
arrow
How To Criticize Constructively
A provider's poor performance can make you look bad to your users and superiors alike. Here are some tips for the fine art of dealing with subpar service.

• Establish expectations based on the technology's maturity and complexity.

• Get the most from your SLA by measuring and documenting performance.

• Recognize that dealing with poor performance is largely a personality issue. Passiveness rarely works, but beware of crossing the line from assertiveness to aggressiveness.

• Know how and when to escalate. If your initial contacts can solve the problem, let them. Be prepared to follow through on an escalation if complaints aren't enough to resolve the dispute.

• Use counsel judiciously. Develop a working relationship with your legal department, but leave plenty of time for your attorneys to solve the problem.

How To Criticize Constructively

Writing a complaint letter that generates a satisfactory response is as much an art as it is a science. Here are some guidelines that may increase the likelihood of a quick answer:

• Keep the letter concise and to the point. Resist the temptation to provide every last detail.

• Try to find something nice to say about the provider and your past working relationship. That sets a positive tone.

• Focus on linking your complaint to the provider's mission, emphasizing how you feel it is your obligation to point out the inconsistency.

• Assuming the problem doesn't relate to a service representative's behavior, avoid personalizing your complaint. Your dispute is with the provider and its processes, not any single individual.

• Be prepared for the follow-up call and have a clear understanding of the key requirements for the provider to adequately address your concerns.

• Document, document, document. Just as measuring and retaining a history of CPU peaks and troughs are important with server management, so too is building a service-documentation file, aka the paper trail. The file should include memos, letters, server logs, trouble-ticket reports--anything pertaining to the provider. Bottom line: If it's not in writing, it never happened.


start top when all else fails

Valley View, Live!

Research and Reports

Storage Virtualization Guide
May 2012

Network Computing: May 2012

TechWeb Careers