The IT Infrastructure Library (ITIL), a longstanding framework, has been both embraced and abandoned by numerous organizations, shaping perspectives on service management in IT. This debate centers on whether service management encompasses the entirety of IT organizations delivering services or is predominantly focused on organizing bureaucratic aspects within service delivery operations. It hinges on interpreting ITIL: as principled guidance from ongoing discussions or as a manual dictating IT service operations. Is ITIL more principle-based or rule-based guidance?
Similar debates apply to related frameworks like DevOps, which can be viewed through both principled and rule-based lenses, yielding parallel outcomes in practical application. Manuals thrive in controlled environments with precise instructions. However, in complex, dynamic settings with various components, overly prescriptive manuals become impractical. When an organization operates within a complex environment, treating best practice frameworks as rule-based manuals becomes futile.
Examining Service Management, foundational concepts shape our understanding. The ServQual framework’s adaptation in ITIL highlights the roles of customer and supplier: customers remain directly engaged with service providers, unlike product manufacturers whose influence diminishes post-sale. Direct interaction between customer and service provider fosters feedback, allowing for service improvements. However, underlying assumptions and miscommunication often hinder service delivery.
In the realm of IT, services are delivered through various products, often prioritizing product development over service comprehension. Advancing IT organizations recognize the significance of understanding how IT products impact users, evident in many ITIL implementation programs aiming to elevate users to customers.
Another core aspect within service management emerges from discussions on the Experience Economy, which posits a value hierarchy—from raw materials to products, services, and ultimately experiences. As complexity increases, delivering experiences adds individual-specific value but also elevates costs. Reducing complexity enhances service availability while potentially lowering costs and perceived value.
This customer-centric hierarchy of value and its relation to delivery complexity is instrumental in discussing IT service management. Tailored IT services command higher value and complexity, whereas generic services necessitate reduced complexity to remain valuable to customers.
The IT department’s role is pivotal: discerning when complexity enhances value and strategizing to mitigate complexity when costs exceed perceived service value. Embracing IT service management unveils a dynamic and compelling concept for exploration within the ever-evolving landscape of information technology.
To read more about organizational design I made a list of curated articles on this subject
- 7. Optimize and Automate – the seventh guiding principle of ITIL4
- 6. Keep it simple and practical – the sixth guiding principle of ITIL4
- 5. Think and work holistically – the fifth guiding principle of ITIL4
- 4. Collaborate and promote visibility – the fourth guiding principle of ITIL4
- 3. Progress iteratively with feedback – the third guiding principle of ITIL4
- 2. Start where you are – the second guiding principle of ITIL4
- 1. Focus on Value – the first guiding principle of ITIL4
- Forbes: ITIL 4 is coming
- McKinsey: The expanding role of design in creating an end-to-end customer experience
- Top 100 Influencer on Service Management