Culture Transformation
Why culture determines ITIL success or failure
Research indicates that "60-70% of ITIL implementations fail to achieve their objectives," primarily due to organizational culture rather than process design or tools. ITIL v5 acknowledges this through its guiding principles, which represent fundamentally cultural statements: "Focus on value," "Collaborate and promote visibility," and "Keep it simple and practical."
Culture cannot be installed like software; it must be cultivated through sustained leadership commitment, consistent behavior modeling, and patience measured in years, not sprints.
The culture spectrum in IT organizations
| Culture Type | Characteristics | ITIL Impact |
|---|---|---|
| Blame culture | Errors are punished. People hide mistakes. Post-incident reviews seek fault. | Incidents go unreported. Problem management is ineffective. Innovation is suppressed. |
| Compliance culture | Rules are followed because they must be. Process is an obligation. | ITIL becomes "checkbox theatre." Processes exist on paper but are circumvented in practice. |
| Performance culture | Results matter. Teams compete. Success is rewarded. | ITIL processes adopted when they help, ignored when they do not. Inconsistent implementation. |
| Learning culture | Mistakes are learning opportunities. Knowledge is shared. Improvement is continuous. | ITIL thrives. Continual improvement is genuine. Practices evolve based on evidence. |
| Generative culture | High trust, high cooperation, messengers are welcomed, failure leads to inquiry. | ITIL operates at its highest potential. Value chain and value streams are continuously optimized. |
Target state: A learning or generative culture that aligns with ITIL v5's guiding principles and the Westrum organizational culture model.
The Westrum model and ITIL
The Westrum organizational culture model identifies three culture types:
| Westrum Type | Information Flow | Failure Response | ITIL Alignment |
|---|---|---|---|
| Pathological (power-oriented) | Hidden, distorted | Scapegoating | ITIL will be resisted or weaponized |
| Bureaucratic (rule-oriented) | Follows formal channels | Justice (rules-based) | ITIL will be implemented but not internalized |
| Generative (performance-oriented) | Actively sought and shared | Inquiry | ITIL will be embraced and continuously improved |
Six pillars of culture transformation
Pillar 1: Psychological safety
Definition: People feel safe to take interpersonal risks -- asking questions, admitting mistakes, proposing ideas, and challenging the status quo without fear of punishment.
ITIL connection: Without psychological safety, incident management becomes an exercise in blame avoidance. Engineers hide near-misses. Problems go unreported until they become crises.
Actions:
- Institute blameless post-mortems for all incidents: focus on contributing factors, not fault
- Leaders publicly share their own mistakes and what they learned
- Celebrate "good catches" (near-misses identified before they caused impact)
- Separate incident review (learning) from performance review (evaluation)
Pillar 2: Shared ownership
Definition: Teams take collective responsibility for outcomes, not just their individual tasks or their silo's metrics.
ITIL connection: The value chain and lifecycle model require cross-functional collaboration. If teams optimize only their own stage, value streams break down.
Actions:
- Define shared SLOs that span team boundaries
- Rotate team members through different lifecycle activities
- Celebrate outcomes (customer satisfaction, incident reduction) rather than outputs
Pillar 3: Continuous learning
Definition: The organization systematically learns from experience and applies that learning to improve.
ITIL connection: Continual improvement is a core component of the ITIL Value System. Without a learning culture, the CI register becomes a list of improvements that never get implemented.
Actions:
- Allocate dedicated time for improvement
- Make retrospectives a habit, not an event
- Invest in professional development: ITIL certification, conferences, communities of practice
- Share learnings through internal tech talks, wiki documentation, and improvement showcases
Pillar 4: Transparency and visibility
Definition: Information flows freely. Decisions, processes, and performance data are visible to everyone who needs them.
ITIL connection: The guiding principle "Collaborate and promote visibility" makes this explicit. Value stream mapping is impossible without transparency.
Actions:
- Make operational dashboards visible to all
- Publish incident timelines and post-mortem reports organization-wide
- Share service level performance with customers
- Make the continual improvement register visible to all teams
Pillar 5: Customer empathy
Definition: Every team member understands who their customers are (internal or external) and cares about their experience.
ITIL connection: ITIL v5's emphasis on experience (XLAs) requires teams to think beyond process compliance to actual human impact.
Actions:
- Expose developers and operations teams to customer feedback regularly
- Include customer satisfaction data in team dashboards alongside technical metrics
- Involve customer representatives in service reviews
- Conduct periodic "customer empathy sessions" where teams experience their own services as users
Pillar 6: Leadership behaviour
Definition: Leaders at all levels model the behaviours they expect from their teams.
ITIL connection: Governance is not just structure and policy: it is the visible commitment of leadership to the principles and practices they advocate.
Actions:
- Senior leaders participate in post-mortems (as learners, not judges)
- Leaders publicly acknowledge when a process did not work and commit to improving it
- Management explicitly prioritizes improvement work alongside delivery work
- Leaders measure and are measured by culture metrics (employee satisfaction, psychological safety surveys), not just operational metrics
Measuring culture change
Culture change is difficult to measure directly but can be assessed through proxy indicators:
| Indicator | What It Measures | Measurement Method |
|---|---|---|
| Incident reporting rate | Willingness to report problems | Incident count per service (increasing early on is a good sign) |
| Post-mortem completion rate | Commitment to learning from failures | % of eligible incidents with completed reviews |
| Improvement completion rate | Follow-through on continual improvement | % of CI register items completed on time |
| Employee engagement score | Overall organizational health | Annual or pulse surveys |
| Psychological safety index | Team trust and openness | Team-level surveys |
| Cross-team collaboration frequency | Breaking down silos | Number of cross-functional projects, shared stand-ups |
| Knowledge contribution rate | Knowledge sharing culture | Articles created/updated per team per month |
The transformation timeline
| Phase | Duration | Focus |
|---|---|---|
| Awareness | Months 1-3 | Leaders understand the current culture and commit to change |
| Experimentation | Months 4-9 | Pilot new behaviours in selected teams |
| Amplification | Months 10-18 | Scale successful experiments; address resistance |
| Integration | Months 19-36 | New behaviours become the default |
| Sustain | Ongoing | Continuous measurement and reinforcement |
Culture transformation is a 3-year journey. Promises of culture change in 6 months typically represent training programs, not transformations.
Related pages
Last updated on April 2, 2026
ITIL® is a registered trademark of PeopleCert. © 2026 ITIL v5 Compass