CA Community






This Blog

April 2010 - Posts

Customer Service Exists - You Just Need to Look for It

Published: April 23 2010, 03:08 PM | 1 Comment(s)
by Eric Feldman

I recently read the blog by my colleague Rob Stroud "The Lost Art of Real Customer Service - Can We Find It Again?"

I am sure that we all have our war stories, but Rob's piece reminded me of a customer service issue I recently had with two credit card companies. While this is a Service Management blog, the issue is still relevant as credit card issuers (and banks) are among the largest users of technology (and adopters of Service Management processes) anywhere.

The issuer of one of my credit cards recently added a $60.00 annual fee for the use of their card. When I signed up for this card many years ago, I was offered the benefit of "no annual fee for life," yet they imposed this fee to me and many of their customers as they work to "preserve the broad availability of credit" (their words, not mine). Coincidentally, the issuer is a large money center bank and one of the largest recipients of TARP bailout funds.

When I called to complain about the fee and my original benefit from many years in the past, all I received was a canned response from a representative. Their process would not allow for any deviation. I asked to escalate the call to a supervisor. The representative told me that they could not do that for me for this type of call. My excellent credit rating and many years as a customer was of no value to them as I could not even speak to a supervisor. I cancelled the card.

I had a different issue with the 2nd credit card issuer. After receiving my latest statement, I noticed that my cash rewards balance was less than I expected. (I had figured that the total would be enough to pay for most of a new mountain bike that I had my eye on!)

I called the credit card company to ask how they calculated the reward total - perhaps my math was off. The representative told me that it appeared I was correct - that they had shortchanged me - but she needed a supervisor to review and approve any changes.

The supervisor came on and reviewed my account. She then told me how my math was wrong. Apparently, purchases at certain types of businesses did not qualify for the specific cash reward I was expecting, hence the lower amount that was credited to my account.

The supervisor then told me because of the confusion and to thank me for being a customer for many years, she was going to credit my cash rewards balance a discretionary award. And here is the best part - the amount she gave me was more than I was calling about in the first place!

Excellent customer service is not just the province of a consumer-based business. It is also essential in the enterprise IT arena. Just because your "customer" may a captive user, does not mean that they are not entitled to excellent service.

One aspect I have found, however, is that in our rush to automate, control costs, and gain efficiencies, we forget that we must anticipate and allow for process variances - escalations, exceptions, and a degree of flexibility.

After all, Service Management begins with Service. And I am sure your users' expectations are more like my 2nd credit card customer service example, and not the first.

And by the way, I am going to get acquainted with my new Cannondale F5 on the trails real soon!

Share this post:  

 

By: Eric Feldman
Eric Feldman has more than 25 years of experience as a senior architect. With a focus on the areas of service level management and IT asset and financial management, Feldman has specialized in designing and implementing solutions based on CA Service Catalog and CA Service Accounting. He has spoken and...
Read More..

So You Want to Implement ITIL

Published: April 23 2010, 11:00 AM | 4 Comment(s)
by Peter Doherty

Sometimes it is worth revisiting the basics!

I talk to many organisations both here in Australia as well as Asia and the US. I quite often hear people talking about wanting to implement ITIL. This to me is quite strange in that you cannot actually implement ITIL. What you can do is journey along the Service Management path and use ITIL as a guiding map. One of the reasons that it is a journey and you cannot implement ITIL is that it is far from complete. You use it for guidance, not as a definitive document.

So why is there the big push for ITIL? Well IT is actually being forced that way as our customers are demanding higher levels of Services in an environment where there are already high levels of customer dissatisfaction. CIO's are embracing ITIL as a proven set of processes that help focus everything does on the business Services they are providing. In other words, the reason why IT exists.

Now Service Management is a journey and it needs to start somewhere, so where do you start? Even though it seems a simple question, the answer is not so simple and really depends on the organisation. The typical consultants answer; ‘it depends'.

If you think about it logically, a journey needs to have a start, a destination, a map and some way of knowing you have arrived.

Some tips for a successful journey:

Before you start it is essential to understand your pain points and start from there. It is not much use starting with Incident or Problem Management if they are working all right but whenever you introduce a Change to your production environment you only have a 50% chance that you will not affect the business. Spend some time looking at your current processes and rate how well you are doing against benchmarks. There are some self evaluation tools available as well as consultancies that can help with this.

Once you have performed some sort of assessment start looking for things that will give you quick wins. A successful Continuous Service Improvement Program (CSIP) is fuelled by using previous wins to sell the next initiative. You should look to create an environment of perpetual motion.

Now the temptation is always there to try and do everything at once. Resist this at all costs as one of the main reasons that Service Management initiatives fail is through not setting correct expectations from the start.

A CISP will flourish in an environment where the culture supports the drive for service excellence. Culture is driven from the top down and without high level buy in, all your other efforts will never deliver to their full potential. So, senior executives should lead by example. Also from a cultural perspective you should look to develop Service Management champions that spread the word at all levels within the organisation.

Celebrate your successes! IT is all too fond of telling our customers when we are doing poorly and not when we do things well. It is important to benchmark your current position and constantly compare how you are going against your benchmarks. Make your customers aware of what you are doing and publish the improvements you are achieving.

As you start implementing the processes you will notice that best practice is not without it's drawbacks. The first one you notice is the additional administrative overhead of managing the processes. This is why it is essential that you look to automate as much of the process. Use technology to your benefit so as implementing best practice is not onerous from a headcount perspective.

Share this post:  

 

By: Peter Doherty
Peter Doherty is an ITILv3 contributing author and a Principal Consultant for CA. With 25 years IT experience in Service Management as well as Enterprise Network and Systems Management, Peter Doherty is CA’s foremost Service Management evangelist in the Asia Pacific region. His day-to-day responsibility...
Read More..

Why So Many People Screw Up their Incident and Problem Processes

Published: April 21 2010, 09:15 AM | 1 Comment(s)
by Peter Doherty

I have been following a very interesting discussion at the ITSkeptic (http://www.itskeptic.org/we-should-create-problem-record-right-front-incide) and have resisted the LinkedIn group as I think the madness will continue there. Why do I call it madness? Well the Skeptic accused me of oversimplifying things and maybe he is right. I actually often think that I overcomplicate things but I think I get a right blend with some pragmatism thrown in.

I will not go over the same old ground as on that site so maybe I should state my position:

Incident Management's (IM) primary objective is to restore the Service and get the customer up and running. This means that if it is a high impact Incident IM manages the restoration process. Why do I need to state this, as I think it is obvious? Well some people think that Problem Management's charter to find and remove the Root Cause may take precedence over restoring the Service to the customer. I say that this is resoundingly incorrect. Yes there will be instances where diagnostic information is lost, but if we are dealing with a high impact Incident our focus should be customer and business oriented!

So that is my opening argument. For a high impact Incident PM should always become involved, firstly by creating a related Problem record and possibly by playing a coordinating role.

So what happens if as part of the Incident process we discover what the root cause is? Some would argue that we do not need to create a Problem record and in that is something that I see causing havoc. Yes we may have found the root cause BUT it is not within IM's charter to decide whether we want to remove that root cause, which is the charter of PM!  I have seen many organisations that have melded IM and PM and it has always caused them difficulties and kills their metrics as they have a large amount of Incidents left open as the root cause has not been addressed. This has no place in IM.

PM is where we make the decision, if the root cause has not been discovered whether we should be even interested in looking at it. And not just root cause as to most organisations that is just the last event that occurred before the error was detected. What about all the contributing causes that could be very time consuming to discover but may allow us to remedy some of these to reduce the risk of the Incident reoccurring at a much decreased cost?

Whether we actually perform root cause analysis must be determined by weighing up the risk of the Incident occurring again and what the impact will be. If we have a quick workaround in place the impact may be mitigated to such an extent that we do not consider doing further root cause analysis. We have a memory leak that our workaround is to reboot the server, what is the cost of this though and does anybody ever go back to look at this as to whether we really need to find and remove the root cause, How many times to these workarounds just get ingrained in the standard operating procedure?

Whatever the case we should ALWAYS raise a related problem record for a high impact Incident - this is the whole tenant of Reactive Problem Management. Some would argue that the most benefits in Problem Management is removing the root cause for high impact Incidents and this may be the case for organisations who experience many of these (an entire blog topic in itself) but is that true of all organisations - I am not so sure!  It will certainly show from a cost perspective as these high impact Incidents have the potential to actually cost the company money.

It is in proactive Problem Management that we look to perform data mining to look for trends, generally across our lower priority Incidents. Very few organisations do this well - the reason being that few organisations have mature Incident classifications or Configuration that is so important to finding trends. There is also a lack of data mining tools with sufficient intelligence to predict these trends and if there are thy ear generally neglected in place of slick and shiny dashboards that provide value from a marketing perspective. Proactive PM will provide more internal benefits to IT as it will stop the expensive resources doing the same thing over an over again, rarely will it have the visibility of removing the cause of high Impact Incidents.

One of the things that I have said in other blogs is that we often try to be too smart when a simpler solution will do the job, this is the same with PM, don't overcomplicate it.

Share this post:  

 

By: Peter Doherty
Peter Doherty is an ITILv3 contributing author and a Principal Consultant for CA. With 25 years IT experience in Service Management as well as Enterprise Network and Systems Management, Peter Doherty is CA’s foremost Service Management evangelist in the Asia Pacific region. His day-to-day responsibility...
Read More..

The Lost Art of Real Customer Service – Can We Find It Again?

Published: April 21 2010, 07:02 AM | 3 Comment(s)
by Robert Stroud

So I finally did it – I gave in and transitioned from a Blackberry to an iPhone. I so wish that I had not. After using the iPhone for a week in the USA I set off to Europe where immediately upon arrival there was no email delivered to the device. I would not have cared except I was delayed and I needed to mail the event team at the conference. I didn't know what number to call, so after getting no Internet access I eventually called the support service (service desk) and after 1 hour and a few calls I gave up. On a whim, I restarted the device and it suddenly worked!

Now remote support is difficult, I agree, but some empathy would have been nice. And how about transferring to the operator the details of my telephone number that I had entered 3 times? Or knowing basic device configuration information? Etcetera.

This reminded me of the of an airport experience the same week.In the past the airport service desk (gate agents) were empowered to make decisions and ensure customer satisfaction. So on a flight between the US and Europe I was fortunate enough to get an upgrade certificate, well an upgrade email actually. I followed the instructions (very unusually) and called the reservations center and was told I was upgraded and dutifully headed off to the airport for the flight. Upon arrival at the airport the agent could not check me in as the business process had not been upgraded to support the new electronic upgrade process and required a physical upgrade certificate. The escalation process and ultimate reissuing of the ticket took over an hour and it was only the diligence and tenacity of the agent who was on the phone to “head office” that saved my upgrade and some sleep on the flight. I left the counter with admiration for the person serving me and none for the airline (note to self, must change my next overseas flight to a different airline.

IT clearly has become the “front of the front office” and is more often than not the interface that the consumer uses and this requires sound logical interfaces but from a customer service perspective removes the domain knowledge previously held from the individual which in turn requires exceptionally effective knowledge management. This is one of the drivers for social networking and collaboration – the manner in which we are sharing information based on experience – only problem here is that many companies block social media and collaboration tools, which adds to the frustration of the knowledge workers

So the iPhone is working again, email is entering my inbox and I can safari the Web so I am all set – now only an exploding volcano can stop me.

Share this post:  

 

By: Robert Stroud
Robert Stroud serves as VP and as Service Management, Cloud Computing and Governance Evangelist at CA Technologies. Robert also serves as an International vice president of ISACA, is part of the Framework committee and was the former chair of the COBIT Steering Committee. Robert also serves on the itSMF...
Read More..

Why Cloud spells C.o.m.p.e.t.i.t.i.o.n. for the average IT department

Published: April 20 2010, 02:57 PM | no comments
by CA Community

Competition seems to be a controversial topic for many in IT. We rather see ourselves as service providers, but typically as the only - or at least the preferred - service provider. The reason to start this new column series on 'The impact of cloud computing on IT service management' with this controversial topic is that there seem to be two independent train of thoughts around cloud computing. On the one hand cloud computing is seen as a way to make traditional IT more efficient, on the other it is seen as a way for users to source IT solutions directly. The first group talks about Infrastructure as a Service and private clouds, while the second talks less but rapidly implements Software as a Service solutions, often bypassing the IT department in the process. Both groups are implementing cloud computing, but from very different starting points. Somehow they need to start talking again; otherwise we either get ‘strangers passing in the night’ or ‘a train wreck waiting to happen’.

For the first time in its history IT is facing outside competition. Sure, outsourcing was no picnic, but outsourcing was more like subcontracting to a ‘friendly’ supplier than real competition. With cloud computing users can simply go outside to procure the services they need. I am currently watching an interesting example close by. While the internal IT department is scrambling to offer an in-house social media type collaboration environment, one user department already went outside. To protect the innocent we won’t mention whether this was a production, sales, marketing, R&D or other department, but you get the idea. Starting in Australia, furthest away from corporate headquarters - both in distance and time-zones - they set up a collaboration environment with an outside cloud provider. In just a few weeks  every member of this global department started sharing their activities, thoughts, projects and enjoying the typical communication that people enjoy on social networks.

As this cloud service is low cost (even starting with free), easy to use and it offers anywhere, anytime access also from non HQ supported devices such as iPhones and home PCs, the chances of IT winning this department back for their corporate service are dim at best. One good soul tried to help IT by requesting a similar online watering hole from corporate IT. As instructed he filled out a service request form at the central service desk , but to date he is still awaiting the first response from IT (a first response likely to be questions about priorities, about what executive will sign this off and what cost center it needs to be charged to). Now this may not be a mission critical enterprise system, but similarly we see user departments contracting directly with system integrators to build new enterprise solutions on a PaaS platform. My point is that many IT departments still seem to be in denial on the realities of this new competitive world called cloud. Time for a wake-up call.

Now IT is not the first department in corporate history to face some serious competition. Here is a wake-up analogy from the consumer electronics industry (if you’re not big on analogies, just substitute 'application' for 'TV and 'IT' for 'factory' and 'cloud' for Japan). About two decades ago a company from my country was global market leader in color TVs. Back then the average life cycle of a TV, before a new model would arrive, was 3.5 years. The average price was fairly stable at around 800 Euro’s and basically all components were custom designed  and produced in house. Becoming the head of a TV factory was the ultimate career dream for many in my home town. Just a few years later, after Japan and Korea entered the global market, prices had dropped by 40% (and continued halving every two years), new models replaced old ones every 6 months and innovations such as remote controls, stereo, PiP and c-text determined market leadership. Our local multinational nearly did not make it through this transition. To cope they introduced 'just in time”, 'total quality' and started 'design for manufacturing', heavily utilizing standard off the shelf components to accommodate the much shorter life cycles. And to top things off they stopped producing the main component (CRT’s) in house, instead they created a production joint venture (a.k.a. a 'cloud') with their biggest competitor.

Overnight the head of manufacturing had to change from being ‘the king of low cost production’ to ‘the fastest orchestrator of the supply chain’. Agility became the word. But agility did not replace the need for low cost, high quality or advanced innovation. It was about delivering all of those at the same time and at neck break speed. Some industries decided this was just too hard and stopped in-house manufacturing all together, others saw it as an opportunity for differentiation. In my view the above analogy graphically illustrates the roller coaster ride IT is about to get on.

Many of the needed skills and tools, such as smarter sourcing, resource pooling, and service oriented architectures; we have already been trialing in the past few years. Under the banner of agile development we even have had a first go at coping with rapid change, despite the overwhelming complexity of enterprise IT. In addition there are many manufacturing best practices, Lean being the obvious one, that IT can benefit from (see also 'How lean is your cloud').

The question in my view is: is IT ready and willing to give up their manufacturing role (provider of services) and transition into an orchestration/supply chain role. Essentially engaging in both mentioned conversations: making enterprise IT more efficient, while at the same time enabling the enterprise to leverage readymade market/cloud services. Interested in your thoughts and comments.

Share this post:  

 

By: CA Community
CA Community is the blog manager’s account used to post general updates and news items.
Read More..

More Posts Next page »