Everything we have written on delivery & risk.

Delivery risk in ServiceNow programmes rarely comes from the technology. It comes from the gap between technical readiness and human readiness, from SLA breaches treated as failures rather than signals, and from project structures that assume a single-team cadence when the programme has already outgrown it.

The Manual covers this domain through two editions. The OCM plan edition addresses the synchronisation problem: technical workstreams and change management workstreams that run on different timelines, with different resource models, and meet only at go-live, when it is too late to course-correct. The resource allocation framework and risk-mitigation decision tree have been field-tested across six programmes and are built to surface misalignment early rather than at deployment.

The SLA breach management edition reframes breaches from failures into institutional learning signals. The recovery framework has three layers: immediate response (contain the breach), root-cause analysis (understand why the breach happened) and structural remediation (change the conditions that allowed it). Most programmes get stuck at layer one because they treat breach management as an operational task rather than a governance feedback loop.

The recurring theme across both editions is that delivery risk is a design problem. The ServiceNow delivery model you choose, how you staff it, how you govern it, how you handle the inevitable surprises, determines whether the programme scales or stalls.