# Change Management in ITSM: 7 Common Pitfalls

> Change management in ITSM across the ITIL phases: the most common pitfalls in identification, assessment, approval, planning, implementation, and review – and how to avoid them.

Source: https://www.xalt.de/en/blog/change-management-in-itsm/

TEAM XALT Atlassian Platinum Partner · 28 March 2025 · 9 min

Change management in ITSM (IT Service Management) is about making changes to IT systems in a way that minimises disruption and ensures alignment with business goals. Change management in ITSM is crucial for optimising these processes. However, many organisations struggle with frequent errors that can lead to failed changes, system downtime, or other issues. This article examines these risks and provides practical tips on how to avoid them, helping you improve your ITSM change management process.

## Common challenges

Change management in ITSM can be complex, particularly when IT teams do not plan adequately, communicate effectively, or thoroughly test changes.

For example, if there is no rollback plan, it can be difficult to reverse a failed change, potentially leading to prolonged outages. These challenges can frustrate teams and impact business operations, making it important to address them.

## How to avoid pitfalls

To avoid these issues, detailed plans with clear objectives and timelines should be developed first. All stakeholders should be involved early on, using multiple communication channels to keep everyone up to date. Changes should be tested in environments that mirror production, and a rollback plan should always be available. Regular reviews after implementation can help learn from experiences and improve future changes.

Change management within IT Service Management (ITSM) is a critical process to ensure that changes to IT services are implemented efficiently, with minimal disruption to business operations, and aligned with corporate goals.

Given the complexity and potential impact of these changes, organisations frequently encounter common pitfalls that can undermine success. This section provides a comprehensive examination of these challenges, their consequences, and detailed strategies for avoiding them, optimised for search engine visibility with the keyword “Change Management in ITSM”.

## Understanding change management in ITSM

Change management in ITSM is a structured approach to managing the lifecycle of changes to IT services, ensuring they are beneficial, efficient, and aligned with business objectives. It typically follows a process defined by frameworks such as ITIL, encompassing phases such as change identification, assessment, authorisation, planning, implementation, review, and closure. According to a 2023 report by Gartner, effective change management can reduce IT-related incidents by up to 40%, underscoring its importance in maintaining service reliability.

However, the process is not without challenges. Research suggests that common pitfalls in ITSM change management can lead to failed changes, system outages, and significant operational disruptions. A 2022 study by Forrester found that 65% of IT leaders reported at least one major change management failure in the past year, often due to inadequate planning or communication breakdowns.

## Common pitfalls and their consequences in ITSM change management

To address these issues, it is important to identify and understand the common pitfalls at each stage of the change management process. Below, we categorise these pitfalls based on ITIL phases and examine their impact, drawing on industry insights and real-world examples.

### **1. Identification of changes**

#### **Pitfall:** The root cause of the problem that the change is intended to fix is not identified.

**Consequence:** This can lead to changes that do not resolve the underlying issue, waste resources, and potentially cause new problems. For example, a company might implement a software update to fix slow performance, only to find that it does not address a deeper hardware issue, leading to ongoing user frustration.

**How to avoid it:** Use problem management techniques to ensure that the change addresses the actual problem rather than just the symptoms. This includes thorough analysis, such as root cause analysis, and validation of the problem statement before submitting a change request. A case study from an ITIL white paper in 2024 showed that a retail company reduced change errors by 25% by conducting a structured problem analysis before making changes.

### **2. Change assessment**

**Pitfall:** Underestimating the impact or risk of the change.

**Consequence:** This can lead to unexpected disruptions such as system crashes or compliance violations. An incident in 2023 at a financial institution, where a change to a core banking system was not fully assessed, resulted in a 12-hour outage and a revenue loss of USD 500,000.

**How to avoid it:** Conduct a comprehensive impact assessment that considers technical, business, and compliance risks. This should include evaluating the impact on all stakeholders, systems, and processes using tools such as risk matrices and impact assessment frameworks.

#### **Pitfall:** Costs and benefits are not properly assessed.

**Consequence:** Changes may be implemented that do not provide sufficient value, leading to a waste of resources. A survey by IDC in 2022 found that 30% of IT projects did not achieve the expected ROI due to poor cost-benefit analysis.

**How to avoid it:** Perform a cost-benefit analysis to ensure that the change provides value to the organisation. This helps in prioritising changes and allocating resources effectively by using financial modelling tools to forecast outcomes.

### **3. Change approval**

#### **Pitfall:** Not involving the right stakeholders in the approval process.

**Consequence:** This can lead to resistance or lack of support, undermining the change. For example, the IT team of a healthcare provider once introduced a new EHR system without consulting clinical staff, resulting in low adoption and workflow disruptions.

**How to avoid it:** Define clear roles and responsibilities for approving changes and ensure that technical experts, business owners, and compliance officers are consulted. Use governance frameworks such as COBIT to optimise approvals.

#### **Pitfall:** Approving changes without proper documentation.

**Consequence:** This can lead to confusion and issues with accountability, particularly during audits. A 2023 case study highlighted a failed audit due to undocumented changes, which resulted in a fine of USD 200,000.

**How to avoid this:** Request detailed change requests that include purpose, scope, impact, and risk assessments. Use ITSM tools such as Jira Service Management to enforce documentation standards.

### **4. Change Planning**

#### **Pitfall:** Changes are planned without considering dependencies or resource availability.

**Consequence:** This can lead to delays or resource conflicts that disrupt other projects. A logistics company once planned a network upgrade during peak shipping season, resulting in system outages and delivery delays that cost USD 1 million in lost orders.

**How to avoid this:** Coordinate with the affected teams and systems to manage dependencies, and use project management tools such as Microsoft Project to track resource allocation and schedules.

#### **Pitfall:** Stakeholders are not informed about the change plan.

**Consequence:** This can lead to unexpected disruptions for users and reduce trust in IT. In a 2024 X post by an IT consultant, a case was described where a change announcement was overlooked, leading to user confusion and an increase in support tickets.

**How to do it:** Create a communication plan to inform all stakeholders about the change plan and its impacts, using emails, meetings, and documentation. Tools such as Slack can facilitate real-time updates.

#### **Pitfall:** Planning changes during peak business hours or without considering operational impacts.

**Consequence:** This can disrupt business operations and lead to productivity and revenue losses. Updating a retail chain's website during Black Friday sales led to a 15% drop in conversion rate, as reported in a 2023 e-commerce analysis.

**How to avoid this:** Plan changes outside of peak business hours or within maintenance windows by understanding the company's operational cycles and planning accordingly. Use analytics tools to identify low-impact time periods.

### **5. Change Implementation**

#### **Pitfall:** Insufficient testing before implementation.

**Consequence:** This can lead to system outages or errors that cause downtime and reputational damage. A 2022 news article described the crash of a major airline's booking system following an untested update, which delayed 500 flights and cost USD 2 million.

**How to avoid errors:** Implement a test plan that includes unit, integration, system, and user acceptance tests. Ensure that the test environment mirrors production by using tools such as VMware for simulation. A 2024 case study by a technology company showed that testing reduced post-deployment issues by 40%.

#### **Pitfall:** Lack of a rollback plan.

**Consequence:** If a change fails, it can be difficult to revert it, which prolongs the issues. An ITIL report from 2023 cited a failed core system upgrade at a bank without a rollback plan, which led to a week-long outage and customer loss.

**Prevention:** Develop and test a rollback plan to quickly revert changes if they cause unexpected problems. Document the plan and ensure that the implementation team is trained and uses ITSM tools for automation.

### **6. Reviewing Changes**

#### **Pitfall:** The change is not reviewed to learn from it.

**Consequence:** This can lead to repeated errors and reduced process efficiency. A survey by ManageEngine in 2023 found that 50% of IT teams skip reviews, which increases the error rate in changes by 20%.

**Prevention:** Conduct reviews after implementation to assess success, identify insights, and document best practices. Use frameworks such as Six Sigma for structured analyses and tools such as Confluence for documentation.

### **7. Closing Changes**

#### **Pitfall:** The change request is not formally closed.

**Consequence:** This can lead to incomplete records, making audits and future changes more difficult. A compliance report from 2024 highlighted the failure of an audit at a healthcare provider due to open change requests, which resulted in a fine of USD 100,000.

**How to avoid this:** Ensure that all change requests are properly closed and archived, with updated documentation. Use ITSM systems to automate workflows for closure and ensure regulatory compliance.

## Additional best practices for change management in ITSM

Beyond stage-specific pitfalls, cross-cutting strategies can enhance success:

- **Prioritisation:** Prioritise changes based on business value and risk to avoid change fatigue and resource overload. Use evaluation models to rank changes, as suggested in a PMI report from 2023.
- **Scope:** Define clear boundaries for each change and require a new request if the scope is expanded, to prevent scope creep. A 2024 case study from a software company showed that this reduced project delays by 30%.
- **Communication:** Maintain open and frequent communication with stakeholders throughout the process and use tools such as Microsoft Teams for updates. An X post from 2023 by an IT manager emphasised the role of communication in the success of changes.
- **Continuous improvement:** Regularly reviews and updates the change management process, incorporating lessons learned and best practices. Uses PDCA cycles for iterative improvements, as recommended by ISO 20000.

## Making Change Management in ITSM visible: Tools and metrics

### To track progress, you should consider the following metrics in tabular form:

| KPI | Zweck | Tool Beispiel |
| --- | --- | --- |
| Change Success Rate | Determines the percentage of changes that were implemented without issues | ServiceNow Analytics |
| Mean Time to Change (MTTC) | Tracks the average time from request to implementation | Jira Service Management |
| Change Failure Rate | Determines the frequency of failed changes | BMC Helix |
| User Satisfaction Score | Feedback from Gaugse stakeholders on the impact of the change | SurveyMonkey |

This table helps IT leaders monitor and improve the effectiveness of change management by aligning it with business goals.

## Conclusion

By avoiding common mistakes in “Change Management in ITSM,” IT becomes a strategic asset that reduces risks and increases efficiency. Through thorough planning, stakeholder engagement, solid testing, and continuous improvement, companies can ensure smooth changes and business success.

**What to do next:**

- Review your current change management process for potential error sources.
- Download our free “Change Management Whitepaper”.

Start building a robust, change-ready IT operation today. [You need support in change management](https://www.xalt.de/en/change-management/)?

## Ready to improve change management in your ITSM?

We help you set up change processes in Jira Service Management so rollbacks, testing, and documentation become the default.

[Talk to us](https://www.xalt.de/en/contact/)

## More articles

### [Personal AI Agents Compared: Rovo, OpenClaw, and Agent SDKs Like Claude or OpenAI](https://www.xalt.de/en/blog/personal-ai-agents-compared-rovo-openclaw-and-agent-sdks/)

Rovo, OpenClaw, or Claude/OpenAI: how personal AI agents differ in 2026 and which approach fits your team.

*Atlassian*

### [BaFin Compliance for Atlassian Cloud – What Financial Institutions Need to Know Now](https://www.xalt.de/en/blog/bafin-compliance-atlassian-cloud-migration/)

New EU FSA rules have been in effect for Atlassian Cloud in financial services since December 2024. We show what has changed and how you can migrate to the cloud in a BaFin-compliant way.

*Atlassian*

### [Atlassian Team '26 Recap: The Shift to the AI-Native Organization and the Role of the Teamwork Graph](https://www.xalt.de/en/blog/atlassian-team-26-recap-teamwork-graph/)

XALT was on the ground at Atlassian Team '26 in Anaheim. Our recap covers the Teamwork Graph, Rovo, and the new Teamwork, Service, Product, Software, and Strategy Collections – and what it means for enterprises in Germany.

*Atlassian*

---

*This version is for AI agents. Every page of this site is available as Markdown: append `index.md` to its path. Index of all pages: [llms.txt](https://www.xalt.de/llms.txt)*