Service catalog items are the forms users fill in to ask for something: a laptop, software access, or a new account. Behind each form sits a workflow that routes the request, collects approvals, and creates tasks for the teams that fulfil it. The form and the workflow are a pair. Change one without the other and requests break in confusing ways.
The pieces in order
- Variables collect the information, such as device type or access level, and should ask only for what fulfilment needs.
- Approval rules decide who must agree, and should point at roles or groups rather than named individuals.
- Catalog tasks break fulfilment into steps, each assigned to the team that can actually do that step.
- Notifications keep the requester informed at each stage, so they stop raising duplicate requests.
When designing a catalog item, walk the request yourself from submission to delivery. Every step where you hesitate is a step users will struggle with too.