Skip to main content

Achieving ITSM Balance

In speaking with colleagues and practitioners, I have found that one of the greatest difficulties for companies to overcome in a Service Management implementation is the desire to be more complex and unbalanced than is absolutely necessary. One of the most basic and underlying elements of good Service Management is the achievement of balance in how we approach the delivery of value to the customers and users through services. Balance helps us to find an equitable point that brings value to the customers and users without throwing out the efforts and actions needed to keep IT going.

When I speak of balance, I am referring to finding the middle ground between extremes. These include balances like the amount of time and effort spent between Incident Management and Problem Management; or perhaps the balance between flexibility and stability; or even the challenges of being proactive versus reactive; customer/service-centric versus technology-centric. There are a multitude of these types of balances and challenges that face an organization trying to use the best practices of Service Management.

An old adage states that “the squeaky wheel gets the grease”. This is true in IT as much as anywhere. We turn our attention to those things and tasks that make the most noise or those people who have the loudest voice. As humans we want to please others. It gives us satisfaction, praise and rewards. However, in simply trying to satisfy every need as quickly as possible in the easiest, most cost effective and timely way we are actually often throwing things out of balance. Sometimes it takes a hard choice to go down the “road less traveled” to find a more stable and effective, efficient and economical balance that brings the greatest value to the customers and users, but does not bring instant gratification.

We could spend all of our time doing Incident Management and resolving service issues and putting out “fires”. But this means a choice not to do Problem Management and gain the benefits of finding problems before they appear or stopping Incidents from constantly recurring. If we put all our time to finding root cause, we will have unresolved issues that impact the value we promised to the customers and users. So the best option is to find a balance between Incident Management and Problem Management that will allow us to resolve issues while spending some of our time being proactive with future potential problems.

To better achieve these benefits of balance we must do several things:
  • Identify opposing views or ideas or action sets that exist within our organizations
  • Determine the balance or middle ground between the extremes for our individual organizations
  • Identify actions we can take now to move towards that middle ground or balance point
  • Put those actions into place
  • Continually improve by looking for more balances to achieve


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