Skip to main content

#SMFlashbook – Best Tip(s) for Building a Service Catalog

Image
By
This blog is being posted today as part of a larger community effort to publish common topic blogs on the same day. I encourage you to review the other blogs on this subject by searching the hashtag #SMFlashbook.

I was simultaneously confused and disappointed by the recent itSMF/Forrester survey results that indicated a large number of organizations had not built a Service Catalog due to lack of funding.    I am also always confused when organizations move forward with their Service Management initiatives without first defining their services. 
So I challenge you with a question:  How can you manage services if you do not have a clear understanding of the services that you provide? 

Here are some very simple and virtually free tips for creating an initial and meaningful Service Catalog:
  • Step away from your tool.   The first steps can be captured on paper, whiteboards or in documents.  The tool part will come later.
  • Gather stakeholders and collectively define and agree on your business services. If you do not know where to start, take a look at your company website or intranet.  In actuality, all businesses or business units only do five things:
o   Acquire or develop a product
o   Market and sell the product
o   Deliver the product (logistics)
o   Support the product
o   Have a corporate infrastructure – HR, IT, Finance, etc.
  • Map the IT Service (s) that underpin each of your business services.  Remember, an app is not a service – one service is likely comprised of multiple applications and infrastructure.  Try to use the same terminology for the business and IT service (e.g., the “Fullfillment Service”)
  • Describe the purpose and use of the service in concise,  business-speak
  • Identify and document the stakeholders for each service
  • Try to define some very generic service levels or service hours for each service
  • Review, agree and publish 
  • If you have a Configuration Management System, you can then replicate this information in a “service CI” record.  The Service CI can then be joined with all of the other  technical and non-technical CIs that contribute to the service.  This allows you to compose or decompose the service  for processes such as Incident, Problem and Change.
It’s too bad that the concept of a Service Catalog (or Service Portfolio) has gained a reputation for being complex and difficult to attain.  In truth, if you follow the above guidelines for defining services, you should not have hundreds of services – some very large organizations only have less than 25.  The difficult part is getting your stakeholders to focus on business services and outcomes, not technical applications and output.  Start simple, stay simple!         

-           
Labels:

Comments

John Wells said…
This comment has been removed by a blog administrator.
October 31, 2013 at 8:14 PM
Post a Comment

Popular posts from this blog

Four Service Characteristics

By
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...
Post a Comment
Read more

What Is A Service Offering?

By
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.      ...
Post a Comment
Read more

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

By
This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...
Post a Comment
Read more