Despite being a critical element of many processes, a service catalog can be difficult to implement. Many service catalog projects underestimate the effort or leave out critical components. These result in systems or documents that languish on the shelf and have little or no use. Often, the focus of the project is on the activity or the specific technology and not the intended business use, leading to a lack of adoption by the business. In a recent survey, only 57% of respondents characterized their service catalog implementations as successful.
So, what can be done to ensure your service catalog project is not one of those left on the shelf? Our experience across many large and small service catalog implementations shows the keys to success lie in four domains:
Implementation: There are some common pitfalls during the initial implementation that can easily be avoided.
This article explores each of these areas listing five key insights, or top tips, to keep in mind when building your service catalog.
Motivation: Why implement a service catalog?
For any project to be successful, stakeholders need to know why the project is being undertaken and have a common vision of the goals. Here are the key reasons both IT and the business will benefit from the service catalog:
Brings IT closer to the business Until you start to define what you do in terms that the business can understand and align yourself in a way that clearly supports what the business does, you are still in a technology silo and not doing real service management.
Serves as the backbone for service management Service catalogs provide the cornerstone for virtually all of the ITIL processes you might implement. They help the different processes organize and prioritize their time and ensure their efforts are tied to services that directly contribute to the business.
Optimizes investment Efficiency is all about getting value for your money. Without defining your services through the eyes of the business, it is almost impossible for IT to ensure they are spending money on the things most important to the business. Similarly, without an understanding of costs, the business is not able to make informed decisions about usage.
Creates a baseline for SLAs, OLAs and underpinning contracts A robust service catalog provides necessary context for defining performance measures to end users, between supporting services, and between the service and the external third party providers. Gathering performance information for the service also provides a substantive starting point for negotiating and agreeing more formal SLAs and OLAs.
Serves as marketing tool Too often service catalogs are developed without the customers involvement, or they are allowed to sit on the shelf rather than being promoted and marketed throughout the organization. A service catalog should be a key to bringing IT and the business closer together. There is a limit to how much silent running the business will accept; some visibility of IT through the service catalog helps to reinforce the value of IT.
Design: Five tips for designing service catalogs
A good design will make sure the catalog meets the customers needs and build in flexibility so it will endure. Here are our five top tips for creating an effective design:
Focus on what your customers want Even if you start by documenting the technology services that make up the building blocks of the service catalog, you need understand what is most important to your customers. The catalog should reflect how they operate the business including the potential for different tiers of service aligned with different customer needs and segments.