SIAM implementation and transition
Domain 6 tests whether you can sequence an implementation sensibly, choose transition tactics, and name the critical success factors and risks.
Implementation stages
- Discover and baseline: current contracts, service architecture, provider landscape, performance baseline, stakeholder map, business case.
- Design: structural option, process model and interfaces, roles and retained capability, governance, tooling, contract changes.
- Build: tooling configuration and integration, process documentation, recruitment or partner selection, training.
- Transition: provider onboarding (due diligence, knowledge transfer, service readiness review), pilot or parallel running, cutover, decommissioning of legacy contracts and services.
- Operate and improve: run the model, measure it, mature it. Treat these as iterative, delivered in waves by service, geography or provider so risk stays bounded.
What makes transition work
Executive sponsorship with a mandate; contracts renegotiated to reward collaboration and shared data; design before tooling; retained capability stood up before the old contract ends; an explicit exit plan for every provider; culture and communication managed as a workstream, not an afterthought.
Worked example
A government department leaves a single outsourcer for four providers and a hybrid integrator. Reasoning: a big-bang cutover would risk citizen-facing services, so transition runs in waves - network first (stable, low business impact), applications second; one service line piloted for eight weeks with parallel running; the new contracts include a clause requiring shared performance data; legacy decommissioning waits until two clean service review cycles. Each choice reduces blast radius and gives the integration team evidence before scaling.
Traps that cost marks
- Tool-first implementation: buying an ITSM suite before the process model and interfaces are designed.
- Implementing SIAM without amending contracts and SLAs - old incentives defeat the new model.
- Big-bang cutover with no pilot or fallback.
- No exit or transition plan for incumbent providers.
- Forgetting that the retained organisation must change too, not only the providers.
- Treating implementation as a project that ends; the model needs continual adjustment.