The core element of ITIL 4 is the "newly created"
Value Chain, which is shown in the illustration above. It describes the most important activity groups on an organizational level, which are necessary to create added value for the customer. The
Value Streams, on the other hand, describe all resources, activities and dependencies that are necessary specifically on an individual level to create value. They are a combination of activities, which may be implemented by different roles, and resources (e.g. products, information or services) with the aim of creating value for the customer. While the approach is a step in the right direction, it is only rudimentarily described in the literature and leaves many question marks over its implementation in everyday operations.
The "newly" created
Customer Journey is designed to expand the Business Relationship Management previously neglected in ITIL v3. Its objective is to involve the customer or user from the initial interest, through the definition of the requirements, the service delivery and the joint creation of value, all the way to its decommissioning. However, this model has so far also been kept relatively general; effective implications for practice are not yet clear from the framework. Here we see added value primarily for organizations that provide their services to external customers. Nevertheless, internal IT organizations can certainly benefit from this approach.
Since ITIL 4,
innovation is an integral part of the overall concept. This is demonstrated by the integration of Design Thinking, which is intended to improve innovation with a focus on the user.
In our opinion, many of the newly added
practices such as project management, risk management and organizational change management (OCM) give a good overview and thus may create considerable added value particularly for smaller companies, as the model covers all relevant areas. However, these practices are certainly too generic and broadly defined for medium-sized and larger companies. Here, the corresponding specific methods and frameworks (e.g. Scrum, Prince2 or PMBOK in relation to project management and Prosci as well as ADKAR for OCM) are more mature than the corresponding ITIL 4 practices
Overall, we are positive about the direction that ITIL 4 is taking. Although this is not an independent element, the revised framework makes strong reference to environmental variables that need to be taken into account, such as the
human factor and the social component, legal or economic changes. Especially in times of Corona, a framework that takes external factors into account and allows companies to react to changing requirements in an agile and customer-oriented manner is extremely valuable.
In many places, however, new ideas are not yet mature enough to be transferred directly from the textbook into practice, which makes it difficult to make the switch based on ITIL 4 alone. Here we see a need to catch up; in order to anchor the principles sustainably in the company, more concrete procedures with practical examples are needed.
Is the switch to ITIL 4 worthwhile?
The question you should ask yourself instead is: What are the requirements for your company and your IT infrastructure?
When changing conditions are a continuous challenge and day-to-day business is strongly affected by technological innovations, agile measures are required. In our opinion, these can be met better with ITIL 4 than with ITIL v3, so it makes perfectly sense for persons responsible for IT service management to study the new iteration. We recommend mainly the "Foundation" to develop a grasp of the overall picture and the terminology, while "Expert" and specific modules are more worthwhile when there is a specific need for a concrete topic.
If your goal is to focus on agility and increase customer focus, we recommend that you examine which elements from the ITIL 4 framework can be transferred to your organization. We would be happy to accompany you in answering this question specifically for your company and in developing a suitable pragmatic approach.