Practice vocabulary for facilitating challenging postmortem meetings: handling defensiveness, blame, silence, and disagreement.
0 / 10 completed
1 / 10
When participants in a postmortem become defensive about their decisions, the facilitator should:
When the team is defensive — refocus on systems. Remind participants that postmortems analyze system conditions, not individual blame.
2 / 10
When a manager is steering the postmortem toward assigning personal blame, the facilitator should:
When the manager is trying to assign blame — redirect to contributing factors. Ask 'What conditions made this outcome possible?' instead.
3 / 10
When a key engineer is not speaking during the postmortem, the facilitator should:
When the engineer is silent — create psychological safety. Use open questions: 'What did you observe from your side?' with no pressure.
4 / 10
When a postmortem discussion goes significantly over its scheduled time, the facilitator should:
When the postmortem is running over time — park items. Capture them in a 'parking lot' and assign async owners to prevent meeting fatigue.
5 / 10
When participants have fundamentally different views on what the root cause was, the facilitator should:
Facilitating disagreement about root cause involves documenting multiple hypotheses, testing each against evidence, and seeking consensus through structured analysis.
6 / 10
Review Comment: 'This code is fine. It works.' (regarding a recently deployed feature with known performance issues). As the tech lead, what's your most appropriate response to this review comment during a postmortem discussion?
This scenario tests recognizing a surface-level response. The correct answer acknowledges functionality while immediately pivoting to address the underlying issue – the performance problems highlighted in the original deployment. Options A and C are insufficient; they don't engage with the problem. Option D is too confrontational for an initial response.
7 / 10
Slack Message: '@john_doe, I think you should have caught this bug earlier.'
You're a senior developer receiving this message from a junior colleague about a recently discovered production issue. During a postmortem, how do you best frame your contribution to the discussion?
This question tests constructive communication. The correct response emphasizes learning and prevention rather than assigning blame. Option A is unnecessarily aggressive and unproductive. Option C avoids the core issue, while option D shifts responsibility inappropriately. Focusing on 'how' is crucial for a positive postmortem.
8 / 10
PR Description: (For a new feature) 'Fixed the UI bug.'
During a postmortem addressing an incident caused by this same UI element, what's the *most* valuable question to ask the developer who wrote the PR?
The key here is understanding the *process* and not just the outcome. Option A tests for a basic check but doesn't address potential underlying problems. Option C simply confirms functionality without exploration. Option D is too vague – focusing on the root cause requires probing the developer's actions.
9 / 10
Standup Update: 'Yesterday, I spent a lot of time debugging the authentication flow.'
The team is discussing an incident that impacted user login. As the Scrum Master facilitating the postmortem, what's your primary goal when prompting this developer for more detail during the discussion?
This question focuses on understanding the *technical approach*. Option A pushes for a simplistic diagnosis. Option C is about process adherence, not problem-solving. Option D is irrelevant to identifying root causes; it's simply an observation.
10 / 10
API Response: (Error message from a microservice) `500 Internal Server Error - Database connection failed.`. During a postmortem regarding repeated outages linked to this service, what's the most effective way to frame the discussion around potential contributing factors?
The API response indicates a technical problem, not a systemic flaw. The correct answer emphasizes data analysis – reviewing logs and metrics for patterns. Options A and C are blaming statements. Option D suggests a solution without understanding the underlying cause.
What will I practice in "Facilitating Difficult Postmortems"?
This is a Post Incident Facilitation exercise set. It walks through 10 scenario-based multiple-choice questions built around real usage of post incident facilitation terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 10 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the post incident facilitation vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Post Incident Facilitation exercises?
See the Post Incident Facilitation exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — post incident facilitation vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.