How do I create a service catalog?
Create it from scratch in four phases.
During interviews with each service team, identify products and services that are already in use. Record the responses in a table categorized by product and service.
Helpful open-ended interview questions include:
For each product, document which aspects are business-critical and which are not, as well as which requests are made frequently and which are made rarely. This information will help with prioritization in the further course of action.
This realistic overview provides:
Provide details about the service offerings and how they will be delivered. You can invest the most effort in this phase. Initially, however, only carry this out for business-critical and frequently requested services.
During individual workshops with each service team, document the information required to process requests and their procedural flow.
Refrain from creating elaborate process flowcharts. Instead, use BPMN (Business Process Model and Notation), which is easy to read and standardized.
The input is the information required for processing, and the output is the delivery of the service offering.
Good design means: “As lean as possible, as robust as necessary.”
For each service offering, clarify who is authorized to use it, who needs to approve it, and who is responsible for the costs.
The documentation from the design phase forms the basis for subsequent implementation in a service management tool.
You can implement the service catalog and request forms either yourself in central software or by handing over the documentation to the responsible team or an external partner.
In any case, log each service offering as a work package to maintain an overview and report on implementation progress. For this purpose, a task or project management tool is recommended.
Before activating the implementations in the software for users and communicating them as a success within the company, have the service teams thoroughly test and confirm them.
Implementation delivers several benefits:
This final phase begins several weeks or months after implementation. Analyze the collected data by service and visualize it as a Pareto chart. This allows you to see which services are being used and which are not yet standardized.
The former represent automation potential. You will evaluate the latter with the service team before adding them to the design phase as new service offerings, which will then be scheduled for implementation.
You have now reached the Continuous Service Improvement (CSI) phase and significantly increased the maturity level of your services.
Congratulations! You have arrived at Service Management:
Users perceive efficient services as “good” when they are clearly described and linked to well-structured requests from forms and workflows. This ensures repeatable and predictable delivery.
RYOSHI is happy to support you in building and implementing your service catalog. We are independent and methodologically sound, delivering added value without burdening you.
Read our related blog article on this topic:
RYOSHI is the pioneer of Lean ITSM and Six Sigma for IT.
Schedule an introductory meeting today.