What does it mean to "adopt and adapt"?

What does it mean to “adopt and adapt” an ITSM framework like ITIL? This question has come up recently in several of my classes. It is not an easy question to answer but one that needs to be addressed early on in any ITSM implementation effort.

The first consideration is the adoption of a framework or perhaps even more than one. Yes, with an ITSM implementation we are not limited to taking on the advice and best practices of only one approach. When we “adopt” a framework, we make a commitment to use the methods, means and approaches laid out within a given framework. This commitment includes being willing to go as far as redesigning how and why we undertake activities and efforts within our organizations. If we want to “adopt” and ITSM framework, but we do not change the fundamental way we approach things, then we have not really adopted an ITSM framework. Adoption requires a fundamental willingness to see things from a new perspective. If you want to redesign your living space you cannot simply rearrange the worn out and in-need-of-replacement furnishings. We want to meld the practices presented in the framework to our “corporate DNA” and become a new version of ourselves.

The second consideration is how to “adapt” the chosen frameworks to meet the needs of our customers. It is important to remember that “adaption” of a framework is not a license for free reign. If your desire or tendency is to change a large portion of the recommended advice then you are not really implementing best practices. You may be simply rearranging your current ways or giving yourself an organizational makeover without addressing the fundamental issues that motivated you to seek out an ITSM framework initially. Adaptation means to adjust the best practices at a detailed level to fit the nuances and nature of your business and its customers. Adaptation includes creating procedures to allow the processes provided in the framework to work in a step-by-step manner and facilitate the use of technology as an enabler of the processes.

In order to effectively “adopt and adapt” we should think about a number of key factors and answer a number of questions:

Why does the organization desire or need ITSM? What do we hope to achieve through our effort to “adopt and adapt”?
What issues or problems do we currently face or might face for which our current methods and approaches have proven insufficient?
Are we willing to give up or throw out inefficient, ineffective and unsuccessful methods that we currently use or have tried in the past?
Are we willing to make needed cultural changes in order to facilitate the implementation of ITSM?
Are we willing to reorganize our structure and staff to make ITSM work?

If your organization is unwilling to change or cannot answer these questions confidently then you will want to prepare your organization for a potentially rough road towards implementation. Entering into an ITSM implementation can be a daunting affair. Going in with a plan and a clear understanding of what it means to “adopt and adapt” can help.

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

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 this best practice has changed. See ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...

Search