Deliberate Action
Pause, vocalize, and gesture before acting to eliminate automatic errors and build team resilience
Deliberate action is a mechanism where operators pause before any action, vocalize what they are about to do, gesture toward the relevant control or document, and only then execute. The practice introduces a conscious break between intention and action, eliminating the automatic, autopilot mistakes that occur when people execute procedures without engaging their brains. The mechanism operates at the interface between humans and the systems they operate -- valves, switches, forms, keystrokes, or authorization signatures. Critically, deliberate action is not performed for the benefit of observers or inspectors; it exists to protect the operator from their own automatic errors. It has two additional benefits beyond individual error prevention: it allows adjacent team members to catch and correct mistakes before they happen, and it enables drill monitors and supervisors to intervene in real-time rather than merely recording errors after the fact.
- Deliberate action exists to protect the operator from automatic mistakes, not for show
- The more important it is to act correctly, the more important it is to act deliberately
- Mistakes are not inevitable -- they can be systematically reduced through conscious action
- In team settings, the pause allows adjacent operators to catch errors before execution
- Speed of execution is not prowess -- accuracy of execution is prowess
- Deliberate action applies to administrative acts like signing forms and authorizing actions, not just physical operations
- Identify the human-system interface pointsMap where in your operations humans interact with machines, systems, forms, or authorization processes. These are the points where automatic errors occur -- turning wrong valves, clicking wrong buttons, signing without reading, or entering incorrect data.Pro tipIn service and knowledge-work organizations, the key interfaces are the moments of signing forms, authorizing actions, and entering keystrokes.
- Implement the pause-vocalize-gesture sequenceBefore any action at an identified interface point, the operator pauses, states aloud what they are about to do, physically gestures toward the control or document, takes a deliberate pause, and only then executes. This sequence must be practiced until it becomes the new automatic behavior.Pro tipThe vocalization should name the specific action and target: 'Shifting number one reactor coolant pump to fast' while pointing at the correct switch, with a pause before pulling it.WarningOperators will initially perceive deliberate action as a training exercise to be abandoned in real situations. Use the thought experiment: if errors matter more in real situations, then deliberate action matters more too.
- Overcome the two perception problemsAddress the belief that deliberate action is for inspectors rather than for self-protection, and the belief that it is a training practice to be abandoned under pressure. Continually reinforce that the mechanism exists to protect the individual operator from their own automatic mistakes.Pro tipShare concrete examples where deliberate action caught an error that would otherwise have propagated. The Santa Fe inspection story is powerful: the crew tried to make the same number of mistakes as everyone else, but the mistakes never happened because of deliberate action.WarningIf even one leader treats deliberate action as performance theater rather than genuine safety practice, the entire mechanism loses credibility.
- Extend to administrative and decision-making processesApply deliberate action beyond physical operations to the act of signing authorizations, approving documents, and entering data. The robo-signing of bank foreclosures is a cautionary example of what happens without deliberateness in administrative processes.Pro tipWhen large stacks of administrative paperwork are just signed off on without thought, errors will eventually accumulate. Each signature should be a deliberate act.
During the highest-stakes reactor inspection, the senior inspector told Marquet that his crew tried to make the same number of mistakes as every other crew. The difference was that the mistakes never actually happened because of deliberate action -- they were either self-corrected by the operator during the pause or caught by a teammate.
A well-intentioned petty officer, working hard during a compressed schedule, moved aside red safety tags and shut a breaker on autopilot. He knew the tags were there but just moved them aside without engaging his brain. During the eight-hour critique, the crew rejected adding more supervision or training and instead invented deliberate action.
A petty officer on Santa Fe violated a red tag by moving it aside and shutting a breaker without thinking. During the eight-hour critique, every standard solution was proposed and rejected: refresher training, additional supervision, more attention to detail. When someone blurted out 'Captain, mistakes just happen!' Marquet pressed further. They realized the operator had been on autopilot -- executing a procedure without engaging his brain. The crew developed deliberate action as their mechanism: pause, vocalize, gesture, then act. Rather than punishing the petty officer through captain's mast, Marquet implemented the alternative. The nuclear-trained personnel recognized it as an extension of 'point and shoot' from nuclear power school, but it was a harder sell for the rest of the crew.