Post-Merger IT Service Integration
A mid-sized logistics company acquires a regional competitor. The two IT organizations use different service management tools, different incident severity definitions, and different supplier contracts. The acquired company has no formal problem management; the acquiring company has a heavy change process. Staff are anxious about redundancies. Customers have experienced duplicated incident communications and conflicting SLAs. The CIO wants to integrate IT services within 12 months while preserving service quality and avoiding a culture clash. There is no shared service catalog. The integration team has representatives from both sides but no agreed principles. One supplier contract has a 6-month exit clause; the other has 18 months. The CIO asks for an approach that stabilizes services first and then improves them.
1. Apply the ITIL 4 guiding principles to recommend how the integration should be approached. Give specific examples for at least four principles.
Read the worked answer
Focus on value: define value from customer outcomes: reliable deliveries, single incident communication, and consistent SLAs. Do not start with tool consolidation for its own sake.
Start where you are: reuse the acquiring company’s incident severity model and the acquired company’s agile problem-solving habits. Assess both before designing a new model.
Progress iteratively with feedback: run a 90-day stabilization pilot for one region or customer segment; gather feedback before scaling. Integration in 12 months should be a series of iterations, not a big bang.
Collaborate and promote visibility: create a joint integration team with decision rights, a single communication channel, and shared dashboards. Include staff from both sides in service catalog design.
Keep it simple and practical: create a minimum viable service catalog and a single severity scheme first; refine later.
Optimize and automate: consolidate monitoring and ticketing only after processes are agreed.
Reasoning: These principles prevent a politically driven merger that ignores service reality. Starting where you are reduces risk and respects both cultures.
2. Use the four dimensions of service management to identify the key integration risks and actions.
Read the worked answer
Organizations and people: risk of culture clash, redundancy anxiety, and unclear roles. Action: transparent communication, retention of key staff, joint governance, and role mapping.
Information and technology: different tools and data models; risk of losing incident history and misreporting. Action: data mapping, interim integration, single source of truth for incidents, and tool consolidation after process alignment.
Partners and suppliers: contracts with different exit clauses and SLAs. Action: inventory contracts, align SLAs, plan the 6-month and 18-month exits, and manage supplier relationships jointly.
Value streams and processes: different severity definitions, no shared catalog, and no formal problem management. Action: harmonize incident severity, create a minimum service catalog, introduce problem management as a pilot, and align change processes proportionately.
Reasoning: Integration fails if it is treated as only a technology project. The four dimensions expose people, supplier, and process risks that must be managed in parallel.
3. What should be included in the first 90-day plan to stabilize services and build trust?
Read the worked answer
Weeks 1–2: establish a joint integration office with clear decision rights; agree a single incident communication protocol; publish a temporary severity matrix.
Weeks 3–6: create a minimum service catalog for top customer-facing services; map supplier contracts and SLAs; stand up a single incident bridge for major incidents; start a joint problem management pilot for recurring incidents.
Weeks 7–12: run a service review with customers; measure incident volume, major incident MTTR, duplicated communications, and SLA breaches. Communicate quick wins. Begin role mapping and cultural listening sessions. Prioritize the first three integration improvements by value and risk.
Trust-building: visible leadership sponsorship, transparency about redundancies, and honoring commitments. Use guiding principles: start where you are, collaborate, and progress iteratively.
Reasoning: Stabilizing communication, severity, and major incident handling reduces customer harm immediately. Trust comes from consistent action, not from a 12-month target.