Creative ITIL® Implementation: Practicing the Framework Before It Is Formally Adopted
ITIL Is Not a Label — It Is a System of Value Creation
While serving as Director of IT Support a few years ago, I attended a discovery and demonstration session for System Center Service Manager (SCSM) with a Microsoft partner. Leaders from multiple IT functions were present.
Midway through the discussion, the partner directed a question to me:
“Are you an ITIL shop?”
A senior colleague replied, somewhat playfully, “She’d like to think so.”
Rather than debate terminology, I described the operational disciplines already established within our multi-tiered IT Support department:
- Structured incident categorization and prioritization
- Clear differentiation between incidents and service requests
- Defined major incident procedures
- Recurring trend analysis and performance reporting
- Root cause investigations for high-impact disruptions
- Documented known errors and knowledge management
- Monitoring and automated response to network events
- Risk-informed change review of code releases
- Measurement of restoration times and repeat incident reduction
The partner paused and responded:
“Ummm… you’re an ITIL shop.”
That moment clarified something important: ITIL maturity is not determined by declaration or labels. It is demonstrated through disciplined practice and results.
What we had built aligned closely with the ITIL 4 Service Value System. Governance expectations were clear. Practices were integrated. Continual improvement was embedded through reporting and analysis. In Service Value Chain terms, we were effectively operating within Deliver & Support and Improve – all without a formal, organizationally sanctioned branding of being ITIL-aligned.
ITIL is not a label. It is a system of value creation.
Operational Maturity Within Your Sphere of Control
There is no doubt that executive sponsorship accelerates enterprise alignment. However, there are times when practitioners need to exert their significant influence long before formal adoption occurs.
Within service desk and support operations alone, leaders can intentionally mature critical ITIL practices within their sphere of control:
- Service Desk and Service Catalogue Management
- Incident and Service Request Management
- Measurement and Reporting
- Change Enablement and Risk Management
When implemented systematically, these practices stabilize operations and produce measurable business value.
This gives us the ability to earn credibility through outcomes:
- Improved mean time to restore
- Increased change success rates
- Greater service reliability
These are not internal process metrics. They are indicators of resilience, customer experience, and cost control.
Why does this matter? Because executives support and fund outcomes, not frameworks.
Change Enablement as a Catalyst
Eventually, my role expanded to Vice President of Technical Operations. With additional operational groups under my leadership, I had broader influence - and greater opportunity to continue what I often describe as a “stealth ITIL implementation.” The framework had still not been formally declared enterprise-wide, but its principles were steadily shaping how we operated.
The arrival of a new CTO brought renewed focus on reducing infrastructure-related change failures. Failed changes were driving service instability, complaints from the business, increased incident volume, and avoidable business disruption. Addressing this challenge required more than technical fixes; it required strengthening the Plan, Improve, and Deliver & Support activities within the Service Value Chain – specifically, Change Enablement, something I had lobbied for many times.
I volunteered the services and expertise of the TechOps ITSM Manager to assist with formalizing and improving Change Enablement, but was met with predictable resistance. There was concern that we would introduce a cumbersome approval structure that would delay innovation and system updates. Some questioned whether Technical Operations was overstepping into infrastructure territory. Organizational silos, after all, tend to defend their boundaries.
Absent an alternative solution and with the support of the CTO, Infrastructure finally – if rather reluctantly - allowed TechOps to lead the Change Enablement implementation.
Rather than impose process, we applied the ITIL Guiding Principles deliberately - particularly Start where you are and Progress iteratively with feedback.
We leveraged the existing capabilities within Ivanti Service Manager’s Change module, which provided a familiar system and the ability to align and report on incidents driving change and resulting from change. We evaluated current workflows, documentation practices, and informal review mechanisms already in place. The objective was not reinvention; it was structured refinement aligned to risk and value.
Working collaboratively with infrastructure leaders, we:
- Leveraged existing documentation and workflows
- Differentiated Standard, Normal, and Emergency changes to streamline approvals
- Clarified risk thresholds and approval expectations
- Introduced automation where appropriate
- Increased visibility into change performance and failure impact
Critically, we put processes in place to evaluate the root cause of failed changes - not through blame, but through data, analysis and discussion. By quantifying downstream effects - incident spikes, extended restoration times, and business impact - we connected Change Enablement directly to service resilience and value protection.
As measurable reductions in failed changes emerged, skepticism diminished. Infrastructure leaders began to recognize that Change Enablement was not bureaucratic oversight; it was adaptive governance and continual improvement in action.
The result was not the feared procedural bottleneck. It improved change success rates, reduced service disruption, and increased organizational confidence in change execution.
In time, the very groups that had expressed concern became advocates.
When it comes to framework adoption, sometimes operational discipline – the proverbial “proof of the pudding” - precedes formal endorsement.
Creative Implementation Is Strategic Discipline
Creative ITIL implementation should not be considered deviation from the framework. It is strategic adaptation within operational constraints.
As ITIL continues to evolve - emphasizing resilience, adaptive governance, and value co-creation - one principle remains constant: frameworks do not create maturity. Disciplined practice does.
Formal adoption may accelerate alignment, but operational integrity establishes credibility and accelerates acceptance.
If you are applying ITIL practices intentionally, improving iteratively, and measuring outcomes aligned to business value, you are practicing ITIL - regardless of whether the organization has formally declared it.
That brief exchange with the Microsoft Partner has stayed with me for years. Not because he used the ITIL label that truly described what we were already doing, but because it validated the intentional work happening behind the scenes. We were not pursuing ITIL for certification or branding; we were pursuing stability, clarity, and measurable improvement. The recognition simply affirmed that disciplined practice speaks for itself. Sometimes, the most meaningful validation comes when someone outside your organization sees the framework in action before your organization has named it.
