Please enable JavaScript.
Coggle requires JavaScript to display documents.
Celanese ITIL Implementation - Coggle Diagram
Celanese ITIL Implementation
Possible Solutions
Solution 1: Establish an Internal ITIL Coaching Network
Pair experienced “ITILers” with department leads to mentor teams instead of forcing compliance.
Pro: Builds natural adoption through trust and peer learning.
Con: Takes longer to see visible, company-wide maturity gains.
Solution 2: Link ITIL Milestones to Business Outcomes
Tie process improvements directly to measurable results.
Pro: Demonstrates tangible ROI and wins executive backing.
Con: Hard to isolate ITIL’s value amid overlapping initiatives.
Solution 3: Create a Lean Service-Level Framework
Develop 3 to 4 flexible service tiers (Basic, Standard, Critical, High Availability) that scale with the business needs.
Pro: Simplifies communication and sets realistic expectations.
Con: May require overhaul of financial chargeback systems.
Solution 4: Integrate OSM and PMO Checkpoints
Build OSM sign-offs into the PMO’s stage-gate process for new deployments.
Pro: Prevents “go-live and forget” syndrome and enforces readiness.
Con: Adds one more approval layer if not streamlined properly.
Key Problems
Unclear IT Process Maturity
Level 2 maturity (“repeatable”) in HP assessment
Fragmented processes across departments
Lack of standardized documentation
Impact: Inefficiency and inconsistent service delivery
Weak Leadership Support
CIO skeptical of formalized processes
Limited top-down sponsorship
Impact: Inconsistent adoption and cultural resistance
Siloed IT Groups (Apps vs Infrastructure)
Poor communication and coordination
“Thrown over the wall” project handoffs
Impact: Service outages and firefighting culture
No Defined Service Levels
Cost allocation model discouraged SLAs
“Best effort” support expectations mismatched
Impact: Strained IT-business relationships
Timeline
2001 - 2005
Celanese begins integrating IT under a single CIO, standardizing systems, and implementing a global ERP
2006 - 2007
IT demand surges, exposing internal inefficiencies and lack of coordination. HP conducts an ITIL assessment in 2007, finding Celanese at maturity level 2 (repeatable)
2008
ITIL initiatives begin informally within Infrastructure; training programs and process teams form (“ITILers”).
2009
Economic downturn slashes IT budget by 30%; CIO must choose which ITIL projects to support with limited funds
Recommended Solution
(Solution 2)
How?
Pick a Few Key Metrics
: Choose 3 to 5 things to measure, like system uptime, how fast problems get fixed, and how successful changes are. These numbers can show if ITIL processes are actually working.
Match ITIL Goals to Business Needs
:
Every ITIL improvement should have a business purpose. For example, improving Change Management could make project rollouts faster and smoother. Make sure leadership understands how each change helps the company.
Start Small and Show Results
:
Focus on quick wins that can be seen right away like improving response times or reducing errors in one department. Sharing early success stories can help convince leadership to support more ITIL work.
Recognize Good Results
:
When teams show progress using ITIL practices, celebrate it.
Why?
This plan fits Celanese’s culture because it focuses on results, not rules. The CIO and business leaders care about performance and costs, so proving ITIL’s value through real numbers will help gain their trust. It keeps the focus on improving outcomes instead of adding unnecessary steps or bureaucracy.
Expected Benefits?
Leadership will be more willing to fund ITIL because they’ll see real value.
IT teams will have clear goals and know their work matters.
ITIL processes will grow naturally as people see that they actually improve performance.
The company will start seeing IT as a smart business partner, not just a support group.