🚨 Incident Response
5 exercise sets. The English you need when production is down: fast, clear, blameless communication under pressure.
- Intermediate
Communicating During an Outage
Write clear status updates, escalations, and Slack/Teams messages while an incident is in progress. Stay calm and precise under pressure.
- Intermediate
Building the Incident Timeline
Document what happened and when. Practice the past tense narrative: "At 14:32 UTC, the deployment pipeline triggered…"
- Advanced
Writing Post-Mortems
Write blameless post-mortem reports: timeline, root cause analysis, impact statement, and action items in professional English.
- Advanced
War Room & Bridge Call Language
Run and participate in incident bridge calls. Vocabulary for assigning owners, calling rollbacks, and declaring "all clear".
- Beginner
On-Call Vocabulary
SLA, SLO, MTTR, MTTD, escalation policy, severity levels — master the vocabulary before your first on-call shift.
Useful language for incident response
Status updates
- "We are currently investigating an issue affecting…"
- "The root cause has been identified as…"
- "A fix has been deployed to production and the situation is being monitored."
- "All systems are operational. Incident resolved at 16:47 UTC."
War room phrases
- "Who owns the database layer right now?"
- "Let's roll back the last deployment."
- "Blast radius — how many users are affected?"
- "Call the all-clear when monitoring is green."
Post-mortem language
- "The contributing factors were…"
- "Action item: add alerting for X by [owner] by [date]."
- "This incident was a result of cascading failures…"
- "No single point of failure caused this; rather…"