ITIL Service Catalogue Management and Service Design: From Idea to a Usable Service
Users cannot ask for what they do not know exists, and a service that is badly designed will cause incidents for years. Two related practices address these needs. Service catalogue management provides a single source of consistent information on all services and service offerings, and ensures it is available to the relevant audience. Service design designs products and services that are fit for purpose, fit for use and able to be delivered by the organisation and its partners.
What Is a Service Catalogue?
A service catalogue lists the services the provider offers, in language the audience understands. It usually has more than one view:
| View | Audience | Content | Example |
|---|---|---|---|
| Business (customer-facing) catalogue | Users and customers | Services as they experience them, with descriptions, hours, cost and how to request | “Email and Calendar”, “Remote Access”, “Employee Onboarding” |
| Technical (supporting) catalogue | IT staff | Components and teams that support each service, with dependencies | Email depends on mail servers, identity service, network |
| Request catalogue | Users | Specific requests users can submit, with forms and expected delivery times | “New laptop”, “Shared mailbox”, “Software install” |
The request catalogue connects directly to Service Request Management; the technical view connects to Service Configuration Management and the CMDB.
What Each Catalogue Entry Should Say
- A plain-language name and short description of what the service does.
- Who can use it and who owns it.
- Hours of availability and support.
- Service levels, or a link to the SLA (see Service Level Management and SLAs).
- How to request, report a problem or get help.
- Costs or charging, if applicable.
- Dependencies on other services and suppliers.
Common Catalogue Problems
- Technical language: “Active Directory account provisioning” instead of “New user account”.
- Too many items: users cannot find anything. Group them and make search work.
- Out-of-date entries: retired services still listed, new ones missing.
- No owner: nobody is accountable for each entry.
Service Design: Beyond the Technology
Service design practice considers the whole service, not only the technical solution. Designers ask:
- Who will use this, and what are they trying to achieve?
- What is their journey from first need to finished outcome?
- What must the service do (utility) and how reliably (warranty)?
- How will it be supported, measured and improved?
- How will it affect the four dimensions (see The Four Dimensions of Service Management)?
Design Tools
| Tool | Use |
|---|---|
| Customer or user journey map | Shows each step the user takes, with feelings, pain points and moments of truth |
| Personas | Short descriptions of typical user types to keep design focused on real needs |
| Service blueprint | Shows what the user sees (front stage) and the processes, systems and people behind it (back stage) |
| Non-functional requirements | Capture availability, performance, security, capacity and recoverability needs |
| Prototype or pilot | Tests the idea with real users before full build |
Design Considerations Checklist
- Experience: is it easy to find, request and use?
- Availability, capacity and continuity requirements agreed (see Availability, Capacity and Service Continuity).
- Security and privacy built in from the start.
- Support model, knowledge articles and training ready before launch.
- Monitoring and metrics designed in.
- Supplier roles and contracts clear.
- Cost and benefits understood.
Worked Example: Designing a Remote Working Service
A company wants to offer a “Remote Working” service. The designer interviews employees and drafts a journey: request equipment, set up access, connect, collaborate, solve problems, return equipment. Pain points emerge: new starters cannot join the VPN before their laptop arrives, and home-office faults have no clear owner. The blueprint shows which back-stage teams are involved. The design includes a pre-configured laptop bundle, a self-service guide, a support route for home-office issues and an availability target of 99.5% for the VPN. The catalogue entry is written as “Work from Home Kit and Access” with one request form, and the team pilots it with 50 staff before releasing it.
Common Mistakes
- Designing from the provider’s point of view instead of the user’s.
- Treating the catalogue as a one-off document instead of a living list.
- Leaving support, training and monitoring until after launch.
- Skipping a pilot and discovering design flaws in production.
- A service catalogue is a single, consistent source of information about services, usually with business, technical and request views.
- Write entries in the user’s language, with owners, hours, service levels and how to request.
- Service design considers the whole experience: journey, utility, warranty, support and measurement.
- Use journey maps, blueprints and pilots to find problems before launch.