Skip to main content

Keeping the Momentum Going

The Continual Service Improvement publication describes the Continual Service Improvement model. One of the questions asked in this model is “How do we keep the momentum going?” This question becomes especially important when your ITSM implementation efforts have been in place for a significant amount of time. The question then becomes more one of “How do we stop from losing the momentum and effort invested up to this point?” Or perhaps “How do we avoid from returning to the old ways?”

For all our efforts to become efficient, effective and economical there is a potential danger that we will fall into comfortable, yet poor habits. So how do we ensure that we do not fall into bad habits such as taking shortcuts, pushing aside process, and just “getting things done” instead of following established methods and processes and doing proper planning?

We must begin by being confident in the strides we have made to this point. If we have followed the Continuous Improvement Model faithfully over time then we will have taken the right steps and established a successful implementation. Once we begin to question the steps we have taken then doubt creeps into our minds. When doubt appears then we will struggle to maintain momentum. By remaining confident in our choices and decisions we can forestall doubt.

Next we must prepare for the future. Building a strong strategy, conducting effective tactical planning and establishing operational approaches and methods can help to pave a smoother road for your efforts at implementing ITSM. If we try to deal with things as they come at us in an ad hoc and unplanned manner, we will struggle to find effectiveness, efficiency and economy. An important part of avoiding old habits is to have the tools, skills and methods in place to deal with roadblocks, barriers and other pitfalls that we may face as we move to higher levels of maturity in ITSM.

Another consideration for avoiding the loss of momentum is to recognize early enough the slowing of your momentum. Look for signs or listen for statements that indicate that people have lost the “spirit” of ITSM. Analyze your metrics to determine if any unexpected changes or trends have occurred with your processes. Have the number of incidents slipped for no reason? Have unauthorized changes been on the rise despite the maturity of your process? Have the amount of suggestions for improvements declined? If you notice that the “spirit” of service management seems to be declining, that is when you must make more effort to re-invigorate people.

The final aspect of keeping the momentum going is to ensure you have the data, information and knowledge available that provides the evidence needed to identify potential improvements. A key part of the momentum of ITSM is the whole idea of improvement. A mindset of making things better for the customer and delivery of value is vital to ITSM. You must use evidence to show the benefits that can be gained from ITSM, as well as to instill a mindset of continual improvement.

There are any number of ideas you can use to ensure that you not only keep moving forward with improvement but also that you did not slip backwards and into ways and means that provide no value. Spend some time thinking about how your own organization might ensure that the cycle of improvement continues.

Comments

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 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 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 than toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

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 th