Communicating with stakeholders requires professionalism and clarity. These exercises cover the collocations engineering managers and tech leads use when sharing updates, escalating blockers, and presenting trade-offs.
0 / 5 completed
1 / 5
The engineering manager sends a weekly digest to ___ on sprint progress.
Share updates is the professional collocation for distributing status information to a group. 'Share' implies openness and proactive communication. 'Give updates' is also common; 'send updates' is more transactional; 'tell updates' is grammatically incorrect.
2 / 5
The tech lead was instructed to ___ to senior management if the API migration fell behind schedule.
Escalate blockers is the standard professional collocation for elevating impediments to a higher authority for resolution. 'Escalate' carries the specific connotation of moving an issue up the chain of command. 'Raise' is common in British English; 'report' and 'share' are less urgent in tone.
3 / 5
Before starting the project, the team must ___ with each sponsor regarding timelines and deliverables.
Set expectations is the fixed professional collocation for establishing shared understanding of what will and will not be delivered. 'Set' is the canonical verb. 'Explain' implies one-way communication; 'state' is formal but less relational; 'show' does not collocate naturally.
4 / 5
During the architecture review, the team was asked to ___ between a microservices and a monolithic approach.
Present trade-offs is the standard collocation for formally communicating the pros and cons of technical options to stakeholders. 'Present' implies a structured, audience-facing communication. 'Explain' and 'describe' are less formal; 'show' is too vague.
5 / 5
The business analyst was assigned to ___ from all department heads before writing the specification.
Gather requirements is the canonical business analysis collocation, used in both agile and waterfall contexts. 'Gather' implies an active, structured elicitation process. 'Collect' is a close alternative; 'get' is too informal; 'obtain' is overly transactional for a collaborative process.