Guide to Demystifying ITIL: Practical Tips for Real-World Implementation
The Information Technology Infrastructure Library (ITIL) was originally a set of IT service management guidelines proposed by a UK government agency. Since the release of its third edition in 2007, it has become the de facto standard framework for IT service management, aiming to improve IT service quality by addressing management needs.
Although more public literature and IT professionals are demonstrating their awareness of the ITIL framework, its technical concepts are still widely misunderstood. Regardless of an organization’s size, implementing ITIL is a massive challenge. Fortunately, the company I work for has already integrated ITIL into its business management processes. Even so, the overall adoption of the ITIL framework is still in its early stages and undergoing a difficult maturation process.
When I began leading the coordination of change management processes for a large organization, I struggled with how the overarching ITIL framework could deliver tangible benefits and value in daily operations. In fact, starting with the overall IT management architecture is far more sensible than getting bogged down in the specific details of each ITIL book.
Here are some friendly tips for understanding the concepts of the ITIL framework:
1. Align ITIL with reality: The expansion of the ITIL framework is undeniable, but that does not mean you must integrate the entire ITIL framework with your company’s business. You should view ITIL as a tool to discover answers to specific needs and problems based on actual requirements. In reality, not all ITIL processes bring benefits to a company. When many people mention ITIL, they instinctively associate it with “more documentation, more processes, and correspondingly more workflow.” In fact, you can organize a workshop on how to ground ITIL in reality to illustrate how real benefits can be achieved through the “Service Operation” and “Service Transition” books of ITIL V3.
You can explain how integrating ITIL supports IT maintenance: when developers from a project team leave the company, new application support staff will inevitably struggle due to the lack of support-level agreements and relevant technical and system maintenance documentation. ITIL specifically addresses the service support period after new services or applications go live, emphasizing the importance of knowledge transfer.
2. Attend ITIL V3 Foundation certification training: Nowadays, more and more companies enroll their service desk and other IT support staff in ITIL V3 Foundation certification training courses. This training provides everyone within the company an opportunity to share knowledge. Another benefit is the chance to form a unified understanding of the ITIL glossary, achieving consistent conceptual awareness within the organization and thus laying the groundwork for future ITIL implementation. Note that although it is just a foundation course, learning and understanding a large volume of ITIL concepts, viewpoints, and information in a short period is a significant challenge and difficulty for any newcomer 鈥?one must be prepared for this.
3. ITIL is not just for IT: In today’s world, IT development touches everyone. When integrating the ITIL framework internally, it is not solely the responsibility of the IT department; other departments, such as finance, must also be involved. Once a mature incident management process is established, the vast majority of users will experience the benefits of ITIL standardization and form an intuitive understanding of it.
4. Simple is best: If your company has not yet established a formal ITIL process, starting with best practices and beginning simply will greatly contribute to the successful implementation of ITIL.
The service desk is an excellent starting point. To begin integrating the ITIL framework, you first need to establish a service catalog, which should contain a list of all applications and IT services provided to users by the service desk. Then, we recommend considering how to incorporate ITIL’s incident management process into the service desk’s daily work. For example: by defining the priority of service incident types and establishing service incident escalation policies based on this, then forming corresponding service level agreements and internal operational level agreements for incidents of different severity levels. This will greatly help improve IT service response times after an incident occurs, thereby meeting customer expectations.
During my implementation of ITIL best practices internally, the greatest gains came from the area of change management: the results were very significant, as all implemented changes to products could be identified and tracked. Any change must be communicated and agreed upon with the customer in advance before implementation, and changes should be minimized during peak business hours to avoid losses. By implementing the change management process, we now clearly know what issues are occurring and the extent of their impact on our infrastructure. This also helps reduce unnecessary conflicts or arguments: for example, when the server team is performing Windows operating system patching, the network team clearly knows this in advance and therefore will not simultaneously perform operations like restarting