Practice public-facing postmortem vocabulary: accountability language, explaining what happened and why, public postmortem structure, and trust-rebuilding communication after incidents.
0 / 14 completed
1 / 14
A company blog post begins: 'We take full ___ for the outage that affected our customers on Tuesday.' What word fits?
'We take full responsibility' is the standard accountability phrase in public-facing postmortems. It signals that the company is not deflecting blame and is committed to preventing recurrence — a critical first step in trust rebuilding.
2 / 14
What is the recommended structure for a public postmortem?
Public postmortems should cover: (1) a plain-language timeline, (2) root cause explanation accessible to non-engineers, (3) customer impact summary, and (4) specific concrete remediation steps with timelines. Vague commitments to 'do better' undermine credibility.
3 / 14
What does 'trust-rebuilding communication' mean after a major incident?
Trust rebuilding requires follow-through: publish the postmortem, then follow up with updates as remediation items are completed. Customers and press note whether companies actually deliver on their postmortem commitments — words without action accelerate trust erosion.
4 / 14
A public postmortem says 'here is what happened and what we're doing to ___ it.' What word fits?
'What we're doing to prevent it' (prevent recurrence) is the most important section of a public postmortem. Specific, measurable commitments (e.g., 'we will add automated failover by June 30') are more credible than generic promises to improve reliability.
5 / 14
Which phrase is most appropriate to open a public postmortem blog post?
An effective public postmortem opens with concrete facts: date, duration, and a clear statement of intent. This immediately demonstrates transparency and sets expectations that the document will be specific and honest — not a PR-managed deflection.
6 / 14
PR Description
During code review, Sarah left this comment on a PR:
"This endpoint is returning 500s intermittently. We need to investigate the rate limiting."
Which of the following responses would be most appropriate for Mark, the engineering lead, to add to the PR description to communicate effectively with the team?
The correct answer highlights a concise and actionable description. Mark needs to convey that the endpoint is experiencing failures (500s) and requires investigation, specifically regarding rate limiting. Options B and D are incorrect because they either dismiss the problem or fail to provide necessary details for troubleshooting. Option C is partially correct, but doesn't emphasize the *need* to investigate, which is crucial in this scenario.
7 / 14
PR Description
During code review, Sarah left this comment on a PR:
"This endpoint is returning 500s intermittently. We need to investigate the rate limiting."
Which of the following responses would be most appropriate for Mark, the engineering lead, to add to the PR description to communicate effectively with the team?
The correct answer highlights a concise and actionable description. Mark needs to convey that the endpoint is experiencing failures (500s) and requires investigation, specifically regarding rate limiting. Options B and D are incorrect because they either dismiss the problem or fail to provide necessary details for troubleshooting. Option C is partially correct, but doesn't emphasize the *need* to investigate, which is crucial in this scenario.
8 / 14
PR Description
During code review, Sarah left this comment on a PR:
"This endpoint is returning 500s intermittently. We need to investigate the rate limiting."
Which of the following responses would be most appropriate for Mark, the engineering lead, to add to the PR description to communicate effectively with the team?
The correct answer highlights a concise and actionable description. Mark needs to convey that the endpoint is experiencing failures (500s) and requires investigation, specifically regarding rate limiting. Options B and D are incorrect because they either dismiss the problem or fail to provide necessary details for troubleshooting. Option C is partially correct, but doesn't emphasize the *need* to investigate, which is crucial in this scenario.
9 / 14
PR Description
During code review, Sarah left this comment on a PR:
"This endpoint is returning 500s intermittently. We need to investigate the rate limiting."
Which of the following responses would be most appropriate for Mark, the engineering lead, to add to the PR description to communicate effectively with the team?
The correct answer highlights a concise and actionable description. Mark needs to convey that the endpoint is experiencing failures (500s) and requires investigation, specifically regarding rate limiting. Options B and D are incorrect because they either dismiss the problem or fail to provide necessary details for troubleshooting. Option C is partially correct, but doesn't emphasize the *need* to investigate, which is crucial in this scenario.
10 / 14
John, a senior engineer, is updating the team on Slack after a recent service degradation. He writes: 'The root cause was a misconfiguration in our load balancer. We're now implementing automated health checks to prevent this from happening again.' Which of the following best describes John's communication?
John's message demonstrates proactive communication by detailing not just the problem but also the steps being taken to avoid recurrence. While transparency is present, the primary focus is on preventative action, which is a key element of effective postmortem communication. Option D is incorrect because assigning blame isn't part of a blameless postmortem.
11 / 14
During a public postmortem draft review, a stakeholder asks: 'How do we ensure our customers understand the changes we've made based on this incident?' Which of the following is the MOST appropriate response?
Option 2 represents the core of trust-rebuilding communication after an incident – clear explanation of what happened and what was done. The other options are either too technical (1), dismissive of user impact (3), or actively detrimental to rebuilding confidence (4).
12 / 14
A junior developer, Mia, is writing the description for a Pull Request that fixes an issue causing intermittent API errors. She includes the following text: 'This PR resolves a concurrency problem identified during testing. We've implemented retry logic and increased the buffer size to handle peak loads.' Which phrase best describes Mia's approach?
Mia is focusing on the 'reactive troubleshooting' aspect by describing how the system handles the errors. While root cause analysis is present, the primary emphasis is on the mitigation strategy – the retry logic and buffer increase – which directly addresses the observed symptoms. The other options misrepresent her focus.
13 / 14
David, a team lead, is presenting a postmortem to stakeholders. He says: 'We're committed to learning from this and improving our monitoring capabilities.' What does this statement primarily convey?
David's statement highlights a crucial aspect of postmortems – learning from mistakes. It signals a commitment to proactive improvements rather than simply guaranteeing prevention (option 2). The other options represent potential outcomes or justifications that are secondary to the core message of continuous improvement.
14 / 14
You're drafting a Slack message to announce the release of a postmortem. Which of the following options best sets the tone and purpose?
Option 3 is the most professional and informative tone for an initial announcement. It clearly states the purpose (sharing findings and actions) and conveys a sense of transparency and accountability. Options 1 & 2 are too terse; option 4 is overly reassuring and potentially minimizes the seriousness of the incident.
What does the "Public-Facing Postmortem Vocabulary" exercise cover?
Practice public-facing postmortem vocabulary: accountability language, explaining what happened and why, public postmortem structure, and trust-rebuilding communication after incidents.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Public-Facing Postmortem Vocabulary"?
This exercise has 14 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more External Crisis Communication exercises?
Browse the full External Crisis Communication hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.