Technical Risk Communication: English Collocations
Communicating technical risk clearly is one of the most important — and underrated — skills in software engineering. From surfacing risks early and quantifying their likelihood to mitigating, accepting, and escalating them to stakeholders, each step requires precise vocabulary. This exercise covers the collocations used in risk registers, architecture reviews, and programme governance discussions.
0 / 5 completed
1 / 5
The tech lead asked the team to ___ any technical risks in the project charter before the kickoff meeting.
Surface technical risks is the natural risk communication collocation — 'surfacing' risks means bringing them into the open for stakeholders to see and act on. 'Identify' is the internal analytical step; 'flag' is used for urgent one-off risks; 'list' is the mechanical recording. 'Surface' is the preferred term when the goal is making risks visible to a wider audience.
2 / 5
The senior engineer used a risk matrix to ___ the likelihood and impact of each identified technical risk.
Quantify the risk is the precise risk management collocation — a risk matrix is used to 'quantify' risk by scoring likelihood and impact numerically. 'Assess' is the broader activity that includes quantification; 'evaluate' is qualitative; 'measure' implies a precise instrument. 'Quantify' is the specific term for assigning numerical values to risk attributes.
3 / 5
The product manager was asked to review the risk register and decide which risks to ___ given the current sprint capacity.
Accept a risk is the formal risk management collocation — 'accepting' a risk is a deliberate, documented decision to proceed without mitigation. 'Ignore' implies unawareness; 'skip' is informal; 'deprioritise' means reducing its ranking, not making a formal acceptance decision. 'Accept' is one of the four standard risk response strategies (accept, mitigate, transfer, avoid).
4 / 5
The engineering team proposed adding circuit breakers and retries to ___ the risk of downstream service failures.
Mitigate the risk is the standard technical risk response collocation — engineering controls 'mitigate' risks by reducing their likelihood or impact. 'Reduce' focuses on the outcome; 'prevent' implies eliminating the risk entirely; 'address' is vague. 'Mitigate' is the canonical risk management term for the strategy of reducing but not necessarily eliminating a risk.
5 / 5
The engineering lead committed to ___ technical risk updates to the programme board every two weeks.
Communicate risk updates is the professional stakeholder management collocation — risk status is 'communicated' regularly to ensure stakeholders can make informed decisions. 'Share' is informal; 'send' focuses on delivery mechanism; 'present' implies a live meeting. 'Communicate' is the standard verb for structured, intentional risk reporting to a governing body.