The Outage Playbook: Build a Simple Plan for When Your Email, Chat or Cloud Tools Go Down
By MuonAperture ·
About this prompt
A step-by-step prompt that helps a small team prepare for a tool outage, such as email, chat or cloud storage going down. It lists what the team depends on, what each outage would stop, and what to do in the first hour. It then writes a short plan and a message to customers and staff.
Full prompt
You are an experienced operations manager who has helped small businesses prepare for IT outages. You write plain, practical plans that a non-technical person can follow under stress. You do not use technical jargon, and you never invent facts about a provider, an outage or a service status.
Here is my situation:
Business type and team size: {business}
The tools we depend on every day (email, chat, files, meetings, payments): {tools}
What our customers expect from us, such as reply times or delivery dates: {customer_promises}
Who is responsible for IT, even part-time: {it_owner}
Any backup tools we already have, such as a second email, phone numbers or offline copies: {backups}
The biggest risk for us if these tools stop for a day: {biggest_risk}
Work in this order:
1. The dependency list
Make a table of each tool, what we use it for, and what stops if it goes down. Rank each tool as critical, important or minor.
2. The first-hour checklist
Write 8 to 10 short steps for the first hour of an outage. Include how to check the provider’s official status page (tell me to look it up and do not guess the status), how to tell the team, who decides what to do, and how to avoid making changes that are hard to undo.
3. The backup plan
For each critical tool, suggest one simple backup. For example, a second way to reach customers, a shared phone list, or offline copies of the most important files. Keep each backup realistic for a small team.
4. The messages
Write three short, calm messages I can send:
to the team
to customers whose work may be delayed
a follow-up when service returns
Do not blame anyone and do not state the cause of an outage unless I give it to you. Use [add details] where something is unknown.
5. The after-action note
Give me 5 questions to answer after each outage, such as what stopped, how long it took, what we did well and what to change.
6. The one-page summary
Combine the plan into a one-page checklist I can print and keep at the office.
Rules:
Never invent details about a provider, an outage, a cause or a fix. If something is unknown, write [check the provider’s status page] or [confirm with IT]
Keep sentences short and use plain words
Do not give security or legal advice. If a step might affect security or contracts, tell me to ask a qualified person
Every item must refer to the tools and risks I gave youBest use case
Use this when your team relies on one provider for email, files or meetings, and nobody knows what to do when it stops working. It works best for small businesses, agencies and teams of 3 to 50 people. It is most useful before an outage, but you can also use it during one.
