Service Catalog Best Practices - Retire services properly — notify users, redirect requests, remove cleanly
Service Catalog Best Practices
Retire services properly — notify users, redirect requests, remove cleanly
Overview
Service retirement is frequently treated as an afterthought. Services are removed suddenly, without notice, leaving customers confused and fulfillment teams fielding complaints. Poorly managed retirements damage customer trust and create operational disruption that is entirely avoidable with proper planning.
Best Practice
Treat every service retirement as a managed transition, not a deletion event. Before retiring a service, identify all active users and notify them with sufficient lead time to adjust. If a replacement service exists, communicate clearly what it is and how to request it. Redirect any in-flight requests to the appropriate alternative. Remove the service from the active catalog only after the notification period has passed and all outstanding requests have been resolved.
Benefit(s)
A well-managed service retirement process preserves customer trust even in the face of changes customers may not welcome. Customers who receive advance notice and clear guidance feel respected and informed. The catalog remains trustworthy because customers know that when a service is available, it is genuinely available — and when it is going away, they will be told in advance.
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers