5 exercises — writing SEV-level notifications, impact statements, blameless root cause analysis, and time-bound action items.
0 / 18 completed
1 / 18
A production service has gone down. You need to send an initial incident notification. Which opening sentence is most effective?
Incident notifications must lead with severity, system, impact, and start time — the four facts stakeholders need first. Use the format: SEV-[N] | [System] [Status] | Impact: [user/business scope] | Since: [time UTC]. Option A is vague ("some kind of issue"). Option C sounds apologetic rather than informative. Option D starts with a probable cause before confirming the impact — cause analysis belongs in a later update, not the first notification.
2 / 18
Complete the impact statement in this incident report: "Users _____ (affect) by this incident are those attempting checkout with a saved payment method. Orders using PayPal _____ (not/affect)."
Use present simple passive to describe the current state of the incident: "Users are affected" (right now, ongoing). This is more direct and natural than the participial phrase "users being affected" or the relative clause "users that are affected". The negative, "are not affected", clearly scopes the impact — limiting scope is a key part of professional incident communication (it reduces panic and helps triage).
3 / 18
You are writing the root cause section of a post-mortem. Which wording follows blameless post-mortem principles?
Blameless post-mortems describe system and process failures, not individual ones. Option C is correct: it names the technical artefact (misconfigured environment variable), the action (deployed to production), and the process gap (bypassing environment validation in CI). Option A names an individual — this violates blameless principles and discourages psychological safety. Option B still uses "developer error" (blame). Option D is informal and lacks precision.
4 / 18
You're writing action items at the end of a post-mortem. Which action item is written correctly?
Post-mortem action items must be specific, measurable, assignable, and time-bound. Option C is the only one that meets all four criteria: it specifies the exact technical action (alerting on connection pool exhaustion, threshold >80%), names an owner (@alice), and has a deadline (2024-02-15). Options A and D use vague language ("probably", "more checks across the board"). Option B lacks a deadline and an individual owner — "backend team" is not an owner.
5 / 18
Choose the best phrase to complete a resolution update: "The incident _____ at 15:47 UTC after we _____ the connection pool limit and _____ the affected instances."
Past simple passive (was resolved) is standard for incident resolution announcements — the incident is a specific completed event. The subsequent actions (increased the connection pool limit, restarted the affected instances) are also past simple — a completed sequence of actions in the past. Present perfect ("has been resolved") would work in a real-time update ("we're happy to report…"), but past simple is cleaner for formal post-mortem writing. The "did + base verb" construction (Option D) is emphatic and sounds unnatural here.
6 / 18
Sarah: "I've just reviewed the PR and noticed a potential race condition in the payment processing module. It seems like we're updating the database concurrently without proper locking."
Which of the following responses would be most appropriate for Mark, the lead developer, to send back on Slack?
The best response acknowledges Sarah's observation while also prompting for further detail. The incorrect options either minimize the severity (Insufficient), offer overly positive feedback without seeking more information (Excellent!), or shift responsibility without encouraging deeper investigation (send a detailed report). A good developer communication focuses on understanding the *impact* of the issue and planning next steps, as highlighted by option 2.
7 / 18
Mark: "Okay, Sarah. Thanks for flagging that. Let's investigate the locking mechanism in more detail and ensure we're using appropriate transactions to prevent data corruption."
This response is most appropriate because it acknowledges Sarah's concern and proposes a clear next step: investigating the locking mechanism. It avoids taking blame (option 3) and provides a concrete action – further analysis – rather than offering a simplistic or vaguely worded solution. Options A and C are too passive, while option B doesn't demonstrate any proactive engagement with the issue.
8 / 18
Sarah: "I've just reviewed the PR and noticed a potential race condition in the payment processing module. It seems like we're updating the database concurrently without proper locking."
Which of the following responses would be most appropriate for Mark, the lead developer, to send back on Slack?
The best response acknowledges Sarah's observation while also prompting for further detail. The incorrect options either minimize the severity (Insufficient), offer overly positive feedback without seeking more information (Excellent!), or shift responsibility without encouraging deeper investigation (send a detailed report). A good developer communication focuses on understanding the *impact* of the issue and planning next steps, as highlighted by option 2.
9 / 18
Mark: "Okay, Sarah. Thanks for flagging that. Let's investigate the locking mechanism in more detail and ensure we're using appropriate transactions to prevent data corruption."
This response is most appropriate because it acknowledges Sarah's concern and proposes a clear next step: investigating the locking mechanism. It avoids taking blame (option 3) and provides a concrete action – further analysis – rather than offering a simplistic or vaguely worded solution. Options A and C are too passive, while option B doesn't demonstrate any proactive engagement with the issue.
10 / 18
Sarah: "I've just reviewed the PR and noticed a potential race condition in the payment processing module. It seems like we're updating the database concurrently without proper locking."
Which of the following responses would be most appropriate for Mark, the lead developer, to send back on Slack?
The best response acknowledges Sarah's observation while also prompting for further detail. The incorrect options either minimize the severity (Insufficient), offer overly positive feedback without seeking more information (Excellent!), or shift responsibility without encouraging deeper investigation (send a detailed report). A good developer communication focuses on understanding the *impact* of the issue and planning next steps, as highlighted by option 2.
11 / 18
Mark: "Okay, Sarah. Thanks for flagging that. Let's investigate the locking mechanism in more detail and ensure we're using appropriate transactions to prevent data corruption."
This response is most appropriate because it acknowledges Sarah's concern and proposes a clear next step: investigating the locking mechanism. It avoids taking blame (option 3) and provides a concrete action – further analysis – rather than offering a simplistic or vaguely worded solution. Options A and C are too passive, while option B doesn't demonstrate any proactive engagement with the issue.
12 / 18
Sarah: "I've just reviewed the PR and noticed a potential race condition in the payment processing module. It seems like we're updating the database concurrently without proper locking."
Which of the following responses would be most appropriate for Mark, the lead developer, to send back on Slack?
The best response acknowledges Sarah's observation while also prompting for further detail. The incorrect options either minimize the severity (Insufficient), offer overly positive feedback without seeking more information (Excellent!), or shift responsibility without encouraging deeper investigation (send a detailed report). A good developer communication focuses on understanding the *impact* of the issue and planning next steps, as highlighted by option 2.
13 / 18
Mark: "Okay, Sarah. Thanks for flagging that. Let's investigate the locking mechanism in more detail and ensure we're using appropriate transactions to prevent data corruption."
This response is most appropriate because it acknowledges Sarah's concern and proposes a clear next step: investigating the locking mechanism. It avoids taking blame (option 3) and provides a concrete action – further analysis – rather than offering a simplistic or vaguely worded solution. Options A and C are too passive, while option B doesn't demonstrate any proactive engagement with the issue.
14 / 18
'The service is experiencing intermittent high latency. Users are reporting slow response times when accessing the API endpoint /users. Initial investigation suggests a potential bottleneck in the database query execution.' Which of the following responses best acknowledges the issue and requests further information from the developer, aligning with effective code review practices?
This option directly requests crucial details (affected users, response times) and asks for log examination – key elements of a productive code review. The other options are overly aggressive, dismissive, or offer irrelevant technical advice. Focusing on specific data points allows the developer to pinpoint the root cause efficiently.
15 / 18
'Hey team, we have an outage! Users can't access our website. Please investigate ASAP.' Receiving this message in a Slack channel, what is the MOST appropriate follow-up response to request further details and coordinate efforts?
Requesting the outage status and identifying the responsible team member are critical for effective incident response. The other options are passive or escalate unnecessarily. A clear request for information ensures everyone understands the situation and their role in resolving it.
16 / 18
'Fixed a bug where users were getting incorrect order totals.' You are writing the PR description for a change that resolved a critical issue impacting revenue. Which of the following descriptions is MOST effective in communicating the impact and resolution to your team?
This option provides context about the impact (incorrect order totals) and briefly outlines the root cause. This is essential for other developers to understand the significance of the change and how it relates to broader system functionality. The others are too vague or focus solely on the technical implementation.
17 / 18
'I was working on the payment processing module.' During your daily stand-up, you're asked to provide a brief update on your work. Considering the context of a recent incident involving race conditions in that same module, which statement best reflects an appropriate and informative response?
This response directly acknowledges the previous incident and connects your work to it. It demonstrates awareness of ongoing issues and provides valuable context for your team. The other options are too generic or avoid discussing the relevant problem.
18 / 18
'The incident resulted in a 95% drop in user traffic for approximately 30 minutes. We immediately deployed a hotfix and restored service.' Which of the following statements BEST summarizes the key components of this incident's description, demonstrating effective communication principles?
This option concisely captures the critical metrics (95% traffic drop, duration), the immediate action taken (hotfix), and the next step (investigation). It's a balanced summary that provides sufficient information without unnecessary technical detail. The other options lack key details or are overly simplistic.
What does the "Incident Reports & Post-mortems — Writing Exercise" exercise cover?
Practice writing professional incident reports, SEV notifications, root cause analyses, and blameless post-mortems. 5 interactive exercises.
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 "Incident Reports & Post-mortems — Writing Exercise"?
This exercise has 18 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 Email & Writing exercises?
Browse the full Email & Writing 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.