Well, ITSM it’s not you…it’s me. When ITIL failure causes you to point fingers, it may be time to dig a little deeper and find the real heart of the issue. It’s not uncommon to go through rough patches in your ITSM relationship. In fact, a Forrester study claims that 52% of ITIL programs fail because of resistance. What kind of resistance? Paul Wilkinson of BSMReview.com breaks it down into 10 common problems.
- No commitment from management
- Saying “Yes” to adopting new procedures, but meaning “No”
- Treating ITIL as an achievement instead of an objective
- Not understanding that ITIL is a continual process, not just a project
- Unwillingness to change procedures
- Not believing that ITIL will work for your organization
- Introducing ITIL procedures but not teaching people to apply them
- Thinking ITIL doesn’t need to understand the business
- Inability to specify the value required by the business
- Not understanding where your priorities lie
Resistance comes in many shapes and forms, but that’s no reason to end the relationship. It’s time to tell your ITSM, “It’s not you, it’s me,” and work on improvements from there.