Skip to main content

Stability vs Responsiveness

In an earlier blog I spoke to the conflicts that all operational organizations face.  This struggle can be broken down into four general imbalances so that an IT organization can identify that they are experiencing an imbalance by leaning more towards one extreme or the other.  At a high level it can provide the service provider with the opportunity to develop some guidelines on how to resolve these conflicts and move towards a best practice approach in resolving discrepancies.  We talked to the first and most common which was the Internal IT view vs. the External Business view.  Today I would like to speak to the dilemma of Stability vs. Responsiveness.
IT operations must ensure that the IT infrastructure is stable, performs at an agreed and defined levels on a consistent basis and is available with the correct amount of capacity to meet the demands of ever changing patterns of business activity.
These changes can be evolutionary.  Needed changes in functionality, performance and technology can happen over a long period of time.  These types of changes can present the service provider with the opportunity to plan, design, build and test better levels of performance and create greater efficiencies and more effective use of resources.  In these scenarios it is much easier to maintain the desired stability IT is seeking, while enhancing customer satisfaction by delivering the new requirements their customers and users seek.
Although as service providers we would always prefer to have our changes presented and delivered in this manner, we know that in today’s business environment this is not always possible.  Many changes happen very quickly and come with considerable constraints on timescales and resources.  The ability to meet these types of deadlines and not impact the services that are currently live can often be a considerable challenge to any IT organization.
Given this tension between stability and responsiveness there are some actions an organization can take to enhance its ability to meet these challenges.
  • Ensure investment in technologies and processes are adaptive and incorporate the use of change models
  • Build a solid service level management (SLM) process with strong ties to all processes from service design all the way through to continual service improvement (CSI).
  • Through service asset and configuration management (SACM) ensure the proper mapping of IT assets to business services and IT operational activities
  • Initiate the change process as early as possible.  Ensure there are strong ties to the project management office (PMO) and the business change process.

Comments

Popular posts from this blog

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, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

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

This article was originally published in 2015. With the Introduction of ITIL 4, some of the concepts have changed in ways that are described below. ITIL 4 has also introduced new roles, as explained in our blog ITIL 4 and the Evolving Role of Roles . Before we dive into the difference between these roles, let’s first look at a key update in ITIL 4 – the shift from processes to practices. ITIL 4 has evolved to focus on holistic practices vs. isolated processes. By definition, a practice is a set of organizational resources designed for performing work or accomplishing an objective. For example, the purpose of the incident management practice is to minimize the negative impact of incidents by restoring normal service operation as quickly as possible. All organizations recognize the need to allocate resources to the management of incidents and mature their capabilities in that area. In ITIL 4, each practice includes resources based on the four ...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...