Six pitfalls to Goldilocks service management

Service management concepts have been widely embraced by IT leaders as a means of improving the efficiency and effectiveness of their organisations.

Enlightened CIOs have come to realise that it’s difficult to create competitive advantage through talent or technology alone since most IT organisations have equal access to the people, software and hardware required to support business operations.

Under these circumstances, internal process sophistication and process discipline become essential components of any initiative seeking to create competitive advantage through the use of information technology.

Service management concepts also provide a new lingua franca for communicating with the functional groups that are ultimately underwriting IT’s expenditures.

Service management can liberate CIOs from trying to explain the benefits of application upgrades, storage virtualisation or network expansion to their internal clients.

A properly constructed business service catalogue can transform those conversations into discussions about inventory turns, market segmentation and cross-sell opportunities. in terms that IT’s clients understand and value.

Although the theoretical benefits of service management are well understood, the IT landscape is littered with organisations that have struggled to implement service management practices.

How can something that is so obviously beneficial in theory be so hard to implement in practice?

The Goldilocks Problem
Goldilocks and The Three Bears is a children’s fairy tale about a young girl who stumbles upon the house of The Three Bears during a walk through the woods.

In the bears’ absence, Goldilocks samples their porridge, their chairs and their beds. In each case, Goldilocks has to try more than one sample of each item to find the one that is just right for her.

IT organisations seeking to implement service management practices typically encounter a very similar dilemma.

Zealots seeking to revolutionise the way IT does business will attempt to establish procedures that are far too detailed, far too sophisticated and, frankly, far too different from current practices to ever be successful.

At the other end of the spectrum, protectors of the status quo will begrudgingly adopt service management jargon to keep IT management happy while continuing to rely on existing operational practices.

The key to a successful service management implementation is to find the balance between business needs and operational sophistication that is just right for individual companies.

The Goldilocks Solution
All successful change management initiatives have certain things in common such as visible executive support, alignment with major business initiatives, clearly defined objectives and success metrics, and early wins.

These key success factors clearly apply to service management initiatives. In addition, there are several potential pitfalls that are unique to service management programs and need to be avoided at all costs.

Several of the more common pitfalls include:

- Building a service catalogue for IT consumption
Functional groups that are consuming IT services are frankly not interested in technical descriptions of three-tier application architectures, network latency or disaster recovery procedures.

They want to buy IT capabilities that enable specific business processes such as lead generation, sales pipeline management or renewals processing.

In addition, they want certain guarantees regarding the availability and response times of such services.

All too often IT groups define business service offerings in terms that make sense to technologists, not in terminology that makes sense to the service buyers.

- Overly ambitious CMDB construction
A comprehensive and accurate Configuration Management Data Base (CMDB) provides the underpinning for almost every major operational practice employed in managing the various technical services that comprise a business service.

1 2 Page 1
Page 1 of 2
7 secrets of successful remote IT teams