Practice incident communication vocabulary: status page update language, investigating/identified/restored phrases, stakeholder notification cadence, and all-clear declaration.
0 / 15 completed
1 / 15
A status page update reads: "We are investigating reports of intermittent errors affecting the payments service. We will provide an update in 30 minutes." What communication principle does this follow?
'We are investigating' is the first phase of incident communication. The key principle: communicate early, even with limited information. Silence breeds anxiety and speculation. The phrase signals: we know about it, we are actively working on it, and we will tell you more in 30 minutes. The update commitment is critical — it tells customers when to stop refreshing the page and prevents support ticket floods from customers who do not know if anyone is aware.
2 / 15
A status page update is changed from 'Investigating' to: "We have identified the root cause — a misconfigured load balancer rule — and are implementing a fix. Service should be restored within 15 minutes." What does this phase of communication signal?
The 'identified root cause' update is a turning point in customer confidence. It answers the most anxious customer question: 'do they even know what's wrong?' The language pattern: state the cause in plain terms (not technical jargon), give a time estimate, and maintain the update cadence commitment. Avoid over-promising on resolution time — 'approximately 15 minutes' with a 30-minute buffer is better than 'fixed in 5 minutes' that slips to an hour.
3 / 15
A status page update reads: "Service has been restored. All systems are operating normally. We are monitoring closely to ensure stability." What purpose does 'monitoring closely' serve in this message?
'Monitoring closely' is standard post-resolution language. It covers a real concern: incidents sometimes recur shortly after mitigation if the fix does not fully address the root cause. Including it in the restoration message: reassures customers the team is still paying attention, sets expectations that a post-mortem will follow, and maintains trust. Follow it with a final update after a suitable monitoring window: 'Stability has been confirmed. Incident closed. Post-mortem to follow.'
4 / 15
An incident manager sets a 'stakeholder notification cadence' of every 30 minutes during a SEV-1. What is a notification cadence?
Notification cadence prevents the communications lead from being reactive — constantly fielding 'any updates?' questions from executives and customers. By pre-committing to a cadence ('update every 30 minutes'), stakeholders know exactly when to expect the next update and stop interrupting the responders. Common cadences by severity: SEV-1 (every 15-30 min internal, every 30-60 min external), SEV-2 (every 30-60 min internal, every 60-120 min external). The cadence is reset when key status changes occur.
5 / 15
An incident commander announces on the bridge: "All-clear — incident is resolved, bridge is closed." What does the all-clear declaration formally signal?
The all-clear is important because incidents can drag on without a clear end. Without a formal close, responders stay on the bridge 'just in case,' wasting energy. The all-clear transitions the incident: response → post-incident. It triggers: closing the status page incident, drafting the internal incident summary, scheduling the post-mortem, and sending the final customer update. Common all-clear language: 'Service is stable. Monitoring period complete. Bridge is closed. Post-mortem in 48 hours.'
6 / 15
Sarah, the lead engineer, is drafting a Slack message to update her team about a degraded API endpoint. The message reads: 'Hey team, experiencing some latency with the /users endpoint. Investigating.' What does 'investigating' primarily convey in this context?
'Investigating' signals that the problem is acknowledged but not yet fully understood. It's a crucial step before proposing a solution or setting an expectation of immediate fixes. Using 'investigating' avoids prematurely committing to a resolution while buying time for diagnosis – it's far better than simply stating 'problem'.
7 / 15
David is writing the description for a Pull Request that introduces a fix for a critical bug. He writes: 'Fixed a race condition in the authentication service. This PR addresses intermittent login failures.' What best describes the purpose of stating 'intermittent login failures'?
The phrase 'intermittent login failures' is vital for communicating the *impact* of the bug. While technical details are important, framing the issue with its effects—how it manifested—helps stakeholders (product managers, support) understand the urgency and potential consequences of the change. It moves beyond just fixing a code issue to describing its real-world implications.
8 / 15
Maria, an incident manager, is setting up automated notifications for a high-priority (SEV-1) incident. She configures the system to send updates every 5 minutes. What does this configuration represent?
The configuration represents a 'notification cadence' – the frequency at which updates are sent. During a SEV-1 incident, regular, short updates are essential to maintain situational awareness and ensure rapid response. This isn't about legal requirements; it's about proactive communication during crisis.
9 / 15
Ben is drafting a status update message after resolving a complex outage. The message reads: 'We've implemented a rollback to the previous stable version and are conducting thorough post-mortem analysis.' What does 'conducting thorough post-mortem analysis' primarily indicate?
'Post-mortem analysis' refers to a critical process of reviewing an incident *after* it's resolved. The goal is not just identifying the root cause (which might be done separately), but also documenting what went wrong and how to prevent similar issues in the future – learning from mistakes is key.
10 / 15
Emily needs to communicate a complex technical issue to a non-technical stakeholder. The issue involves a subtle performance bottleneck in a microservice. Which phrasing would be MOST effective?
Using simplified language like 'a slow part of the system' avoids overwhelming the stakeholder with technical jargon. Focusing on the *impact* – affecting user experience – is more relatable and allows the stakeholder to understand the severity without needing a deep technical understanding. Specificity about the problem itself isn't helpful here.
11 / 15
Sarah, the lead engineer, is drafting a Slack message to update her team about a degraded API endpoint. The message reads: 'Hey team, experiencing some latency with the /users endpoint. Investigating.' What does 'investigating' primarily convey in this context?
'Investigating' signals that the problem is acknowledged but not yet fully understood. It's a crucial step before proposing a solution or setting an expectation of immediate fixes. Using 'investigating' avoids prematurely committing to a resolution while buying time for diagnosis – it's far better than simply stating 'problem'.
12 / 15
David is writing the description for a Pull Request that introduces a fix for a critical bug. He writes: 'Fixed a race condition in the authentication service. This PR addresses intermittent login failures.' What best describes the purpose of stating 'intermittent login failures'?
The phrase 'intermittent login failures' is vital for communicating the *impact* of the bug. While technical details are important, framing the issue with its effects—how it manifested—helps stakeholders (product managers, support) understand the urgency and potential consequences of the change. It moves beyond just fixing a code issue to describing its real-world implications.
13 / 15
Maria, an incident manager, is setting up automated notifications for a high-priority (SEV-1) incident. She configures the system to send updates every 5 minutes. What does this configuration represent?
The configuration represents a 'notification cadence' – the frequency at which updates are sent. During a SEV-1 incident, regular, short updates are essential to maintain situational awareness and ensure rapid response. This isn't about legal requirements; it's about proactive communication during crisis.
14 / 15
Ben is drafting a status update message after resolving a complex outage. The message reads: 'We've implemented a rollback to the previous stable version and are conducting thorough post-mortem analysis.' What does 'conducting thorough post-mortem analysis' primarily indicate?
'Post-mortem analysis' refers to a critical process of reviewing an incident *after* it's resolved. The goal is not just identifying the root cause (which might be done separately), but also documenting what went wrong and how to prevent similar issues in the future – learning from mistakes is key.
15 / 15
Emily needs to communicate a complex technical issue to a non-technical stakeholder. The issue involves a subtle performance bottleneck in a microservice. Which phrasing would be MOST effective?
Using simplified language like 'a slow part of the system' avoids overwhelming the stakeholder with technical jargon. Focusing on the *impact* – affecting user experience – is more relatable and allows the stakeholder to understand the severity without needing a deep technical understanding. Specificity about the problem itself isn't helpful here.
What will I practise in "Incident Communication Vocabulary"?
Practice incident communication vocabulary: status page update language, investigating/identified/restored phrases, stakeholder notification cadence, and all-clear declaration.
How many exercises are in this module?
This module has 15 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
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.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Incident Command Language exercises?
Browse the full Incident Command Language hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.