Skip to main content

Why are IT Services So Hard to Define? (Part 1)

A Service Catalog is one of the first assets that an organization should build when initiating their Service Management program.  After all, how can you manage services if you do not have a clear understanding what services your IT organization provides?

Unfortunately, many organizations struggle with obtaining agreement on the scope and definition of end-to-end, business enabling services.  If left unchecked, these struggles can turn political and widen the divide between IT and the business as well as cause conflict between internal IT units. 

To avoid some of the potential challenges in service definition exercises, here are some helpful suggestions:
  • Set the stage by providing IT staff with a chart of business processes and begin integrating business vocabulary into service parameters ("Order Processing" not "Ecommerce").   Have business stakeholders conduct "lunch and learn" presentations that educate IT on how each unit uses IT Services.  Start your service definitions with a business outcome and work the technology backwards  ("Claims" instead of "XYZ application")
  • Stop equating applications with services - one service is likely going to be built upon multiple applications.  This is a big culture change and requires constant reinforcement.
  • Watch for political minefields that imply that an application, individual or team is less important if not designated an official "service".  Just because the network may not independently qualify as a business service, it is still critical to the delivery of other services.
  • Avoid making definitions too technical or so business centric that business and/or IT staff can't relate to or envision the service.
  • Speak in terms of value to the business ("What value does this service provide?  What business process does it enable?  How does it affect the bottom line?").  Avoid discussing the underlying technical infrastructure with customers.
These are all good first steps to creating a common understanding of outcome-based service.


Piotr Chęć said…
I agree with you. In reality though, I have seen many more IT organizations focusing on incident and change management and never going beyond that.

I think it is safe to assume, that having a service desk is pretty much given in most larger companies. The difference between IT of the past and IT of the future is strong orientation on business processes and the services enabling them. All of us, ITSM professionals, have a role to play in driving this change.

Piotr Chec
ITSM Perfection Blog
Joseph said…
Have business stakeholders conduct "lunch and learn" presentations that educate IT on how each unit uses IT Services.

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service". I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize: SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle. ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with