“We are brilliant in a crisis” is not the compliment you think
· 3 min read
In brief
Being “brilliant in a crisis” is not the compliment it seems, because excelling at incident management usually means getting a great deal of practice fixing failures that should not have happened. John Sansbury argues that IT and Estates teams in higher education should shift effort from heroic recovery to prevention.
- Incident management is the only purely reactive process in service management; its sole benefit is restoring a service that should not have broken.
- Four barriers keep organisations reactive: everyone is too busy firefighting, unreasonable deadlines push teams to cut corners, prevention costs are visible while failure costs are spread invisibly, and a hero culture rewards the dramatic rescue over the uneventful year. The Millennium Bug shows that prevention is thankless precisely when it works best.
- The cost is large. Research cited in the book puts the cost of putting right what should not have gone wrong at up to 30 per cent of turnover, and outages at between 2,300 and more than 9,000 dollars per minute.
- The practical first step is problem management, which removes the causes of incidents rather than their symptoms. One trained problem manager who prevents a single serious outage a year pays for themselves several times over.
- That person must be dedicated. Assigned alongside a day job, they will be pulled back into firefighting, and recurring issues such as hall lift failures or annual timetabling clashes will simply recur.
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.
