4 exercises — redirecting blame to stay process-focused, requesting a structured timeline walkthrough, transitioning from analysis to action, and assigning owned, dated action items.
0 / 19 completed
1 / 19
You are facilitating a postmortem and someone starts explaining what a specific engineer did wrong. How do you redirect the conversation to stay blameless?
'Let's focus on what happened, not who did it' is the standard blameless-postmortem redirect — it reframes the discussion around the sequence of events and system conditions rather than individual fault: 'Let's focus on what happened, not who did it.' This phrase is calm, procedural, and doesn't single anyone out. 'Let's not talk about who made the mistake' still implies a mistake was made by a person. 'That's not really fair' sounds like you're defending the individual rather than redirecting the process. 'We shouldn't name names, okay?' sounds like a rule being enforced rather than a natural facilitation move. Blameless facilitation language consistently centres on the system and timeline, not the person.
2 / 19
You want the team to walk through the sequence of events during the incident in order. Which question is most effective?
'Can you walk us through the contributing factors, starting from the first alert?' is precise incident-review language — it asks for a structured, chronological account and explicitly frames the causes as 'contributing factors' rather than a single root cause or someone's fault: 'Can you walk us through the contributing factors, starting from the first alert?' 'What exactly happened, in general' is contradictory (exactly vs. in general). 'Tell us the story' is too informal for a structured timeline review. 'Your version of events' implies there are competing narratives, which undermines the blameless framing. Anchoring the walkthrough to a concrete starting point ('the first alert') produces a more useful timeline.
3 / 19
Near the end of a postmortem, you want to move the discussion from analysis to actionable improvement. Which question is most standard?
'What did we learn from this, and what should change?' is the standard transition phrase from incident analysis to remediation in a postmortem: it converts the discussion from diagnosis into concrete improvement. 'Are we done here?' skips the improvement step entirely. 'Whose fault was it, ultimately?' reintroduces blame after (presumably) a blameless discussion. 'Let's just hope this doesn't happen again' relies on hope instead of action — the opposite of what a postmortem is for. Effective postmortems always end with named, trackable follow-up actions derived from lessons learned, not vague hopes or blame attribution.
4 / 19
You are wrapping up the postmortem and need to assign a specific improvement task. Which phrasing is most appropriate?
'Who will own action item #2: [specific action] by [deadline]?' is the standard closing phrase for postmortems — it names the item number, the specific action, and a deadline, and directly asks the room to name an owner: 'Who will own action item #2: adding an alert for queue depth by next sprint?' 'Someone should probably...' has no named owner or deadline. 'We'll figure out who does what later' defers accountability past the meeting, when action items are most likely to get assigned. 'I hope the on-call team handles that' relies on hope rather than an explicit commitment. Postmortems that end without named owners and deadlines rarely result in the improvements being made.
5 / 19
Sarah, the Lead Backend Engineer, is reviewing a pull request for a new payment gateway integration. A junior developer has included extensive logging throughout the code. Sarah comments: 'This level of logging is going to severely impact performance.' Which response best demonstrates constructive feedback during this post-mortem discussion?
The correct answer focuses on investigation and optimization—a key element of post-mortems. Simply stating an opinion or assigning blame (options A & C) doesn't contribute to learning. Option D deflects responsibility and avoids addressing the underlying issue of performance impact. Suggesting a focused review allows for identifying truly necessary logging.
6 / 19
David, a DevOps Engineer, sends a Slack message to the team: 'The database server crashed again. It's likely due to insufficient memory allocation.' What is the MOST effective way for him to frame this issue during a post-mortem meeting?
Option 1 encourages investigation and data-driven analysis—a crucial step in post-mortems. It avoids assigning blame and focuses on understanding the *cause* of the problem. Options A and C are reactive without understanding, while option B is overly simplistic and doesn't acknowledge the complexity of system failures. The goal isn't just to fix a symptom but to prevent recurrence.
7 / 19
Maria, a Software Engineer, is drafting a PR description for a recent incident involving an API outage. The description reads: 'The server died because I forgot to restart it.' Which revision BEST improves this description for a post-mortem?
Option 1 provides a neutral and factual description of the event, focusing on the outcome without personal blame. It avoids accusatory language like 'I forgot' (option A) and doesn't attribute the problem to a bug (option D). Option B is more detailed but still avoids direct blame, while option C is overly self-deprecating and unprofessional for a post-mortem.
8 / 19
During a standup update about the recent deployment issue, Ben says: 'I spent all morning debugging the build process. It was incredibly complex and frustrating.' How should he frame this during the post-mortem discussion to ensure constructive learning?
Option 1 shifts the focus from personal frustration to a systemic analysis of the build process. This aligns with the purpose of a post-mortem, which is to identify and address underlying problems, not dwell on individual experiences. Options A & C are unproductive, while option B inappropriately deflects responsibility.
9 / 19
Emily, a Senior Developer, is leading a post-mortem for a recent production incident. She asks the team: 'What were our assumptions and how did they contribute to the problem?' Which question does this BEST represent?
Option 2 directly addresses the concept of assumptions and their impact—a critical element in understanding why incidents occur. It probes the team's thought process rather than just seeking a technical root cause (option 1). Options A & D are focused on outcomes/responsibility, not the underlying decision-making. Recognizing and challenging assumptions is key to preventing future mistakes.
10 / 19
Sarah, the Lead Backend Engineer, is reviewing a pull request for a new payment gateway integration. A junior developer has included extensive logging throughout the code. Sarah comments: 'This level of logging is going to severely impact performance.' Which response best demonstrates constructive feedback during this post-mortem discussion?
The correct answer focuses on investigation and optimization—a key element of post-mortems. Simply stating an opinion or assigning blame (options A & C) doesn't contribute to learning. Option D deflects responsibility and avoids addressing the underlying issue of performance impact. Suggesting a focused review allows for identifying truly necessary logging.
11 / 19
David, a DevOps Engineer, sends a Slack message to the team: 'The database server crashed again. It's likely due to insufficient memory allocation.' What is the MOST effective way for him to frame this issue during a post-mortem meeting?
Option 1 encourages investigation and data-driven analysis—a crucial step in post-mortems. It avoids assigning blame and focuses on understanding the *cause* of the problem. Options A and C are reactive without understanding, while option B is overly simplistic and doesn't acknowledge the complexity of system failures. The goal isn't just to fix a symptom but to prevent recurrence.
12 / 19
Maria, a Software Engineer, is drafting a PR description for a recent incident involving an API outage. The description reads: 'The server died because I forgot to restart it.' Which revision BEST improves this description for a post-mortem?
Option 1 provides a neutral and factual description of the event, focusing on the outcome without personal blame. It avoids accusatory language like 'I forgot' (option A) and doesn't attribute the problem to a bug (option D). Option B is more detailed but still avoids direct blame, while option C is overly self-deprecating and unprofessional for a post-mortem.
13 / 19
During a standup update about the recent deployment issue, Ben says: 'I spent all morning debugging the build process. It was incredibly complex and frustrating.' How should he frame this during the post-mortem discussion to ensure constructive learning?
Option 1 shifts the focus from personal frustration to a systemic analysis of the build process. This aligns with the purpose of a post-mortem, which is to identify and address underlying problems, not dwell on individual experiences. Options A & C are unproductive, while option B inappropriately deflects responsibility.
14 / 19
Emily, a Senior Developer, is leading a post-mortem for a recent production incident. She asks the team: 'What were our assumptions and how did they contribute to the problem?' Which question does this BEST represent?
Option 2 directly addresses the concept of assumptions and their impact—a critical element in understanding why incidents occur. It probes the team's thought process rather than just seeking a technical root cause (option 1). Options A & D are focused on outcomes/responsibility, not the underlying decision-making. Recognizing and challenging assumptions is key to preventing future mistakes.
15 / 19
Sarah, the Lead Backend Engineer, is reviewing a pull request for a new payment gateway integration. A junior developer has included extensive logging throughout the code. Sarah comments: 'This level of logging is going to severely impact performance.' Which response best demonstrates constructive feedback during this post-mortem discussion?
The correct answer focuses on investigation and optimization—a key element of post-mortems. Simply stating an opinion or assigning blame (options A & C) doesn't contribute to learning. Option D deflects responsibility and avoids addressing the underlying issue of performance impact. Suggesting a focused review allows for identifying truly necessary logging.
16 / 19
David, a DevOps Engineer, sends a Slack message to the team: 'The database server crashed again. It's likely due to insufficient memory allocation.' What is the MOST effective way for him to frame this issue during a post-mortem meeting?
Option 1 encourages investigation and data-driven analysis—a crucial step in post-mortems. It avoids assigning blame and focuses on understanding the *cause* of the problem. Options A and C are reactive without understanding, while option B is overly simplistic and doesn't acknowledge the complexity of system failures. The goal isn't just to fix a symptom but to prevent recurrence.
17 / 19
Maria, a Software Engineer, is drafting a PR description for a recent incident involving an API outage. The description reads: 'The server died because I forgot to restart it.' Which revision BEST improves this description for a post-mortem?
Option 1 provides a neutral and factual description of the event, focusing on the outcome without personal blame. It avoids accusatory language like 'I forgot' (option A) and doesn't attribute the problem to a bug (option D). Option B is more detailed but still avoids direct blame, while option C is overly self-deprecating and unprofessional for a post-mortem.
18 / 19
During a standup update about the recent deployment issue, Ben says: 'I spent all morning debugging the build process. It was incredibly complex and frustrating.' How should he frame this during the post-mortem discussion to ensure constructive learning?
Option 1 shifts the focus from personal frustration to a systemic analysis of the build process. This aligns with the purpose of a post-mortem, which is to identify and address underlying problems, not dwell on individual experiences. Options A & C are unproductive, while option B inappropriately deflects responsibility.
19 / 19
Emily, a Senior Developer, is leading a post-mortem for a recent production incident. She asks the team: 'What were our assumptions and how did they contribute to the problem?' Which question does this BEST represent?
Option 2 directly addresses the concept of assumptions and their impact—a critical element in understanding why incidents occur. It probes the team's thought process rather than just seeking a technical root cause (option 1). Options A & D are focused on outcomes/responsibility, not the underlying decision-making. Recognizing and challenging assumptions is key to preventing future mistakes.
What will I practise in "Incident Review / Post-Mortem Meeting Language"?
This module focuses on Meetings & Collaboration — real workplace phrasing you'll use on the job. It contains 19 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 19 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 Meetings & Collaboration exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around meetings & collaboration — 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 Meetings & Collaboration exercises?
See the Meetings & Collaboration 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.