The freezer, the certificate and the one person who knows
· 3 min read
In brief
Single points of failure are not always hardware. As John Sansbury argues in The Journey to Service Excellence, they can be software, a licence, a certificate, a supplier or one irreplaceable person whose knowledge exists only in their head, and they usually stay invisible until they break.
- One expiry can have global reach. Carriers in eleven countries were affected on the same day by a failure nobody knew was a single point of failure or was about to expire; the compensation Ericsson was believed to have paid O2 alone was in the order of £100 million.
- Universities have their own hidden weak links. Examples include a minus eighty freezer with an untested alarm, a research licence whose renewal date sits in one inbox, a computing cluster relying on a script only one postdoc understands, and a long-serving technician about to retire with undocumented knowledge.
- Know what downtime costs. Very few leaders know what an hour of downtime costs, yet it is the most effective business case for prevention. TSB's 2018 migration failure cost £366 million once compensation, fraud losses, fixing costs and lost income were counted.
- Look deliberately, with simple techniques. Single point of failure analysis asks, at each step of a service, what happens if this one thing fails and whether anything stands behind it. Fault tree analysis works backwards from an unaffordable failure to map every path that could cause it. Neither needs expensive tooling, only time to look before failure strikes.
Continue reading on the Exchange
Join or sign in to read the complete article, explore the full knowledge library and record your CPD.
Founder membership is free for life
More from John Sansbury
Available to members.
Related articles
How should the service desk handle a Microsoft 365 outage it cannot fix?
Treat a supplier cloud outage as your own major incident: log it once, tell people early on a channel that still works, update on a rhythm and review your dependency afterwards.

Deploying AI is the easy part: who runs it once it goes live?
Only a third of large enterprises have met the business case for their main AI programme. New research points to a gap in who runs AI after launch, and what leaders can do.
How do I compare help desk tool pricing before rolling it out across several departments?
Compare help desk tools on a full year's cost for your real agents, approvers and requesters in every department, not on the headline monthly price.
Turning 'not helpful' into a fix
'Not helpful' is free, honest feedback, and most of it goes nowhere. Turn that click into a fix.
When the author leaves, who owns the article?
Articles keep being read after their authors move on. Make sure the care for them does not leave too.
Test after every change, or find out from users
Knowledge changes fail quietly. A short, repeatable test after every change finds the problem before your users do.
