Skip to main content

The Best of Service Operation, Part 2

Tool Selection Criteria
Originally Published on February 1, 2011

Service management technology plays a major role in our support of the business. There are enterprise wide tools that support service management systems and processes. There are also tools which support the specific lifecycle phases.

You should define your process before selecting a tool. Countless organizations have purchased a tool prematurely, only to find that it does not match the workflow of their newly reengineered process. Defining one or more processes first will help to narrow down the requirements and selection criteria and make it easier for the supplier to demonstrate how their product can complement your new process. Match tools to the process, not the other way around.

Wading through all the options, vendors, suppliers can often be a daunting task. Let’s discuss a technique for evaluating tools and finding the product which will support our goals and objectives.
  • What Requirements?
    • Meet with the business, the technical teams, your process owners, and stakeholders to get their input on tool requirements. Use the MoSCoW technique to define your Must Have, Should Have, Could Have, and Want to Have needs. 
  • Identify Products
    • Identify the products which appear to support your requirements.
  • Selection Criteria
    • Put together the selection criteria and prioritize the list.
  • Evaluate Products
    • Review the list of potential products to ensure that they meet the selection criteria. 
  • Short Listing
    • Create a short list of eligible products. If possible, have the tool vendors come in and demonstrate their product to the stakeholders. 
  • Scoring
    • Score the short list of products according to whether they meet requirements, cost, additional features, etc.  
  • Rank the Products
    • Organize your short list of tools in order of preference
  • Select the Products
    • Recommend your preferred tool and obtain approvals to purchase.  Begin to plan the implementation, training, etc.
Most tools are built to be customized to the individual needs of the customer.  Customizing field labels, drop down category lists, reports, views and workflows is expected. However, extensive functional customization can be costly and may hamper your ability to upgrade the product later.  Make sure the tool is not too complicated to use - the goal is to enhance your product, not hinder it.

Finally, deploy tools to match your ITSM maturity. Provide initial and ongoing training of the tools. Monitor data collection to ensure that staff is complying with process policies and procedures.

Comments

Popular posts from this blog

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.”  Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What is the difference between Process Owner, Process Manager and Process Practitioner?

This article was originally published in 2015. With the Introduction of ITIL 4, some of the concepts have changed in ways that are described below. ITIL 4 has also introduced new roles, as explained in our blog ITIL 4 and the Evolving Role of Roles . Before we dive into the difference between these roles, let’s first look at a key update in ITIL 4 – the shift from processes to practices. ITIL 4 has evolved to focus on holistic practices vs. isolated processes. By definition, a practice is a set of organizational resources designed for performing work or accomplishing an objective. For example, the purpose of the incident management practice is to minimize the negative impact of incidents by restoring normal service operation as quickly as possible. All organizations recognize the need to allocate resources to the management of incidents and mature their capabilities in that area. In ITIL 4, each practice includes resources based on the four ...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...