If you weren’t affected yourself, you probably heard of the Microsoft email outage that took place last Thursday and dragged into, of all days, Friday the 13th. 👻
With so many schools running on Microsoft, plenty of staff rooms around the world got an unexpected day off email, and I suspect quite a few teachers enjoyed every minute of it. LinkedIn was certainly bursting with out-of-office jokes and celebrations, and responsive marketing teams didn’t miss a beat either. These two made me laugh out loud:
For the researchers studying email culture now, I bet last week must have felt like a gift.
Not everyone got a day off, of course. For the counselor with an urgent safeguarding concern, or the business office watching invoices with fixed due dates sit in limbo, it was a long day.
Still, an email outage is far from a crisis, and anyone who has lived through a real one can tell the difference. But it’s a useful excuse to think like we’re in one, because the best time to plan for a crisis is when you’re not in the middle of it.
Come to think of it, the closest I’ve been to a real one started with an email.
An Afternoon on the Soccer Field
During my first few years in Bucharest, on a bitterly cold winter day, a handful of international schools in the city received a coordinated email saying that a bomb had been placed in their buildings. Admin at our school quickly alerted the authorities and rang the fire alarm, and off we went to the soccer field for what essentially felt like an unscheduled fire drill.
As instructed, the entire school, from our youngest early childhood (EC2) to Grade 12 students, plus all the staff, stood there calmly, some in t-shirts and aprons, waiting for the “all clear” that would send us back into our heated classrooms, offices, posts and kitchen.
That announcement didn’t come in the first ten minutes, or the first hour even. We stayed there for an entire afternoon, past dismissal time, with worried parents sitting in their cars outside the field watching us shiver, while the bomb squad thoroughly searched the school.
When they finally confirmed it was a hoax, we were asked to leave the premises without going back inside, which for many of us meant heading home without our backpacks, winter coats or even car keys.
Our leaders were careful about what they shared on the megaphone, and rightly so, with all the children on that field. I don’t recall exactly what we were told about the wait, but I do remember the stretch of time when no communication came at all. There was nothing to report, except that we were waiting for the professionals to do their work.
Friday reminded me of that feeling in a much smaller way: the longer you wait in silence for word that something is fixed or resolved, the more you start to worry about what you can’t reach.
And in most school ecosystems, email is the catch-all channel. Spend a few minutes with any school’s crisis plan and you’ll quickly notice its prevalence.
Where We Are
Emergency protocols are not new to anyone who has worked in a school, especially since 2020. Most schools already have a reliable first response for a day like Friday, and it’s usually an SMS that feels like a tweet (from the 140-character days).
But these messages are built for brevity. They relay the bare minimum, and leave room for questions about what needs to happen today.
Stop for a moment and think about what travels by email in any given week at your school. I bet you have your own version of dismissal notes, revised deadlines, forms, duty rotation changes, or even the feedback surveys about the last fire drill.
When email goes down, all of it becomes unreachable because, more often than not, email is the only place where these things live.
Where We’re Going
Low-stakes events like Friday’s are like a rehearsal, a chance to check how ready we are for the real thing.
The principle behind the system we’ll use couldn’t be simpler: email is the doorbell, and the portal is the house. As such, the email’s job is to let people know what is waiting for them, while the information itself lives somewhere they can always find, whether or not the doorbell works.
I am a firm believer that every school needs a Single Source of Truth (SSoT), a central home where procedures are published and kept up to date, and where announcements live before they go out by email.
It’s the idea behind my very first post, The Single Source Principle, which is still one of the most-read articles I’ve written to date.
And I’ll be honest with you: this will not be a 30-minute task for a calm afternoon. A proper SSoT takes time, planning, and a dedicated owner, but it may be the most worthwhile admin job your school takes on this year.
When you think of it as part of your crisis-response plan, the time it takes to build and test it starts to look like a bargain.
So, today, I invite you to make this concept a proper item on your leadership team’s agenda this year.
How to Get There
You all know I love a good map, and this project starts with one. The video below walks through a design technique called process mapping, where you follow one piece of information from the moment someone creates it to the moment it reaches the person who needs it, writing down every step, person and platform along the way.
For this project, a process map will show you:
What only lives in email. Any step where the inbox is the sole home is a gap the next outage will expose.
Where the same information lives in several places, and which version people trust when they don’t match.
Who the bottlenecks are. If one person sends, approves or forwards everything, that’s your single point of failure on a bad day.
Which channels depend on each other, so you can see what goes down together.
Where your SSoT should sit. Usually it’s the place people already check for something else that works.
Then, build the home.
Once the map shows you where this SSoT should live, add a “this week” page to it, something like a live Google doc that your leadership team and anyone who needs to be able to communicate with all staff can edit and every staff member can view.
Here is where the actions required, upcoming deadlines and anything that has changed is posted, each entry dated and taken down once it’s passed.
Next, set one simple rule for everyone who communicates widely: post to the SSoT first, and only then send the email, with a link back to it.
Now, you might be thinking, “what if Google is down next?” and you’d be right to ask. No home is outage-proof, so the trick is making sure it never shares a provider with your email. If you’re a Microsoft school, a Google Doc works well. If you’re a Google school, look at your website or LMS.
Truth be told, none of this would have shortened our afternoon on that soccer field. But whether you’re stuck on a field or at home after an unexpected school closure, knowing exactly where to look for news makes the wait a lot easier. That’s what a good system does when the usual channel isn’t there.
This Week’s Move
Pull up the last five emails your school sent to all staff that asked people to do something. For each, check whether the same information lives anywhere other than the inbox. The ones that don’t have an official home make a good first list for your SSoT portal.
If you’re a Microsoft school, I’d love to hear how Friday went, and any tricks worth sharing with colleagues elsewhere.
Systematically yours,

About the Author:
G (short for Gitane) is co-founder and Chief Creative Officer at EKG Collective, helping international schools turn communication complexity into systematic clarity. Learn more at ekgcollective.com.





