Require a physical touch or verbal callout for each checklist item — prevent autopilot execution that checks without verifying
For each checklist item, require a physical action (touching the control) or verbal callout (saying the condition aloud) to prevent autopilot execution where the ritual completes without actual verification.
Why This Is a Rule
Japanese rail operators use "pointing and calling" (shisa kanko): physically pointing at each signal and saying its state aloud before proceeding. This seemingly ritualistic practice reduces errors by 85% compared to silent visual checks. The mechanism is attentional engagement: a physical action (pointing, touching) and a verbal action (calling out) require motor cortex and language processing engagement that a purely visual check doesn't. You can visually "scan" a checklist while your attention is elsewhere; you can't physically point and verbally call out while disengaged.
Checklist complacency — completing the ritual of checking without performing actual verification — is the primary failure mode of mature checklists (Checklists need mandatory pause points where all activity stops — verification run as background process catches nothing, If you check a box in under 5 seconds without pausing, you didn't verify — you performed a ritual). After using the same checklist dozens of times, the checking behavior becomes automatic while the verification function atrophies. Physical and verbal engagement break this automaticity by requiring conscious motor actions that can't be performed on autopilot.
For personal checklists, the equivalent is: physically touching the item being verified (tap the setting on screen, handle the object, open the file) or saying the verification aloud ("Backup confirmed. Tests passing. Credentials rotated"). Either action forces a moment of conscious engagement that silent box-ticking doesn't.
When This Fires
- When designing verification procedures for critical checklist items
- When a checklist has been in use long enough that complacency risk is high
- When checklist execution feels automatic and you suspect verification quality has degraded
- Complements Checklists need mandatory pause points where all activity stops — verification run as background process catches nothing (pause points) with the specific verification technique at each pause
Common Failure Mode
Silent visual confirmation: glancing at a screen and checking the box based on what you expected to see rather than what you actually observed. Confirmation bias makes you "see" the expected state even when the actual state differs. Physical touch or verbal callout breaks this by forcing active engagement with the actual current state rather than the expected state.
The Protocol
(1) For each critical checklist item, define the verification action: what must you physically do or verbally confirm? (2) Physical verification: touch the control, open the file, navigate to the setting. Confirm the actual state, not the assumed state. (3) Verbal verification: say the state aloud: "Database backup: completed at 3:47 PM." Speaking forces you to encode the actual observation in language, which requires more cognitive engagement than a mental acknowledgment. (4) Only after performing the physical or verbal action → mark the item complete. (5) If you catch yourself checking the box before the physical/verbal verification → that's complacency in action. Slow down and re-verify with the engagement step.