Practice vocabulary for communicating technical risks to stakeholders: risk framing, probability vs. impact, risk treatment options, service boundary risk, and escalation language.
0 / 10 completed
1 / 10
An engineer says 'if we don't address this, we risk outage during Black Friday'. What makes this risk communication effective?
Effective risk communication connects technical risk to business consequences the stakeholder cares about. 'We have a race condition in the checkout service' is abstract; 'we risk a checkout outage during Black Friday — our highest revenue day' is concrete and urgent. Time-bounding the risk ('during Black Friday') creates appropriate urgency and helps prioritise the remediation.
2 / 10
'The probability is low but impact is high.' How should this type of risk be handled?
Risk management uses a probability × impact matrix. Low probability / high impact risks (e.g., database corruption, security breach, Black Friday outage) may have a very low expected annual cost when multiplied out, but their catastrophic nature justifies proactive mitigation. Stakeholders must understand that unlikely does not mean ignorable when the impact is irreversible or reputation-damaging.
3 / 10
'We recommend accepting/mitigating/transferring this risk.' What do these three options mean?
The four standard risk treatment options are: Accept (acknowledge and document — appropriate for low risks or when mitigation cost exceeds risk cost), Mitigate (reduce probability or impact through action), Transfer (shift financial or operational consequence to a third party — e.g., insurance, vendor SLA), and Avoid (eliminate the risk by not doing the activity). Presenting options lets stakeholders make an informed decision rather than just hearing a problem.
4 / 10
'The risk is bounded to one service.' Why is communicating risk boundaries important?
Stakeholders often fear worst-case scenarios. Communicating that a risk is bounded — 'this only affects the reporting service, the payment service is on a separate stack and is isolated' — helps stakeholders calibrate their response. Bounded risks have lower potential impact, require narrower remediation, and are less likely to cascade. Clearly communicating boundaries prevents over-reaction and helps prioritise.
5 / 10
What is the key difference between communicating a risk to engineers versus to business stakeholders?
Engineers need technical context to understand and fix the problem. Stakeholders need a different set of information: what is the business impact if this risk materialises, how likely is it, what does it cost to address it, and what happens if we don't? Translating technical risk into business decision language — without burying it in jargon — is a core skill for senior engineers and engineering managers.
6 / 10
Review Comment: 'This change introduces a potential race condition. While the probability of it occurring is low, if it does happen during peak load, we could experience intermittent data corruption. I've added a mutex to mitigate.'
Which best describes the communication style in this code review comment?
This comment demonstrates proactive mitigation by not just stating a problem (race condition) but also detailing the steps taken to address it (adding a mutex). Options A and C are too passive; option D focuses solely on the technical detail without acknowledging or addressing the risk. It's crucial in developer communication to balance technical explanation with risk awareness.
7 / 10
Slack Message from @johndoe: 'Just ran some tests on the new API endpoint. The response time is consistently above 300ms – a significant deviation from our target of 200ms. It *might* be related to the recent database migration.'
What type of risk communication is @johndoe primarily conveying?
@johndoe is communicating operational risk by focusing on measurable performance deviations from expected targets. While the database migration *could* be related, the primary concern is the impact of the slow response times. The other options introduce concepts not directly present in the message; a key element of effective communication is accurately identifying the type of risk.
8 / 10
PR Description: 'This PR updates the user authentication flow. The new implementation reduces the attack surface by limiting direct access to sensitive data. There's a small chance of an attacker exploiting this vulnerability (low probability), but the potential impact is extremely high – unauthorized access to user accounts. (CVSS score: 8.5)'.
What aspect of risk communication does this PR description emphasize?
This PR description prioritizes impact-focused communication by explicitly stating 'the potential impact…is extremely high.' While a CVSS score is included, it's used to support this emphasis on the consequences. The other options represent different aspects of risk management that aren't directly highlighted here.
9 / 10
Standup Update from @sarahlee: 'I'm currently investigating a potential bottleneck in the message queue processing. We're seeing occasional delays, and while it hasn't caused any outages yet, we need to understand the root cause before it impacts our service availability. The delay is intermittent – difficult to reproduce.'
How should Sarah best communicate this situation during the standup?
Sarah should raise awareness and request support. While a critical incident might be warranted later, at this stage, she's focusing on understanding the issue's potential impact and needs help to investigate. Simply accepting responsibility or providing an overly detailed analysis would be premature given the intermittent nature of the problem.
10 / 10
API Response:HTTP/1.1 503 Service Unavailable Error Message: 'Database connection timeout' Timestamp: 2024-10-27T10:30:00Z
Which of the following best describes the risk being communicated through this API response?
The API response clearly indicates a 'Database connection timeout,' pointing to a risk related to service dependencies. The system's availability is impacted because it cannot connect to the required database. While other risks could be involved, this specific message directly highlights a dependency issue.
This exercise, "Technical Risk Communication Vocabulary", tests your understanding of tech-to-business vocabulary and phrasing through 10 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 10 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this Tech-to-Business exercise for?
It's designed for IT professionals and learners who want to sound natural discussing tech-to-business topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more Tech-to-Business exercises?
Browse the full Tech-to-Business exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.