CA Community






This Blog

Changing the menu is a risk!

Published: October 27 2009, 12:00 PM
by Robert Stroud

My travels recently took me to Tokyo for the CA Expo. When in Japan I usually stay at the hotel close to the office which helps my day and evening to be very predictable. I arrive at Narita, take the bus to the hotel, go to the office and then back to the hotel where I order their famous burger. Now this is no ordinary burger; it has pineapple, bacon, egg, 2 patties, lettuce, cheese and on top of all that I add an extra egg (and schedule an extra hour in the gym as well). 

On a past visit for an itSMF conference, I arrived and was faced with a challenge. The menu had changed and I couldn't find my beloved burger!  What to do?  I immediately logged a complaint, sorry incident with the Service Desk (hotel reception) and I believe that my issue was escalated to second level support as the Duty Manager called me back to give me a lengthy explanation about the business rationalization for the change in the menu. He then offered to make have a burger made as per my request. What great customer service! I was suitably impressed. 

Last week when I returned to Japan and my usual routine, imagine my delight as I opened the menu to find my famous burger was back on the menu!  Was my feedback that important that I changed the whole menu?  I called Room Service and asked for my burger, only to be told it was no longer on the menu and that the menu in my room was the old menu.  What devastation. I had not effected change, and in fact, poor change management by the hotel had led to significant drop in my satisfaction level. 

I had a similiar experience when I was taking one of my flights within Asia. The airline I was travelling on recently introduced a new service charge into effect that I experienced while in Asia. The IT Systems were updated, the staff informed, the Web site updated of the changes to the baggage rules but those who had bought tickets in the period prior to the change and had not visited the Web site had no idea and turned up to be hit with an additional charge that due to the coding of the IT systems could not be waived (well at least that's what I was told). I dutifully paid the charge and then caught my flight and again the customer experience rates as below average.

These experiences reminded me of the complexity of change management and that it clearly extends beyond IT and that if we do not get the cultural and organizational aspects correct then even the best IT change process won't make the situation better. Change is no longer just change for IT;  it is "IT enabled Business Change" and as such, change management must include the business and the cultural aspects must form part of your consideration.

Have you rolled the Business into your Change Advisory Board?  If not, maybe its time!

 

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..

5 people have left comments:

Excellent point, Rob.  All changes should have consideration of "impact on customers" as part of the impact analysis, inclusive of "soft impacts" like how a change may affect how a customer orders a service, uses the service, is billed for the service...  How about a simple flag in change order template with "soft impact on customer" yes or no, where a "yes" triggers a template that drills into these other questions?  This would then spawn processes such as sending notifications to affected users, updating the service catalog, etc.

Posted by: Dave Wilt | October 29, 2009 12:56 PM

Great article Rob. It never ceases to amaze me when changes are implemented without thinking through the full implications. Ultimately, if the change affects a service then it impacts the customer of that service. One of the things overlooked is the expectation vs delivery - the outcome of this defines the customer's experience and ulimately their view of the company/organisation/department. Customers have a choice and are quite vociferous when let down. Change management isn't just an isolated process its effects are felt throught the organisation. The point of service delivery (consumption) is where many (behind the sceens) aspects are brought together in a moment of truth...

Look forward to seeing you in Birmingham at the itSMF conference. can't guarantee the burgers!

Paul Gostick

Posted by: Paul Gostick | October 29, 2009 2:35 PM

Rob,

I agree that you have made some very valid points.  A task that IT Organizations can add to their overall Change Management process is impact analysis.  This type of analysis will allow IT organizations to look at their change process from the customer view and also from a holistic perspective.  Impact analysis also encourages IT Organizations to tie their Change Management process to other ITIL processes, such as SLM and Financial Management.  By doing this, IT could potentially identify and avoid SLA breaches and financial penalties caused by the change.

Posted by: Michael King | October 29, 2009 4:27 PM

Wow! I think a good explanation of something that is made out to be a complex concept.

The linkage is also excellent..

Good one...pleasant reading.

Posted by: raghu | November 10, 2009 9:10 AM

Paul,

I am always amazed at the reluctance of IT professionals to "see the bigger picture".  My change will not impact the Banking Service, I am only installing a patch or rebooting a single server.  Now if you look at the micro level their view may be correct, at the global service view, not so true as the server is critical to the Service Value Chain (SVN).  In the past we knew all the pieces, parts, components, now it is a large task to understand it all.  Thus Change Management is a critical discipline as you and I agree.

Great to see you this week - we shall catch up again soon.

Rob

Posted by: Robert Stroud | November 10, 2009 3:28 PM

Leave a Comment

* An asterisk indicates a required field

* :  

:

* :  

 Submit