IT Service Negotiation: Six Steps to Diffuse Awkward Situations


When you work in an IT service capacity, it's not easy to "say no" to a customer request that comes your way. Customer service is all about helping people and solving problems, and that implies an acceptance of any and all requests.  But it doesn't always work that way.  Read on to learn when and how to "say no".

Getting Started: Balancing IT Service Interests

Internal IT services are unique within the world of customer service. Obviously, one primary role of the internal IT organization is to serve and support end-users, and that involves solving problems and filling needs as requested.  But IT services and operations are driven by more than individual end-user demands, they are also subject to company interests, professional ethics and technology best practices.   (Also Read:  Customer Service Principles for IT Management)

For example, systems access would probably be a lot easier for end-users without user-ids and passwords, but doing away with systems security would certainly not be in the best interests of the company. At times, company interests may very well take precedence over end-user interests, and you may need to say "no", even if you are technically capable of fulfilling the request. That said, standards and practices are only one element to consider when faced with a potentially sensitive user request - there are also practical considerations:

  • Do you have the time to complete the request?
  • Do you have the resources to complete the request?
  • Do you have the skills to complete the request?
  • Do you have the authority to agree?
  • What are your prior commitments, and does this request present any conflicts?
  • Is the request within the scope of your responsibilities?

Whenever service requests cannot be fulfilled, action must be taken to minimize the fallout and protect organizational interests.  Here are few suggestions and techniques.....

How to Say No and Minimize Potential Fallout

#1 Don't Alienate, Collaborate

As the questions listed above indicate, at times, despite the natural inclination or actual ability to be helpful, you may need to say "no". When you must refuse an end-user request, you will want to do so without an outright rejection - that serves no purpose and will probably only alienate your end-user, causing them to bypass you in the future or just go over your head. So the trick here is to say "no" without actually using the word.

#2 Consider the Associated Politics

While it may be unpleasant, or even unfair at times, internal politics are a reality in any business, large or small. Before you respond to any service or project request in the negative, you need to consider "who is asking?". Sometimes, you may not be able to "say no", even if "no" is the best response. On the other hand, an unqualified "yes" in these circumstances can also be dangerous, particularly if you really will not be able to fulfill the request. In these circumstances, even if you cannot say "no", the ensuing analysis will still be worthwhile. If you are fully informed and prepared, you can work towards compromise, and seek guidance from your own management. In addition, in consideration of scheduling and resource limitations, every "yes" offered to one request, may very well generate a "no" to another, so you need to be prepared to justify and reschedule your other commitments.

#3 Learn to Listen

If you are to respond properly, it is important that you fully understand the nature and the specifics of the request - does it relate to a service problem, a project already underway, a new project or some other issue? If you refuse the request without a full understanding of its elements and origins, you risk embarrassment at a later date.

#4 Evaluate all the Circumstances

Evaluate the request. Using the questions listed above, you will need to evaluate the request in order to determine whether acceptance and completion is possible (or even mandatory), or to determine whether rejection is in order. Your analysis will need to consider company policies, current priorities, available time, resources, skills and other related issues.

#5 Develop an Action Plan

Based on the nature of the request and your related analysis, you will need to develop an appropriate response, which likely will fit into one of four categories:

- A "yes" (You commit to the request).
- A "no" with an explanation* (I can't complete this request and here's why).
- A compromise (Some alternative to the initial request).
- A referral (The name of an alternative resource for assistance or escalation).

Take Note: If you must refuse the request, you should be ready to justify that decision. In this way, the reasons for the rejection take priority over the rejection itself, placing all parties on equal footing should the rejection be disputed. If you were to just say "no" without an explanation, it would be very difficult to justify and defend your position. In addition, your job is to serve the business and your end-users, if you refuse requests without viable reasons, you will likely not be in your position for very long.

#6 Get Ready to Negotiate and Compromise

Once you have developed your responsive action plan, the hardest part begins .... you have to let your end-user know. How you choose to communicate your response will depend on several factors: the nature of the request (formal or informal), the person making the request, your relationship with that person, the sensitivity of your response, and the culture of your company. You may choose to make your response in person, on the phone, via e-mail, on paper, or some combination thereof. Whatever mechanism you use, you should always follow a few basic techniques:

  • Don't be defensive or overly apologetic. Simply state that you regret that you cannot complete the request at this time, and offer your explanation. (i.e. scheduling conflicts, conflicts with internal policies, conflicts with other plans or projects, etc.) Emphasize the reason, not the rejection.
  • Try and be as positive as possible, focusing on any compromises or alternatives that you can offer.
  • Always leave yourself an opening for a graceful exit. Your end-user may offer an alternative of their own, point out an error in your analysis, or they may react negatively to your response. If necessary, leave yourself a way to "re-think" the matter so that you can seek assistance from your own management before things get ugly. You can accomplish this with a simple statement to the effect of "if you have any questions, or feel that I have misunderstood your request in any way, please let me know". Let the end-user know that you have not shut the door in his/her face.

Continue reading more on this subject in our next article How to Offer Effective Apologies for Customer Service Failures.


About Us- ITtoolkit.com has been around since 2001.  What will you find here?  We have articles (covering a wide range of topics relating to our IT service strategy and project fast tracking methodologies).  We have templates and whitepapers to download.  We have our series of IT management infographics.  And, we have our "Toolkit productivity packages", combining "education and execution" - with time-saving concepts, steps and templates packaged in digital downloads.  Our current Toolkit offerings include the Fast Track Project Toolkit and IT Service Strategy Toolkit.

Learn more about the Service Strategy Toolkit from ITtoolkit.com

ARE YOU READY...?

TO MAKE YOUR I.T. DEPARTMENT MORE VALUED, RESPONSIVE AND RELEVANT?

If you are, then you need the IT Service Strategy Toolkit from ITtoolkit.com! The Toolkit teaches you how to "add value" to IT projects and services -- using our time-saving "service strategy process". It's ready for instant download, filled with 400+ pages of steps, guidelines, practices and templates. Find Out More

Featured Management Topic: Project Fast Tracking

Strategic fast tracking is a streamlined project management process, used to level the playing field when "project problems" get in the way of on-time success. Our informative "fast tracking" article series explains more:

Part 1: What is Strategic Fast Tracking?

Part 2: Evaluating Projects for Fast-Track-Ability

Part 3: Pinpointing Project Priorities

Get an illustrated view of the fast tracking process in the "Step-by-Step to a Fast Tracked Project" infographic.

Articles, Tips & Offers Right to Your Inbox

Sign up for the ITtoolkit.com newsletter and be the first to know about our latest blog articles, templates, white papers, infographics, and special offers.

We won't overload your inbox and we don't share or sell subscriber information. Just enter your email address below.