Planning an ITSM Implementation – A blog on 5 Common Pitfalls to avoid

Projects for IT service management vary in size, the range of activities they involve, and the amount of time and staff they require. Although there won't be any two implementations that are exactly alike, they all aim to accomplish key business objectives. No business has ever implemented ITSM "perfectly." A company eventually acknowledges its errors and concludes its past. There are numerous lessons to be learned in this area because ITSM procedures rely heavily on having access to complete, accurate, current, and integrated data to support operations and decision-making. To make your ITSM implementation more effective and error-free, review these 5 frequent data-related implementation blunders. Regardless of how mature the company is, our experience demonstrates that some issues, errors, and challenges recur.

Pitfall 1: Superficial review of business requirements

The way your firm operates will alter if ITSM is implemented successfully. It is essential to be clear about the difficulties you are now facing, the issues you want to solve, and the expected outcomes. It must be mapped out with a solid commercial foundation. Define how ITSM will directly support, satisfy your requirements, or assist your business in meeting its demands as part of establishing your ITSM deployment plan. Your ITSM endeavor will be more successful if you can connect it to the business' mission, vision, and goals. Many businesses concentrate so much on the technical features of ITSM solutions when drafting an RFP that they overlook the fundamental principles underlying their initial need for the tool. Gartner advises adopting the MoSCoW technique to clarify business requirements and prevent unnecessarily complex checklists rather than gathering a lengthy list of technical requirements from IT stakeholders and associated processes:

M – MUST – a condition that the final answer must satisfy.

S – SHOULD – a top priority that ought to be addressed in the solution, if at all possible.

C – COULD –a desirable requirement that, given enough time and money, will be fulfilled.

W – WON’T –a need that won't be used in a particular release but could be taken into account later.

Pitfall 2: Communication problems

The first step toward executing the new ITSM project is to win support. However, it sometimes happens that the project manager fails to develop a precise communication plan. As a result, it can start internal conflicts or even put the project on hold. Because of this, it is crucial to decide at the outset of the project how the project will be communicated to the management of the organization regarding significant statuses, milestones, and essential information. Business benefit communications are as crucial at this point. To avoid project development stalling, you must be clear about who is in charge of approvals and how to contact them. You should now assess the requirements of every system user without focusing on a specific target audience. Effective communication requires using various strategies and channels, including internal marketing campaigns, mailings, articles on the intranet, information campaigns at work, and even gamification-based employee engagement programs. This strategy can help you achieve your objectives by streamlining collaborative processes and holistic work, all while encouraging transparency and developing trust-based relationships. 

Pitfall 3: No phases of training

Workshops and training on ITSM features (such as ITIL, incident, problem training, etc.) are essential. Why? They link the organization's official job and its broad strategic objectives. People will make decisions based on their experience incompetently if they are not adequately trained. Although that information is valuable, best practices that have previously demonstrated their effectiveness in the sector lead to the possibility of becoming a strategic business partner.

Additionally, management, facilitation of meetings, negotiation, and project management training may be necessary for service and support staff. Because the processes are continually being enhanced, keep in mind that ITSM tools training is not a one-time thing. Both new hires and those who need to brush up on their knowledge should receive it. By supporting tool optimization, the training helps IT users and end users save time, hence boosting their productivity. It might also serve as a source of feedback those results in new company needs. It is an excellent method for getting data from users (both IT and Business). Employees will notice and appreciate that you respect their time and assist them in producing more work if you do it correctly.

Pitfall 4: Ineffective change in management

The management of change is frequently undervalued. This is a factor that many businesses overlook, particularly when changing their ITSM systems. When a company upgrades its platform, it often wants to utilize pre-made solutions and the best practices that accompany them, which necessitates organizational changes. The failure of business leaders to involve managers in implementing, promoting, and facilitating necessary changes is another typical error in change management. We must keep in mind that this is a creative process in which all employees ought to participate because their feedback is crucial. These suggestions should be used when creating future modifications that will lighten your staff members' workloads. For expanding enterprises, implementing a new or replacement ITSM solution can be a huge step forward. Humans naturally resist change, especially if you haven't made your motive apparent or explained the benefits it would bring to your company. Your team needs to become involved for these reasons.

Pitfall 5: Unstable processes

The definition of the group of persons involved in the process and the absence of standardized, documented ITSM processes turn out to be prevalent issues. It is important to establish the responsibility matrix (RACI) right away. By doing this, you will significantly simplify and enhance communication with the implementation partner. A significant problem is the absence of a description of the current system and its integration with other systems. Unstructured processes don't follow a set pattern and can't be predicted in advance. However, that does not imply that they cannot be documented and improved. Unstructured processes rely heavily on information, and the business probably already has a lot of this information (such as documents and emails) stored. For managing unstructured operations, Enterprise Content Management (ECM) modules allow collaboration, data collection, and many more capabilities.


Service management, like so many other IT initiatives, performs best when business requirements shape it, its values are effectively conveyed, there is no long-term hidden technical debt, and it is adequately maintained over time. The ITSM best practices have a track record of increasing customer satisfaction, but if the implementation process is not handled efficiently, things could go wrong. These are just 5 of the most typical ITSM errors and some advice on how to avoid them. However, it is vital to keep this in mind to avoid the common errors mentioned in this article. 

Author Icon