Please enable JavaScript to view the comments powered by Disqus. Top 10 Reasons Why do ITSM Tools Implementation Fails & How to Avoid Them?

Top 10 Reasons Why do ITSM Tools Implementation Fails & How to Avoid Them?

Manish Rathi

Manish Rathi

Last updated 11/10/2019


Top 10 Reasons Why do ITSM Tools Implementation Fails & How to Avoid Them?

ITSM Tools Implementation Fails?

Implementing IT service management (ITSM) in your organization is the most critical activity especially during the transition phase and it decides the future of Managed Services operations team.

 Why do ITSM Tools Implementation Fails

Definition of ITSM Tools failures comes from any of below trigger points

  • A service provider is not able to implement the technical solution within a defined timeline
  • Implemented ITSM Tools solution does not deliver on its promises
  • Cultural adoption of the tools and practices fail.

Let’s get into Top 10 causes why ITSM Tools Implementation fails

 

Over Engineering -

 

 Over Engineering Fails

One of the reasons could be over customization to suit existing processes rather than adopting standards.

 

Lack of Organization Change Management (OCM) -

 Lack of Organization Change Management (OCM)

Change management coverage and training to all stakeholders is not done. Reluctance to follow system processes and prefer to have one on one email or telephonic conversation.

 

Poor collaboration & communication -

 Poor collaboration & communication

user groups are not taken into confidence and all their needs are not addressed. User groups are not made aware of the new features and functionality eventually impacting the adoption. Incomplete user training

 

Poorly designed processes

 Poorly designed processes Fail

eventually resulting in the poor functionality Or even sometimes the tool has too many irrelevant fields from organization perspective which reduces their productivity to log tickets or follow tools

 

Ignoring Heart of ITSM – CMDB -

 Ignoring Heart of ITSM – CMDB

Traditionally most organization start implementing Incident Management/ Problem Management/ Change Management/ Service Request processes without fixing CMDB. CMDB is a heart of ITSM implementation and unfortunately, it is not given due weightage. Lack of clear understanding of business service mappings, Poor CI categorization and CMDB not compliant

 

B2B Integrations -

 B2B Integrations Fail

E-bonding is an overrated concept; an organization which is looking for a robust ITSM tool should discourage this at first place. E-bonding brings in complexity which is difficult to handle. Management of Metadata, as organizations are dynamic, metadata (CTI, Assignment Group, etc) inside it needs to be continuously refreshed, but most organization post-implementation doesn’t take care of it.

 

Lack of following application life cycle

 Lack of following application life cycle Fail

for enhancements in the ITSM tool. Traditionally ITSM tools are managed by Infra teams and they don’t have the expertise to manage the application life cycle.

 

Lack of Focus on Automation-

 Lack of Focus on Automation Fail

Trying to do automation without simplifying the services first and focusing on complex architecture. Handshaking between different tools and services is not taken care of properly

Lack of good functional consultant

 Lack of good functional consultant Fail

who understands the business, end-users expectation, processes and ITSM tool capabilities. The success of ITSM tool implementation is marrying these 4 things.

 

Missing Value Chain -

 Missing Value Chain Fail

  1. The projects fail as we are technical engineering solution architects and we are not used to value chain

Conclusion: 

So to summarize this key reasons includes poor requirements definition, the pressure to go "out of the box," a "lift and shift" mentality, inability to balance time pressure with scope creep, unrealistic expectations, lack of executive support.

Thanks to All Contributors –

Below are the Name Of Subject Matter Experts from Various IT/NONIT Industry they share their thoughts about Why ITSM Tools Implementation Failure.

Manish Rathi, Avinash Sudhakar Kajale, Anupam Sarkar, Krishna Chaitanya Gudimetla, Rohan Kadam, Vikrant Tyagi, Venkataramanamurty Kotra

Topic Related Post

Is ITIL certification worth your time & efforts?
Is ITIL certification worth your time & efforts?
How to implement ITIL?
How to implement ITIL?
What are the Most Common Root Cause of Major Incidents?
What are the Most Common Root Cause of Major Incidents?

About Author

Manish has more than 13 yrs of experience in IT Industry and has worked as ITIL Head with expertise in the areas like Enterprise IT Transformation, ITSM, SIAM, Blockchain.

 
 

SUBMIT ENQUIRY

 
 
 
 
 
 
 

Upcoming Events

ITIL-Logo-BL
ITIL

Every Weekend

AWS-Logo-BL
AWS

Every Weekend

Dev-Ops-Logo-BL
DevOps

Every Weekend

Prince2-Logo-BL
PRINCE2

Every Weekend

Topic Related

Take Simple Quiz and Get Discount Upto 50%
     
   18002122003
 
 
  • Disclaimer
  • PRINCE2® is a registered trade mark of AXELOS Limited, used under permission of AXELOS. All rights reserved.
  • ITIL® is a registered trade mark of AXELOS Limited, used under permission of AXELOS & PEOPLECERT. All rights reserved.
  • MSP® is a registered trade mark of AXELOS Limited, used under permission of AXELOS. All rights reserved.
  • DevOps® is a registered trade mark of DevOps Institute Limited, used under permission of DOI. All rights reserved.