Product managers use a precise vocabulary when working with requirements. This quiz targets the key collocations for defining, capturing, prioritising, and approving the scope of product work.
0 / 5 completed
1 / 5
Fill in: 'The product manager's job is to ___ clear requirements before engineering starts work.'
We 'define requirements' — 'define' is the canonical collocation for specifying what a feature must do in unambiguous terms. 'Write requirements' focuses on documentation rather than the act of specifying; 'create requirements' is too generic; 'set requirements' implies targets rather than a full specification.
2 / 5
Fill in: 'We held user research sessions to ___ real needs before building anything.'
We 'capture user needs' — 'capture' is the standard product collocation for recording insights from research in a structured form. 'Collect' suits data; 'find' is informal; 'gather' is close but 'capture' implies preserving and structuring insights, which is the key skill in requirements work.
3 / 5
Fill in: 'With three months to launch, the team had to ___ the most valuable features and cut the rest.'
We 'prioritise features' — 'prioritise' is the product management standard for deciding what to build first based on value and effort. 'Rank' is close but implies a fixed list rather than an ongoing process; 'sort' and 'order' are neutral terms that lack the strategic connotation of product decision-making.
4 / 5
Fill in: 'Before writing tickets, we need to ___ our assumptions about how users actually perform this task.'
We 'validate assumptions' — 'validate' is the precise product term for proving or disproving a hypothesis through evidence. 'Test assumptions' is also common but slightly more engineering-flavoured; 'check' is informal; 'confirm' implies you already expect the answer to be yes, which undermines genuine discovery.
5 / 5
Fill in: 'The director of product must ___ the final scope before engineering can begin the sprint.'
We 'sign off on scope' — 'sign off on' is the formal collocation for a stakeholder granting official approval to proceed, including their name or authority. 'Approve' is close but 'sign off on' adds the sense of formal closure. 'Accept' and 'confirm' lack this authority connotation.