ITIL 4 Guiding Principles - Keep It Simple

ITIL 4 Guiding Principles - Keep It Simple - Take Two

If there is a way to make something complex it seems like we as IT Service Providers have that technique down to an art. Last week an ITIL 4 Foundation student asked, “Why is that?"

The human brain is an intricate organ weighing on average about three pounds. There are about eleven billion neurons and one hundred trillion connections in your brain. The brain is the command central of everything that we think, everything you say and yes, of every solution that we might come up with. Our brain is thirsty for information. The more information we allow in the more eager our brain gets. This cycle generates a demand for stimulation. The more complex something becomes, the more stimulated our brain becomes. Hmmm, this might explain why so many become addicted to tech!

This guiding principle “Keep IT Simple” is just that… SIMPLE! The difficult task is going

to be how do we ensure that we have “Just Enough” process and governance moving forward but also how do we take very complex systems, processes and ways of thinking that exist and “Keep IT Simple”. In many cases, we will have to radically shift the way that we think and train our brains for a new way of looking at things. A new way to stimulate these neurons is to think, how can I make this more simple? Then look at the solution again. Think once more, How can I make this even more simple? Challenge this creative eager brain to work hard and stimulate it with “Simplicity”!

There are a lot of techniques and methods that are available to us and in some cases where over-engineering has gone wild, we might have to step back and re-engineer some processes that are too heavy or too rigid for today's evolving requirements and business need.

One solution to consider is “LEAN IT”. Applying things like “Value Stream Mapping” (a lean tool) that will allow us to identify where there is waste, and where there are bottlenecks that hinder the flow of work.

Another way to keep things simple is to apply Agile Service Management practices and follow an iterative approach for ongoing continual feedback and corrective actions to siphon out waste with incremental improvements. There are other techniques like swarming and collaboration using chat clients and chat bots! Kanban boards will help to visualize work and therefore identify issues early in the creation of solutions.

To keep it simple we will have to have an open mind. “Keep IT Simple” is only one of seven guiding principles brought forward with ITIL 4 best practices. These guiding principles are not exclusive and like “Keeping IT Simple”, are used in conjunction with all the other ITIL 4 guiding principles. The ITSM Professor provides an overview for each of the ITIL 4 Guiding Principles. Learn them all and realize how they can help you in your continuous journey for improvement. Understand that to be fast and nimble we must “Keep IT Simple”

Educate & Inspire!

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 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 the concepts have changed in ways that are described below. ITIL 4 has also introduced new roles, as explained in our blog ITIL 4 and the Evolving Role of Roles . Before we dive into the difference between these roles, let’s first look at a key update in ITIL 4 – the shift from processes to practices. ITIL 4 has evolved to focus on holistic practices vs. isolated processes. By definition, a practice is a set of organizational resources designed for performing work or accomplishing an objective. For example, the purpose of the incident management practice is to minimize the negative impact of incidents by restoring normal service operation as quickly as possible. All organizations recognize the need to allocate resources to the management of incidents and mature their capabilities in that area. In ITIL 4, each practice includes resources based on the four ...

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

Search