When ITIL 4 was introduced, one of its biggest - and most misunderstood - shifts was moving away from processes to a broader, more flexible concept: practices .   See also What is the difference between Process Owner, Process Manager, and Process Practitioner? In earlier versions of ITIL, each process had a clear sequence of activities, inputs, and outputs. That approach helped organizations standardize service management but often led to rigidity,  especially as digital transformation accelerated and work became more cross-functional. ITIL 4 recognized that service management isn’t just about what we do, but also who , how , and why . A practice is a holistic set of organizational resources -  people, processes, information, and technology -  working together to achieve outcomes. Processes still exist, but they now sit inside practices rather than defining them. What This Means for the Service Management Office (SMO) For many SMOs, this shift...

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