Home > CA Community > Service Management

CA Community





This Blog

Service Management

The importance of Service Management from building a strategy to applying best practices with ITIL is paramount in realizing real world, practical implementations. Learn how you can go from strategy to implementation

Service Management is Valuable Outside of IT as Well!

Published: February 25 2013, 10:14 AM
by Robert Stroud

If your customer is complaining, it can be viewed as a positive sign as they are still a customer. But unless you promptly resolve the situation, they will probably NOT be your customer for long.

I just returned from one of my worst customer service experiences ever-a cruise in the Bahamas. The hot food was cold, the cold food hot, the service staff didn't know how to smile and their idea of a clean room didn't match mine-not to mention that the towels replaced daily were worse than the day before and the room maintenance wasn't completed. Now I realize this reads like a seismic issue, but what really got me was the means to report, monitor and track resolution. Let me explain.

In the case of the food, it was a simple matter of informing the headwaiter who returned minutes later with another cold meal-my guess is they hadn't heard of a microwave. Then, my "chilled" soup arrived warm and I left. Finally, after complaining to management, my room was brought up to an acceptable standard, although the hurricane-like noise from the window to the exit under the door made for many sleepless nights.

What was particularly frustrating was that this organization has a reputation for delivering exceptional customer service. That's one reason why I chose it. But after a number of less-than-satisfying visits to customer service, I gave up. Ironically, when I departed I was asked if I "enjoyed my stay." I replied "No" and was promptly told to complete the online survey as they had no capabilities for verbal or written complaints - "that had to be dealt with at HQ."

My impression here is a deep-seated seismic problem with the organization-stemming from its culture and lack of structure, processes and effective tools to ensure customer delight.

I mentioned this experience to a marketing VP at a global manufacturer, who was sitting next to me on a flight to an industry outsourcing conference where I was speaking. He said his organization was experiencing similar customer service challenges and that a number of customer satisfaction issues were recently escalated to him. He also said these issues were hurting sales and that myriad challenges-including rapid customer turnover, frequent  production line changes to support a more agile approach, and product changes to meet  customer expectations-were causing quality issues.

To resolve the process, his company's first step was to fully grasp the issues and their impact of quality product delivery, and then determine where the change process should be better automated to relieve the manual burden on the staff. In the interim, he had stepped up quality checks to ensure that immediate purchaser satisfaction issues were resolved. Technology was critical to cost-effective delivery of the product. He leveraged a service management solution from his IT organization for incident tracking, collation and reporting, tracking major customer outages and implications and resolutions. More importantly, the organization leveraged the automated change process to request change and then track it across the estate.

This scenario is not unique.  We see solutions for service management and program management (both agile and waterfall) used extensively outside of IT. And this trend will continue to accelerate, as technology remains critical to the delivery of business value in this world of rapidly accelerating change.

But it's not happening everywhere. A few days after my vacation, I still hadn't received the comment form. So in desperation to provide feedback, I visited the website and submitted an online customer service form detailing my experiences.  I got an immediate reply that my feedback is important and "we will get back to you in 7-10 days."  It's day 7 and no response, but I really don't expect them to follow through.

They had an opportunity to seize the moment, and then didn't. And they lost a customer in the process. So if you're not responsive to your customers, they won't be customers for long.

 

 

By: Robert Stroud
Robert Stroud is vice president of innovation and strategy for Service and Portfolio Management at CA Technologies. Rob is dedicated to the development of industry trends, strategy and communication of industry best practices. Rob is a strong advocate for the governance, security, risk and assurance...
Read More..

3 people have left comments:

Service management actually began outside of It and still lives a vibrant life there! The pioneers are those I cite in my writings and include Levitt, Normann (who wrote first book on subject), Albrecht, and so many more.... If only our It community would embrace this fact more often we might actually get the full spectrum of service management concepts into the traditional ITSM thinking. I tried to help with the Universal Service Management Body of Knowledge.

Posted by: Ian Clayton | February 25, 2013 12:36 PM

Ian, absolutely, I recall 30 years ago when I started in this industry, before ITIL, we were delivering service management and very effectively if I might say and yes it was not in IT.  As mentioned in the blog and by yourself we need to view the full spectrum of Service Management and even if IT is important, its not all about IT.

Posted by: Robert Stroud | February 25, 2013 2:09 PM

Pingback from  Fresh Links Sundae from David Lowe of Actionable ITSM | Actionable ITSM

Posted by: Fresh Links Sundae from David Lowe of Actionable ITSM | Actionable ITSM | March 3, 2013 10:14 AM

Leave a Comment

* An asterisk indicates a required field

* :  

:

* :  

  Submit