Blameless Postmortems: Language for Learning Without Blame
5 exercises on postmortem key phrases. Choose the most natural and professional option.
0 / 10 completed
1 / 10
When writing a postmortem, how should you describe what caused the incident?
CONTRIBUTING FACTORS: The phrase "The contributing factors were..." shifts focus from individuals to systemic conditions. It invites multiple causes and prevents blame. Examples: "The contributing factors were: no automatic rollback on error spike, alert thresholds set too high, and runbook out of date." / "Contributing factors included: unclear ownership of the config file, no staging environment parity, and insufficient monitoring." / "The contributing factors were a combination of time pressure from the release deadline and gaps in our on-call rotation." Options A/C/D name or imply individual blame, which makes postmortems less honest and psychologically unsafe for contributors.
2 / 10
You're presenting the sequence of events at the postmortem. Which opening is most professional?
TIMELINE LANGUAGE: "The timeline shows:" followed by timestamped events is the standard postmortem format used at Google, Atlassian, and most engineering organisations. It's factual, precise, and keeps the narrative grounded in data. Examples: "The timeline shows: 09:00 config change merged; 09:04 latency increased 40%; 09:12 page triggered." / "The timeline shows feature flag enabled at 16:30, first customer report at 16:38, rollback completed at 16:52." / "Timeline: 22:00 cron job ran; 22:01 DB CPU hit 100%; 22:03 primary failover triggered." Options A/B/C are informal and lack the precision needed for a formal postmortem document.
3 / 10
A junior engineer is afraid they'll be blamed. What framing do you use in the postmortem?
SYSTEM FAILURE FRAMING: "This was a system failure, not a human failure" is the cornerstone phrase of blameless postmortems, popularised by Google SRE and Etsy engineering. It acknowledges that humans operate within imperfect systems. Examples: "This was a system failure — our CI pipeline should have caught this before it reached production." / "We don't blame individuals. This is a system failure: our alerts didn't fire early enough." / "System failure: the deployment tool had no guardrail to prevent this class of change." Option B dismisses the issue, C is sympathetic but not systemic, D is the opposite of blameless culture.
4 / 10
How do you present action items at the end of a postmortem?
FRAMING ACTION ITEMS: Postmortem action items need specific ownership, due dates, and tie back to the contributing factors. The format "(1) Action — owner: X, due: date" makes follow-through accountable. Examples: "Action: Increase alert sensitivity on payment errors. Owner: SRE, due: next sprint." / "Action: Add staging parity for config changes. Owner: DevOps, due: 2024-02-15." / "Action: Document the on-call escalation path. Owner: Ana. Due: end of month." Options A/D are vague with no ownership, option B reverts to individual blame rather than process improvement.
5 / 10
How do you close the postmortem learning section?
WHAT DID WE LEARN: The "What did we learn?" section should name specific systemic improvements, not personal lessons or superstitions. Examples: "What did we learn? Our feature flag system has no gradual rollout capability — we need to build that." / "What did we learn? We lack observability into the connection pool state. Adding metrics is now a P1." / "What did we learn? The incident declaration threshold is too high — we were firefighting for 20 minutes before declaring." Option A is wishful thinking, C is blame-adjacent, D is a folk heuristic, not a systemic insight.
6 / 10
Sarah, a senior engineer, is drafting the description for a Pull Request that introduced an intermittent error in the user authentication service. She wants to focus on finding the root cause without assigning blame. Which of the following phrases best reflects this approach?
The key here is focusing on the technical problem and its *cause*, not assigning responsibility. Option A blames the code's quality, while option D points to a process failure. Option B is too vague and doesn't describe the issue itself, and option 'C' directly identifies the root cause – a race condition – demonstrating a blameless approach.
7 / 10
During a Slack discussion following an incident where the website's API experienced high latency, Mark wants to encourage a productive conversation. Which of the following messages is most appropriate for him to post?
Mark's goal is to facilitate understanding and problem-solving. Option A is demanding and accusatory. Option D dismisses the issue without investigation. Option 'B' clearly outlines the desired action: investigating the cause of the latency, aligning with a blameless postmortem philosophy.
8 / 10
As part of a postmortem for a failed deployment to production, David needs to summarize the timeline. Which statement is the most effective way to describe the initial problem?
Option A is overly simplistic and potentially accusatory. While technically true, it doesn't provide context or allow for investigation. Option 'B' accurately describes the observed symptoms (increased error rates) and timeframe, allowing for analysis of the root cause – crucial for a blameless postmortem. The other options present misleading information.
9 / 10
During a standup meeting, Alex reports an incident where a microservice experienced a brief outage. He's preparing to add details to the postmortem. Which of the following statements is best for him to include?
Alex needs to focus on *what happened* and its impact. Option A immediately introduces blame. Option D suggests a solution, which is appropriate for action items but not the initial description of the incident. Option 'B' provides a factual account of the outage without judgment – perfectly aligned with blameless postmortems.
10 / 10
In the 'Learning' section of a postmortem document, Emily is summarizing the key takeaways. Which statement best captures the purpose of this section?
The 'Learning' section is about *systemic* improvement, not individual accountability. Option A directly contradicts the blameless approach. While solutions and technical details are important, the focus should be on extracting lessons to avoid repetition – a proactive step toward preventing future incidents without assigning blame.
What will I practise in "Blameless Postmortems: Language for Learning Without Blame"?
This module focuses on Phrasebook — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Phrasebook exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasebook — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Phrasebook exercises?
See the Phrasebook hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.