Resource Library

Using ITIL can improve your IT service levels, customer service ratings, business productivity and reduce operating costs, but getting started can be overwhelming. Gain the understanding you need to adopt and adapt ITIL with instructions and tips for important steps such as internal employee communications, determining potential pain points and methods for evaluating your existing processes.

The ITIL® event management process defines three event types: informational, warning and exception. In this post, I will discuss the different event types and give real-world examples of each.

Change is the order of the day, and if anything, the pace of business and technology change is accelerating. The business and customers are looking to IT service providers to be more responsive, delivering more frequent service changes with higher quality-resulting in services that deliver more value to the business. In order to continue to be relevant and of high value, ITIL must continue to benefit from other complementary best-practices for IT. DevOps, an approach that encourages improved communication, collaboration, and teamwork across development and operations, can have a positive influence in improving ITIL processes across the service life-cycle.

This white paper describes a technique for defining processes called SIPOC (Suppliers, Inputs, Process, Outputs, and Customers). SIPOC provides a structured way to define the key elements of any process. SIPOC can be used as a means of defining any of the service management processes presented in ITIL® best practices. Furthermore, SIPOC can be used as the preliminary input into the more formal documentation of a process in one of many process design tools.

Learn the ITIL® concepts of accountability, boundaries, and consistency (the ABCs) and discover how ITIL helps establish, manage, and maintain the ABCs.

A gap analysis is a tool that ITIL recommends organizations use to compare their current state to some future desired state.

Many I&O leaders and customers see little value from investments in ITIL. Not getting the Return on Investment (ROI) you expect normally comes from using ITIL incorrectly. You, your staff, and your customers must share the same goals and understand exactly what to expect from your ITIL investments. The goal of ITIL is not “business and IT alignment” or “competitive advantage from IT investments.” Instead, its first goal is to stabilize service operation. This builds a base for the second goal: increasing value through service optimization. You must have clear-cut, documented, and managed expectations for each activity, and order is vital. Success requires that you stabilize service delivery before trying to optimize. Focusing on the correct goal and linking each ITIL task to that goal is the correct use of ITIL.

ITIL is generally not prescriptive. In reality, the CSI Register at any given organization might look significantly different than the example given in the CSI book. The fields given in this example are important. 

Organizations that plan for and conduct supplier management according to defined processes and boundaries are more likely to receive predictable, high-quality goods and services from their suppliers in a timely manner.

Previously I discussed service providers and their risks in the example of my involvement with a landscaping company. ITIL clearly states that services, “…deliver value to customers by facilitating outcomes customers want to achieve…” However, sometimes organizations and people focus on outputs as opposed to outcomes, which sacrifices some of the value of the service. This leads to a question, what is the difference between an outcome and an output?