Comparaison des fournisseurs ITSM

7 Success Factors in Choosing an ITSM Tool

Blog
by Benoit Lévesque - 
September 21 2019

IT management is now essential. The information technology department is now central to business operations efficiency. Over the years, its stakeholders have transformed this cost centre into a revenue generator and a catalyst for the customer experience.

This digital transformation does not only bring its share of benefits and productivity, but also its challenges. IT Service Management (ITSM) and request management across the whole organization is no exception.

Through your quest for performance and the search for a new service desk tool (also known as a ticketing tool, helpdesk, management of IT services or IT support centre), some missteps can lead you to a wrong decision.

Below are some tips below to get you to the right place and ultimately, to help you make the best possible choice.

 

All ITSM and service desk options are not the same

All software, paid or free, are obviously not equal. Basic or advanced functions sometimes differ and this is where the first mistake lies; looking for software first.

Too often we discuss ITSM initiatives and we are told, "I am looking for a help desk software, I have $ 30,000 in the budget (budgeted or in my budget) and I want to install everything on the cloud.” However, this research should be based on issues that can be grouped into 4 blocks:

  • Consolidate and optimize critical business processes
  • Automate and simplify routine tasks
  • Make informed and measured business decisions
  • Satisfy its users by offering quality services

 

So, what elements do I prioritize in finding the perfect solution?

 

1. Measure the maturity of your processes: find the right "fit"

A first success factor for choosing the right ITSM system is to evaluate the maturity of your processes - or even if it is not in place - to model at a minimum the processes you want to support through a ticket office. Drawing on a napkin, does that tell you something? Joking aside, try modeling on Visio or another digital tool instead.

Implementing a service management system usually requires a structured, robust and reliable approach. By cons, any system is not for any organization and / or business context. You must find the right "fit".

You most likely have a list of requirements, with your essential needs and your "nice-to-have" requirements. These elements leads you to validate this list with suppliers.

A good exercise in determining the maturity of your processes is the model of Axelos, owner of the ITIL® brand. This type of exercise leads you to evaluate the next steps of your project with a strategic and tactical perspective to reach your goals.

These are the milestones in your continuous improvement roadmap - and yes, even after the implementation, an ITSM solution is continually evolving.

 

2. Determine if ITIL® framework is right for you

The IT service management practice is framed by good practices and industry-specific standards.

The first version of ITIL® was published by the Central Informatics and Telecommunications Agency in the early 1980s. It was developed as a set of standards aimed at improving IT performance. The standards were adopted in subsequent years by governmental and non-governmental entities. As standards grew in popularity, several versions (ITIL® V2, ITIL® V3) were released. The most recent version was published in 2011: ITIL® 2011. In 2014, the ownership of ITIL® was transferred to Axelos, a professional services company based in the United Kingdom. The ITIL® ITIL® 2011 processes are grouped into 5 separate publications: Service Strategy, Service Design, Service Transition, Service Operation, and Continuous Service Improvement.

List of ITIL® processes :

  • Access management
  • Availability Management
  • Capacity Management
  • Change management
  • Continuous improvement of services
  • Demand Management
  • Coordination of the design
  • Event Management
  • Financial management
  • Incident management
  • IT Service Continuity Management
  • Information Security Management
  • Knowledge Management
  • Problem Management
  • Versioning and Deployment Management
  • Request for fulfillment
  • Supplier Management
  • Service Asset Management and Configuration
  • Service Catalog Management
  • Service Level Management
  • Service Portfolio Management
  • Management Strategy for IT Services

Other recognized standards are also used in business, such as COBIT, Six Sigma, ISO 20000, TOGAF and, FitSM.

 

3. Flexibility or template-only? Think long term.

Even if the "On Premise" era and modular legacy-type software are less popular, you need to think about the functional flexibility your team is looking for. If you have NO resource to allocate to the ITSM implementation project or if the scope of the project is very limited, you may rely on a rigid tool where templates are available to you at a low price.

Be careful, this path is sometimes the right one, but can limit your future initiatives. Keep in mind your business moves and evolves, just like your processes and your projects in supporting users.

Do not hit a wall with a short-term bet and a simple request management system.

On the other hand, a flexible tool gives you the potential to start in phases and to scale processes, one priority at a time.

 

4. Is your project built for IT needs only?

When talking about service management process, no need to limit to computers or technology. Yes, a helpdesk is known as a tool dedicated to information technology and IT support centres, but it is not the case anymore. The notion of "tickets" remains, but the tools capabilities go much further than just "ticketing" management.

A visionary service management project potentially includes the services of the entire organization and its needs, which can be detailed through a service catalogue. Your requests can come from human resources (arrival of an employee, request for access) or from procurement (approval for an equipment purchase) or legal processes (request for a lost object or a cancelled service). We are now talking about Business Service Management or Enterprise Service Management to describe the scope of service delivery within the organization.

If your future ITSM project does not include your business services, ask yourself if you could benefit from the involvement of your colleagues from other departments. These allies can provide you even more ammo to advance your project.

 

5. Expert comparisons are complimentary. Trust the real users first.

Reports and comparisons of all kinds often show different results. Or at best these documents do not show all the options on the market. Make sure that the information retained for your short list of suppliers comes from real customers and not from reclusive or niche analysts.

These large audits are certainly relevant but are more appropriate for very large companies. For SMEs and mid-sized companies wanting to move to the next level, these valued and expensive reports do not present you with all the options. Even less viable options aligned with your budget and your needs.

Take a look at the recent Software Reviews report, which includes the opinions of more than 700 ITSM users and administrators.

 

6. Beyond the supplier, choose your business partner.

Although it may sound a little cliche, the importance of this point can not be underestimated. You do not just choose an IT service management tool; you choose a partner with whom you do business, hopefully for many years. It is important to ensure that the supplier meets its commitments.

An excellent way to evaluate this is to examine a supplier's ability to meet its product roadmap schedule. Unfortunately, a supplier's commitment to you may vary depending on the size and scale of your organization. 

However, an SME or an organization that does not have a well-known brand often does not attract the same attention, especially among large ITSM tools providers that focus on the enterprise space. If you are a small organization, be sure to talk to references or peers with the same organizational profile as yours. For example, a government agency or educational institution will have very different needs from those of a pharmaceutical company, a manufacturing distributor or a financial services organization.

The location - or at least the proximity of service - of your partner is also a factor of success. His ability to speak your language, understand the specifics of your requirements and especially, those of your business reality is decisive.

Doing business directly with an editor can make all the difference. Take the example of a reseller or an? integrator of an ITSM system that fails to include a critical requirement or mishandles customer improvement requests; these errors can affect the project's progression.

 

7. License Types and Options

Several types of licences are offered. Named, floating, role-based, etc.

Some will offer you integrated models and other modular solutions. No matter which avenue you choose, the licence is only part of your investment.

The deployment of the solution, the production and test environments, the training of the users and your administrators are all points to evaluate for a successful implementation.

Especially since with the arrival of the cloud, things have changed. In the past, you invested in perpetual licences and installed on your infrastructure. Now you can evaluate strong cloud options and choose a solution that will follow your maturity and improve your ITSM processes.

In short, beware of the hidden costs that never stop accumulating. Do business with a real software provider and avoid "service specialists".

 

What to look for in an ITSM solution?

Now that you have considered the maturity of your IT processes, the tools in place, the discussions with industry experts, etc., it's time to think about the features. Each solution will offer a variety of features and capabilities. By understanding your specific needs, as outlined in the seven steps above, you are better equipped to find the best solution for your business. Things to consider include:

  • Support for the processes and framework of best practices that your organization will implement, such as ITIL incident, problem, and change management.
  • Ability to automatically assign tickets according to specialization or skills.
  • Integration or support of asset management to track, manage and maintain IT assets, including software and software licenses.
  • Ability to change deployment model (onsite to cloud or vice versa) if your business needs change.
  • Supports integrations with third-party solutions that your business relies on, such as asset management, remote management, mobile device management, and authentication.
  • The ease with which you can configure and modify without the need for expensive programmers (fast setup with minimal overhead).
  • Dashboards, statistics and real-time and dynamic reports.
  • Support the migration of data from existing tools and solutions to the new ITSM solution.

 

Ready to start your solution search?

Use this list of vendor-neutral questions in this downloadable document. It will help you stay organized and solicit suppliers according to your needs.