Skip to main content

Process Improvement is Like Driving a Stick Shift Car

Have you ever driven a stick-shift car?

At first, it feels as if there are way too many steps to remember just to move from park to drive. Step on the clutch, put the car into gear, ease off the clutch as you gently press on the gas. Once you are moving, you then have to upshift and downshift to navigate thru traffic, all the while hoping not to stall the car or strip the gears. What if you get stuck on a hill? It takes all of your skill not to slip into the car behind you.

You may have thought, "Is this really worth it? If I were in an automatic, I could just put it into "Drive" and go. This stick-shift is slowing me down".

So why do race cars choose manual transmissions over automatics? The answer is simple - it gives the drivers better control, helps them meet the challenges of the track and allows them to go much, much faster.

IT Service Management process improvement is similar to driving a stick-shift car. At first, you may perceive newly implemented processes as more of an obstacle than an enabler. Too many forms, too many delays, too many interfaces with other processes, people or technology.

You may think "Is this really worth it? Before we implemented this process, I could just make that change and move on! This process is slowing us down. "

Clear, repeatable, effective and efficient processes give an organization better control, improve their ability to meet to changing business requirements and, once mastered, allow IT to go much, much faster at a higher level of quality. It may not seem that way at first - staff needs time to adapt to a new set of procedures and processes need time to demonstrate benefits. As processes mature and become part of your organizational culture, a natural order will evolve for performing the right steps at the right time. When process becomes "just the way we do things here", you will be able to go much faster with better control.

This is the type of analogy that can make ITIL, MOF or other ITSM organizational awareness campaigns more relevant. Maybe include a poster of your favorite NASCAR or Formula One Driver? Just a thought.

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 then 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 Offe

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