If you check a box in under 5 seconds without pausing…

Why This Is a Rule

Five seconds is the diagnostic threshold because genuine verification requires time: navigating to a setting, reading a value, comparing it to the expected state, and confirming the match. This sequence cannot be completed in under 5 seconds for any non-trivial item. If you marked a checklist item "complete" in 3 seconds, you didn't perform these steps — you checked the box based on memory, expectation, or autopilot. The speed itself is the diagnostic signal.

This is the self-monitoring complement to Require a physical touch or verbal callout for each… (physical/verbal verification). Require a physical touch or verbal callout for each… tells you how to verify. This rule tells you how to detect when you're not actually verifying. The 5-second threshold is a simple, always-available meta-check: if it was too fast, it wasn't real verification.

The failure mode this catches is invisible to the practitioner. When you check a box in 2 seconds, it feels like you verified it — the subjective experience of checking occurred. But the verification was based on cached state ("it was correct last time") rather than observed current state. The 5-second threshold makes this invisible failure mode visible.

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….