WATCHTake a breath. Do these in order.
How you might know
- Customers could be affected by an incident.
- People are asking questions you cannot yet answer.
- A rumor is spreading.
Do this now
Write what happened in plain words
One or two sentences without jargon. Say what went wrong and when it was found.
Say who is affected and who is not
Be specific. Say how people can tell if they are affected.
Give people clear actions
For example, "Replace your API key at your provider". Short numbered steps.
Say what you are doing
Explain what you have fixed and what you are still working on.
Promise the next update
Say when you will update again, and keep that promise even if there is nothing new.
Have one person approve and publish
One voice avoids mixed messages. Use email for affected people and a status page for everyone.
Do not do this
- Do not speculate about the cause.
- Do not minimize or hide behind vague words.
- Do not blame individuals or customers.
Who to tell
- Affected users first
- Everyone else via your status page or website
What to save before you clean up
- Each version of the update with timestamps
- The facts behind each statement
In the next 24 hours
- Update the notice as you learn more.
- Answer questions in one place.
- If personal data was exposed, check legal notification deadlines now (for example, GDPR generally expects regulator notice within 72 hours where feasible, unless the risk to people is unlikely). Ask a lawyer.
- Prepare a fuller post mortem.
What to write in the post mortem afterwards
- Time from detection to first message
- Whether readers could act on it
- What questions it left unanswered
Finished this one?
Add it to What I learned and earn 30 Trust. You can open your list from the badge at the bottom of the page.