Loading
Because the process is known rather than written. Under pressure the person doing it skips the step that seemed unnecessary, and the reason it existed is discovered afterwards.
A checklist is the set of steps inside one task, ticked as they are done, with the person and time recorded against each.
Items are ticked individually and the task cannot close with mandatory items outstanding. Each tick keeps who and when, so the record is evidence rather than a memory.
A production cutover has eleven steps in a required order. The checklist blocks completion until each is ticked, and the record shows who verified the backup and at what time.
They will not make a step happen. A tick records a claim; whether the backup was verified is between the person and their conscience.
The completed checklist stays with the task, so an audit or a post-mortem reads what was actually done rather than what the runbook says.
Yes, and the task cannot be completed while one is outstanding.
Yes, per task type, which is how a runbook stops being a document.
Yes, with who and when, including un-ticks.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.