Skip to main content

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.


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 policies (r…

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 the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…