Practise the standard verbs for keeping on-call runbooks accurate after incidents.
0 / 5 completed
1 / 5
Fill in: 'We ___ the on-call runbook right after every incident, rather than a step nobody's actually corrected since it went stale.'
We 'update a runbook' — the standard, simple collocation for revising incident-response steps after an incident. The other options are less idiomatic here.
2 / 5
Fill in: 'A stale runbook step during a live incident can ___ the on-call engineer chasing a fix nobody's actually documented correctly.'
We say a stale step will 'leave' an engineer chasing an undocumented fix — the standard, natural collocation for the resulting delay. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ every new failure mode into the runbook, rather than a workaround nobody else on-call can actually find.'
We 'add a failure mode' — the standard, simple collocation for expanding a runbook with newly discovered issues. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every runbook step against the current system architecture, rather than an instruction nobody's actually re-tested.'
We 'verify a step' — the standard, simple collocation for confirming a runbook still matches the live system. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ runbook accuracy in the quarterly on-call retro, rather than a doc nobody's actually walked through since it was written.'
We 'review accuracy' — the standard, simple collocation for periodically checking a runbook is still correct. The other options aren't idiomatic here.