Friday the 13th lived up to its reputation for many UK businesses this month. As staff started their working day, disruption to Microsoft 365 meant familiar ways of communicating and getting work done were suddenly unavailable.
If your organisation was affected that morning, you probably learnt something about how it operates under pressure.
Perhaps a few phone calls kept an important transaction moving. Perhaps an application remained available, but the email needed to complete its workflow didn’t. Or perhaps colleagues found an alternative that got them through the morning, while creating work to catch up on afterwards.
Or did your organisation effectively have a “snow day”, with people ready to work but unable to access what they needed? An unexpected day off might have been welcome for some, but for the business it meant lost working time and tasks waiting to be picked up later.
Those experiences are worth revisiting while they’re fresh. They can show where your business is resilient, where it relies on individual resourcefulness and where a relatively small change could help.
Here, we look at how to turn what happened into practical improvements - and consider whether the arrangements that helped on Friday would hold up during a longer or different disruption.

Some of the most revealing consequences of an outage are the ones nobody expected.
During the disruption some hospitality businesses reported that losing email also affected voicemail, because messages were delivered by email. An emailed verification requirement created another access problem. Several apparently separate functions depended on the same unavailable service.
Your organisation may have discovered similar dependencies. A customer portal might have remained available while its notifications stopped. Staff might have been able to open an application but unable to complete an approval or retrieve the information needed to use it.
These are good places to begin a review. Ask colleagues what they expected to work, what actually happened and where they became stuck. Following those specific experiences back through the process can reveal dependencies that are easy to miss in a list of systems.
It’s also worth considering what remained available. If your workaround depended on telephony, a customer database or a particular sign-in service, that dependency belongs in the review too. Friday gave you evidence about one disruption; another could affect a different combination of services.
An alternative route can be remarkably simple. Reuters reported that Aviva used alternative telephone numbers for earnings calls and Bluetooth to transfer recordings during the outage. Its chief executive, Amanda Blanc, also said the business had tested a comparable outage of critical technology systems approximately two weeks earlier.
At TIEVA, we experienced some of that benefit ourselves. With Mimecast email security deployed, we and customers using the same functionality could still send and receive emails. There was a significant catch, though: many of the people we needed to contact were still affected, so messages couldn’t necessarily flow in both directions. It allowed some work to continue, but it was far from business as usual.
That’s worth considering when reviewing your own arrangements. A fallback may keep your side of a process working while customers, suppliers or other partners remain unable to complete theirs. Understanding those limits helps you plan what you can realistically achieve during an outage.
Alongside the technology available, consider the part people played in keeping work moving. Some colleagues may have followed an agreed fallback process; others may have found a way through using their own knowledge and contacts.
Someone might have had a supplier’s mobile number, held a local copy of a document or understood how to complete a process manually. That initiative deserves recognition. Capturing the knowledge behind it makes the same option available when that colleague is absent or dealing with another urgent problem.
A short conversation with the people involved can help establish what they did, what access they needed and which decisions required approval. Those details give you something concrete to build into the plan, beyond recording that the business simply got by.
Switching from email to telephone sounds straightforward until everyone needs to make a call.
Euronext told listed companies to use the telephone during the disruption. It also ensured sufficient staffing for the additional workload and verified callers’ identities, according to the same Reuters report.
That’s an important detail. A fallback channel needs people to operate it, a way to prioritise requests and a record of what has been agreed.
For many UK businesses, the immediate challenge was getting through Friday. A practical next step is to consider how those same arrangements would perform through another working day. Could the team keep answering calls alongside its usual work? Would manual approvals start to queue? Could staff still find the information needed to help customers?
You may decide that a reduced service would be the most realistic response: prioritising urgent transactions, extending response times or temporarily pausing lower-priority work. Agreeing those choices in advance helps colleagues make consistent decisions and gives customers clearer expectations.
People trying to help customers will naturally look for another way to communicate. Giving them suitable options beforehand makes that easier.
Reuters reported that HSBC reminded staff not to use unauthorised personal email or WhatsApp during the outage. Maersk asked customers to telephone about urgent matters and to verify unexpected outage-related communications with their local representative.
Both examples highlight the importance of retaining familiar safeguards when the way people work has changed.
A practical plan should explain which alternative channels staff can use, what information they can share and how to verify sensitive instructions. It should also make clear how approvals and decisions will be recorded, so colleagues have something reliable to refer to afterwards.
Access deserves attention too. An alternative application offers limited help if signing in requires a message sent to the unavailable mailbox. Testing those access arrangements, with appropriate security controls maintained, is part of checking that the fallback will work when needed.
Customers experiencing the same disruption may understand why a response is delayed. They still need to know how to reach you and what to expect.
Make your preferred channels clear through a route they can access. Depending on your business, that could be a website notice, a service-status page, a recorded telephone message or another established communication channel.
The message should help customers decide what to do next. Explain which services remain available, how to raise an urgent request and whether an earlier enquiry needs following up. If response times have changed, say so.
It’s also worth thinking through the effect of those instructions on your team. Asking everyone to resend an email, for example, could create duplicates when queued messages arrive. A clear approach to follow-up can save effort for customers and staff alike.
Once services return, there can be an understandable temptation to assume everything is back to normal. For the people handling outstanding work, recovery may take longer.
Emails may arrive after a request has already been dealt with by telephone. Temporary records may need entering into business systems. Transactions started manually may need checking before the usual workflow resumes.
Planning for this helps avoid confusion during the catch-up. Agree who will reconcile records, how colleagues will identify completed requests and which outstanding activities take priority.
There may also be limits on what the business can recover immediately. If teams spent the day handling calls or working manually, their usual tasks may still be waiting. Allowing for that effort produces more realistic expectations for staff and customers.
You now have a recent account of how your organisation responded to disruption. That gives you a useful basis for a practical exercise.
Bring together the people involved and revisit a few important moments: where a process stalled, how an alternative was found or why a decision took longer than expected. The aim is to understand what would make the response easier next time.
Then try out the improvements. Can colleagues access business continuity plans without the usual collaboration platform? Can authorised staff sign in to the fallback systems? Can a customer request move through the alternative process and back into normal operations without losing information?
You can extend the scenario where it helps. The colleague who solved the problem might be unavailable. The disruption might last longer. Another critical vendor’s service might be affected. These variations help establish how repeatable the response is and where further preparation would be worthwhile.
Some changes may need a technology solution. Others may involve clearer responsibilities, accessible contact information, an approved communication channel or a better way of recording manual work.
The experience of Friday the 13th can help you prioritise. Focus on the gaps with the greatest business impact, then consider the practicality of addressing them. Additional systems bring costs, training requirements and maintenance of their own, so each proposed solution should have a clear purpose.
At TIEVA, we can help you turn what happened into a practical improvement plan: reviewing dependencies across business-critical technologies and vendors, identifying suitable fallback solutions, and helping develop and test business continuity and recovery plans.
If the outage revealed something you’d like to address - or a workaround you’d like to make more dependable - speak to your TIEVA account manager or contact our team.