If you check a box in under 5 seconds without pausing…
For any pre-flight check item you can complete in under 5 seconds without pausing, treat that as evidence of ritual execution not genuine verification—pause and locate observable evidence before marking complete.
When This Fires
- During any checklist execution when you notice yourself moving through items quickly
- When a checklist "takes no time" — that's the complacency signal
- As a meta-check applied to any verification protocol
- Complements Checklists need mandatory pause points where all activity… (pause points) and Require a physical touch or verbal callout for each… (physical/verbal action) with the speed diagnostic
Common Failure Mode
Rapid-fire checking of an entire list: "Check, check, check, check — all good!" Total time: 15 seconds for a 10-item list. That's 1.5 seconds per item — not enough time for genuine verification of any item. The checklist became a click-through ritual. The boxes are marked, the psychological comfort of "having checked" is satisfied, and zero actual verification occurred.
The Protocol
(1) During checklist execution, monitor your speed on each item. (2) If you complete any item in under 5 seconds → stop. You did not verify. (3) Return to the item and perform genuine verification: navigate to the state, observe the current value, compare to expected, confirm the match. This will take 5-30 seconds depending on the item. (4) If multiple items were completed in rapid succession → return to the beginning. All rapid-checked items need re-verification. (5) Use the 5-second threshold as a calibration tool: if most items take under 5 seconds, either the checklist contains items that don't need checking (Checklists are 5-10 items that catch what competent people… — remove them) or you're in a complacency pattern that needs the structural interventions of Checklists need mandatory pause points where all activity… and Require a physical touch or verbal callout for each….