Service Design and Transition
Designing services that hold up
Service design turns strategy into a service blueprint that is usable, reliable, and supportable. The classic design dimensions are utility and warranty, plus the "four Ps": people, processes, products (technology), and partners (suppliers). Design must cover not just the live service but the service level agreements (SLAs), operational level agreements (OLAs) between internal teams, and underpinning contracts (UCs) with external suppliers. A frequent trap: an OLA is internal, a UC is with a third party, and an SLA is with the customer - mixing these up is a common distractor.
Transition: controlled movement into live use
Transition manages change, release and deployment, knowledge transfer, and testing. Know the difference between a release (a set of changes made available for use) and a deployment (the act of moving it into the live environment). Understand change types - standard (pre-authorized, low risk), normal (assessed and approved), emergency (fast-tracked) - and the role of the change advisory board (CAB) in advising on normal changes.
Traps to watch
- Assuming design ends when the service goes live; design also covers retirement.
- Treating a standard change as one needing full CAB review - it is pre-authorized by definition.
- Believing testing is optional for low-visibility changes.
Worked rule
For any change question, first classify the change type. Standard changes follow the pre-agreed procedure without CAB sign-off; normal changes need assessment and approval; emergency changes need expedited approval with later review. Classify first, then choose the approval path.