A healthy feedback culture depends on precise, respectful language. This quiz covers the collocations for giving, requesting, acknowledging, and incorporating feedback in engineering teams.
0 / 5 completed
1 / 5
Fill in: 'Good engineering managers know how to ___ constructive feedback without demotivating the team.'
We 'give feedback' — 'give feedback' is the most natural and widely used collocation in professional development contexts. 'Provide feedback' is slightly more formal and common in written assessments; 'offer feedback' implies optionality; 'deliver feedback' focuses on the manner of communication and is common in coaching but less idiomatic than 'give'.
2 / 5
Fill in: 'After the sprint review, she decided to ___ input from the frontend team on the new design system.'
We 'request input' — 'request' is the formal collocation for formally inviting contributions, signalling that the response is expected. 'Ask for' is close but informal; 'seek input' is also standard; 'get input' is too casual for a structured feedback process.
3 / 5
Fill in: 'When team members raised concerns about the deployment timeline, the lead made sure to ___ those concerns publicly.'
We 'acknowledge concerns' — 'acknowledge' means to recognise that a concern is valid and has been heard, which is the first step in a healthy feedback culture. 'Address concerns' goes further, implying action; 'accept' implies complete agreement; 'note' is administrative and does not convey empathy.
4 / 5
Fill in: 'The team agreed to ___ the suggestions from the retrospective before the next sprint began.'
We 'incorporate suggestions' — 'incorporate' means to weave suggestions meaningfully into existing plans or processes. 'Use suggestions' is informal; 'apply suggestions' is close but 'apply' is more common with rules or methods; 'add suggestions' implies appending to a list rather than integrating them into practice.
5 / 5
Fill in: 'Based on the feedback, the team decided to ___ their approach to code review instead of sticking with the old process.'
We 'iterate on an approach' — 'iterate on' is the agile and engineering-standard collocation for making progressive improvements through repeated cycles. 'Change' implies a single switch; 'update' is close but focuses on a one-time modification; 'revise' is more common in writing and formal documents.