Polle de Maagt 
Polle de Maagt
Story.
Is the service down for everyone? Is the problem my phone, wifi or account? Should I wait, restart everything or contact support?
Apple answers those questions with a public System Status page. It lists the key services and shows whether they are available or affected by a planned or unplanned incident.
The page does not solve the outage. It solves the second problem: not knowing what is happening.
What they did.
Apple put the status of its services on one plain public page. Each service gets a simple indicator. When something is wrong, the page says which service is affected and since when.
It is not hidden behind a login or a support flow. Anyone can check it in seconds.
Why it works.
Without context, customers start troubleshooting, contacting support and sharing theories. A simple status page reduces uncertainty and shows that the company is watching the same problem.
Transparency will not make a broken service work. It does make the failure easier to handle.
Try it yourself.
Every organisation with a service customers depend on should have one. Keep it public. Keep it plain. Update it before customers need to ask.
It does not have to be software. A train operator, an IT helpdesk or a facilities team can do the same with one page.
List the three services customers ask about most when something breaks. Decide where their status will be visible and who updates it.
Source: my original post of May 2020 and Apple’s System Status page. Traffic light made with Midjourney.
