Architecture Decision Record Language Collocations
Practise the standard verbs for writing lasting, useful architecture decision records.
0 / 5 completed
1 / 5
Fill in: 'We ___ an architecture decision record the moment a significant choice is made, so the reasoning is captured while it's still fresh, not reconstructed months later from memory.'
We 'write a record' — the standard, simple collocation for documenting a significant technical decision. The other options are less idiomatic here.
2 / 5
Fill in: 'Skipping the record for a decision that felt obvious at the time can ___ a future engineer reversing it, unaware the same option was already tried and rejected.'
We say a missing record will 'leave' a future engineer repeating past mistakes — the standard, natural collocation for the resulting gap. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ every rejected alternative in the record too, since knowing what was considered and ruled out is often as useful as knowing what was chosen.'
We 'list an alternative' — the standard, simple collocation for recording options considered during a decision. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ an old record rather than editing it in place once circumstances change, since a decision's original context should stay untouched and honestly dated.'
We 'supersede a record' — the standard, established collocation for formally replacing an outdated decision with a new one. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ the record against the team's actual constraints at the time, budget, deadline and staffing, so a later reader judges the decision fairly, not with hindsight.'
We 'frame a record' — the standard, simple collocation for situating a decision within its original context. The other options are less idiomatic here.