How a 20-Minute Outage Was Perceived as Two Hours Due to Poor Communication

A technical team resolved a service outage in just 20 minutes, but the wider organisation experienced it as a two-hour disruption because no one communicated updates externally. The service desk fielded 90 calls from confused staff, two department heads made operational decisions based on rumour, and a delivery team was sent home unnecessarily. Even after service was restored, users continued assuming the system was down for another 90 minutes due to cached pages and the absence of a recovery announcement. The team's existing status page had gone untouched for 14 months, as updating it was no one's assigned responsibility during incidents. In response, the organisation now designates two named roles from the start of every significant incident — one to manage the fix and a separate person solely responsible for communications — with mandatory updates sent on a fixed schedule regardless of whether there is new information to share.