Practice · 4 min
Checklists that earn their keep
A checklist is useful when every line prevents a known, plausible mistake.
Use observable verbs
“Verify the service” is not a step. “Request the homepage and expect status 200” is. The second instruction can be repeated and reviewed.
Put risky steps near their recovery
If a change can interrupt access, state how to test it and how to undo it before presenting the command that makes the change.
Delete ceremonial lines
Long lists invite skimming. Remove steps that are automatic, cannot be checked, or merely restate the goal. What remains should be short enough to use every time.