When the email goes, so does the way you tell everyone the email has gone
- Technology
- IT consultancy
- Business continuity
- Knutsford
The first instinct, when a cloud outage takes the mail out, is to email everybody and explain. That is the one thing that cannot be done.
Teams usually goes at the same time, because it is the same sign-in and frequently the same provider having the same bad morning. So within about four minutes a director has discovered that the three channels they would normally use to say "it is not just you, sit tight" are all on the other side of the fault.
Then comes the part nobody plans for. The list of staff mobile numbers is in the system that is down.
The list is the first thing to fix, and it is not a technology problem
Most small firms keep staff contact details in exactly two places: a cloud HR or payroll system, and the contacts that sync into Outlook. During a Microsoft outage both are unreachable, and the director is left scrolling their own phone hoping they once texted the part-time bookkeeper about a car park.
A sheet of paper in a drawer solves this permanently. Names, mobile numbers, next of kin if you hold it, your main suppliers with the account references you would have to quote, and the broadband and phone providers. Print it, date it, and reprint it when somebody joins or leaves.
It feels like an anachronism right up to the first time you need it.
Choose the channel before you need it, not during
Whatever you use to reach staff off-email needs two properties. It must not share a sign-in with your email, and everyone must have used it at least once already.
The second one is where plans fail. A group created in the middle of an outage requires you to contact everybody to tell them about the way you are going to contact them, which is the problem you were trying to solve. A group that already exists, with everybody in it, which somebody used last month to say the gate code had changed, works immediately.
It does not matter much which tool. A messaging group, a plain SMS list, a WhatsApp group with a dull name. What matters is that it predates the emergency.
What to say, and how often
Staff need three things from you during a blackout, and only one of them is technical.
Whether it is them or everyone. People will spend forty minutes restarting things and doubting their own laptop unless somebody with authority says the words "it is not your machine". Say it early, even if you do not yet know the cause.
What to do in the meantime, including what not to do. This is the instruction that gets left out, and it is the one that saves you work in December. Nobody should be re-sending client documents from a personal email account, copying files onto a personal drive, or setting up a forward "just until it is back". Those are reasonable improvisations by conscientious people, and they outlive the outage: a forwarding rule set on a Thursday morning is still copying your client mail to somebody's personal inbox two years later, which is its own afternoon of work to unpick.
And when the next update is coming. Not "we will let you know", but "I will send something by half eleven whether or not there is news".
Silence does not read as calm. People fill it in, usually with the worst version, and then act on their guess.
Supporting the team is mostly about permission
The thing that actually stresses people during an outage is not the technology. It is the sense that clients are being let down and that each of them is personally failing somebody.
So name who is handling clients. One person, with one agreed holding line, so that fourteen individuals are not each inventing an apology of their own and promising different things about when it will be fixed. Everybody else gets told explicitly that they are not expected to chase it.
Then tell people what to do with the time. Half an outage is dead time that nobody is allowed to admit to, and the honest version lands better: pick up the filing, the calls, the quotes you have been meaning to write by hand. People relax when the day has a shape.
If your phone system is Teams, it has gone with everything else. If it is a separate provider running over your broadband, it will survive somebody else's cloud outage, and not a cut line in the street. Worth knowing which you have before the morning it matters, because the answer changes who can still be reached.
The hour of work, now
- 01Print a contact sheet: staff mobiles, suppliers, account references, broadband and phone providers. Put it somewhere everyone can find without a password
- 02Make sure the off-email group exists, has everybody in it, and gets used for something harmless occasionally
- 03Name who decides and who communicates, and name their deputy for the day they are on a plane
- 04Write the two paragraphs you would send to staff and to clients, and keep them where you can reach them from a phone
- 05Decide now what staff may and may not improvise with, and tell them before they need to know
The last one is the one that pays for itself. Improvisation during an outage is not a discipline problem, it is what good employees do when the tools stop, and the only way to steer it is to have said something in advance.
And the day after
When the service comes back, your records have a hole in them the shape of the outage. Decisions made on the phone, agreements reached in a group chat, a client who was told something by somebody who then forgot to write it down.
An hour of putting that back into the system, deliberately, while everyone still remembers, is worth more than anything you did while it was down. We wrote about that side of it during last week's outage: the service was restored the same day, and the workarounds people invented are still in place.
You cannot prevent the next one. Microsoft's outage was Microsoft's to fix and the only honest instruction that morning was to wait. What you can decide, on a quiet Tuesday with a printer, is whether the second hour of it looks like the first.
If you would rather somebody else wrote the sheet and tested the group, we can do that with you.
We work with businesses across Knutsford, Alderley Edge, Wilmslow, Altrincham, Stockport and Warrington, and remotely for clients anywhere in the UK.
If any of this sounds like your business, we will tell you plainly whether we can help.
