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...
The cloud has changed everything. The way we build, deliver, and manage services looks nothing like it did when ITIL first emerged. Traditional frameworks were designed for centralized, relatively static infrastructures. Today, most organizations live in the dynamic, distributed reality of cloud computing - where scalability, automation, and speed rule the day. ITIL 4 bridges that gap beautifully. Its Service Value System (SVS) connects governance, Agile, Lean , DevOps , Site Reliability Engineering (SRE) , and continual improvement into one integrated approach. I often describe ITIL 4 as moving from rigid processes to flexible, value-driven practices . Nowhere is that shift more evident than in the cloud. New Realities in Cloud Environments Cloud computing gives us extraordinary power: elastic scalability, self-service provisioning, and global reach. But it also introduces new challenges. Resources appear and disappear in seconds. Ownership lines blur between custome...