1. Multiple levels of approval for all tickets
Is your service management system up to scratch? When a ticket comes in, where does it go first and how many people does it go through before the issue is fixed? As tickets get sent through multiple ‘tiers’ resolution time is increased, and often information is lost along the way.
Organisations that are leading at customer service are able to resolve tickets both quickly and to a high standard. With a fixed hierarchy this is much harder to achieve.
2. ITSM processes that suppress collaboration
When your teams and individuals have fixed job responsibilities and strict task lists, it often leads to siloed teams that each have a narrow focus.
When individual teams are only working within their specific sections of the organisation, this prevents regular communication with other departments across the business. Therefore, a single team may not have enough context when trying to resolve tickets.
Without the right context, issues may take longer to fix. By not having the full picture, the solution might not be the right one for that particular customer.
3. Use of legacy, not fully fit-for-purpose ITSM tools
Legacy ITSM tools are often more rigid and harder to customise. When you’re trying to adapt to the changing market—which is essential for modern ITSM—using old and inflexible tools can provide many blockers.
The other main issue with many legacy ITSM tools is that they won’t usually link up with the tools your developers are using. This means there is an extra step before the ticket can be added to the developer backlog.
As tickets are moved between programs, visibility can be lost and the customer is left waiting for a resolution.