Practise the standard verbs for prioritising technical debt by real impact.
0 / 5 completed
1 / 5
Fill in: 'We ___ every tech debt item by its actual business impact, not by how annoying it feels to the engineer who happens to touch that file most often.'
We 'rank an item' — the standard, simple collocation for ordering tech debt by priority. The other options are less idiomatic here.
2 / 5
Fill in: 'Treating every piece of debt as equally urgent instead of ranking it can ___ the team fixing a cosmetic annoyance while a genuinely risky module stays untouched for years.'
We say unranked debt will 'leave' the wrong item fixed first — the standard, natural collocation for the resulting misallocation. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ tech debt items against the roadmap quarterly, since a debt item nobody revisits tends to quietly get pushed forever by the next urgent feature.'
We 'review an item' — the standard, simple collocation for reassessing debt priority on a schedule. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every debt item with a concrete cost, in incident risk or slowed delivery, rather than describing it only in vague terms like 'messy' or 'old'.'
We 'document an item' — the standard, simple collocation for recording the concrete justification behind a debt entry. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a small debt-reduction slot into every sprint, since a backlog that only ever gets addressed 'when there's time' effectively never gets addressed at all.'
We 'carve out a slot' — the standard, simple collocation for reserving dedicated capacity within a sprint. The other options aren't idiomatic here.