Skip to main content

ITIL 4 Guiding Principles – Keep It Simple

Keeping it Simple is one step towards creating a world where people get up in the morning and are inspired to go to work and love to do the work that they do. The more complex something is, the more there are ways for it to go wrong. We as an industry of service providers must become educated and stop the insanity! Getting the education and the certification is a wonderful first step but once qualified we must adapt those learnings to make it simple and “Keep IT Simple” 

“Keep it Simple”, one of the seven ITIL 4 Guiding Principles is a topic we have written about many times over the years.  It is anything but simple. We must acknowledge that IT services are comprised of many complex systems and if there is a way to make them even more complex IT Professionals in general seem to have that idea down to an ART. 

So; How did we get that way. Business requirements are dynamic and are consistently evolving even as you read this line. Over a period of years and in many cases decades the systems that support those requirements have evolved. Historically IT professionals adapted to the bureaucracy that they were wedged into in order to survive. A bureaucracy typically refers to an organization that has multi-layered systems and processes. These systems processes and procedures were designed to maintain uniformity and control. Keep it simple! We need just enough process, just enough governance, and just enough incremental ongoing improvements to make it simple and to keep it simple. Processes overtime in many cases became over-engineered and while they might gain the control needed for compliance and regulatory demands, they tend to slow down the flow of work, create roadblocks and sometimes become a major impediment to getting quality and value delivered on time. It really hurts our capability when the process becomes the goal rather than the outcomes that generate real value! Monolithic applications, legacy systems, and siloed cultures all add the complexity for the delivery of services to customers. 

DevOps and Agile professionals are adapting to new ways to remove waste and to increase the flow of work for all value streams using LEAN practices. Applying one "ity bitty" micro improvement (simple) can sometimes have an extreme impact to the agility of your value streams and to the overall value potential. Notice the ity bitty?! Take one small improvement opportunity to simplify a process or system and break that into many other small increments of improvement. Prioritize and pick one. Work fast to integrate that change into the process and then start again. Remember you can not implement a process. It is an ongoing emerging set of activities which hopefully evolve with the dynamic needs of the business and customer. 

Deming says: Plan, Do, Check Act! Agile says “one increment “or iteration of work at a time. ITSM best practice says that with Continual Improvement you must “Keep The Momentum Going”. All will require an outside-in perspective with ongoing feedback loops to help us prioritize the next step towards “Keeping IT Simple” one of the DevOps Principles is “Shortened and Amplified feedback loops. The sooner the better. If a process, service, metric, report or anything that is in play today does not add value, take corrective action or eliminate it! Keep it simple and adopt ITIL practices and then adapt keeping it simple and speaking "simple" as you co-create with others.

Make it Simple and Keep it Simple! … Keep the Momentum going and inspire others to greatness!

...educate and Inspire 


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 th

The ITIL® Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi

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