Practise the standard verbs for running a cross-team RFC review to a clear decision.
0 / 5 completed
1 / 5
Fill in: 'We ___ the RFC to every affected team well before the review meeting, so a stakeholder isn't seeing the proposal for the first time live.'
We 'circulate an RFC' — the standard, established collocation for distributing a proposal for advance review. The other options aren't the recognised term here.
2 / 5
Fill in: 'Sending an RFC out without a clear review deadline can ___ a decision drifting for weeks with no one team feeling obliged to respond.'
We say a missing deadline will 'leave' a decision drifting — the standard, natural collocation for the resulting delay. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ written feedback from each affected team in the document itself, so an objection is recorded before the proposal is considered approved.'
We 'solicit feedback' — the standard, established collocation for actively requesting input on a proposal. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ an unresolved objection explicitly in the RFC status, rather than letting silence be read as tacit agreement from a team that hasn't replied.'
We 'flag an objection' — the standard, simple collocation for marking an unresolved concern clearly. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the RFC with a clear decision and rationale once every raised concern has been addressed, so the outcome is unambiguous going forward.'
We 'finalize an RFC' — the standard, established collocation for closing out a proposal with a recorded decision. The other options aren't the recognised term here.