Roadmap discussions demand specific verb-noun pairings. Practise the collocations that product and engineering teams use every day.
0 / 5 completed
1 / 5
Fill in: 'We plan to ___ the dark-mode feature in Q3 once the design is finalised.'
We 'ship a feature' — 'ship' is the dominant engineering collocation for delivering working software to users. 'Launch' suits products/campaigns; 'release' is broader; 'push' specifically means pushing code to a repository, not delivering the feature end-to-end.
2 / 5
Fill in: 'We need to ___ priorities before the roadmap is published or teams will work at cross purposes.'
We 'align on priorities' — 'align on' is the standard phrase for reaching shared understanding across stakeholders. 'Agree with' requires an object person; 'settle' is informal and often implies conflict; 'lock in' means to finalise, not to reach shared understanding.
3 / 5
Fill in: 'The committee decided to ___ several low-priority items ___ of the roadmap to free up bandwidth.'
We 'move items out' (of the roadmap) — this is the standard phrase for deferring or removing work from a plan. 'Take away' implies physical removal; 'drop off' is informal; 'pull back' usually means to reduce scope, not remove an item entirely.
4 / 5
Fill in: 'The PM wants to ___ clear milestones so progress is visible to leadership every quarter.'
We 'set milestones' — 'set' is the fixed-collocation verb for establishing goals, deadlines, or markers. 'Make milestones' is grammatical but non-idiomatic; 'put milestones' requires a preposition; 'create milestones' is acceptable but less idiomatic in planning speech.
5 / 5
Fill in: 'We use a shared dashboard to ___ progress against the roadmap each week.'
We 'track progress' — 'track' is the standard collocation for continuously monitoring advancement toward goals. 'Measure progress' focuses on quantification rather than ongoing monitoring; 'follow progress' sounds informal; 'check progress' implies a one-time review.