Script the Critical Moves

Script the Critical Moves is a change method for translating a broad direction into a small number of observable actions. It reduces ambiguity at the moments where people otherwise hesitate, interpret the goal differently or default to the old behaviour.

When to use it

• Turn an aspiration into behaviour people can perform now.

• Reduce avoidable choice overload in a recurring situation.

• Make a new practice easier to teach, observe and reinforce.

• Create a temporary default while people build skill and confidence.

• Avoid scripting work whose safety or quality requires expert judgement in changing conditions.

Origins

Chip and Dan Heath present “Script the Critical Moves” in Switch as part of directing the rational side of change. The method draws on decision research, implementation intentions, checklists and operational standard work: clarity about the next behaviour can free people from re-deciding the same issue repeatedly.

What it is

A critical move is a specific action in a defined situation. It is not a value, personality trait or desired outcome. “Deliver excellent service” is an aspiration; “acknowledge every unresolved request before handoff and name the next owner” is a behaviour that can be taught and observed.

A script can be a rule, checklist, default, sequence or if–then response. Good scripts define the smallest set of moves that carries disproportionate value. They leave judgement available outside that boundary and include an escalation path for exceptions.

How to use it

Define the target outcome and the behaviour gap. Observe the work and interview people at the point of hesitation; do not design the script only from policy.

Identify the recurring situations where interpretation creates delay, inconsistency or error. Ask which action, performed reliably, would make the largest near-term difference. Write it with an actor, trigger, verb and completion condition.

Test whether two people can independently tell whether the move occurred. Keep the list short, use the language of the work and remove steps that do not change the outcome. Make dependencies and exceptions explicit.

Pilot the script with representative users. Measure performance, workload, error and unintended effects. Revise it when the environment or evidence changes, and retire it when capability has become reliable or the script no longer adds value.

In safety-critical or regulated work, integrate the script with professional standards, stop-work authority and escalation. A checklist supports expertise; it does not replace it.

Top practical tip

Watch the task in context and mark the exact hesitation, handoff or exception point. That moment usually reveals the move worth scripting and the information the script must supply.

Top pitfall

Do not script every action or optimise only for compliance. Over-scripting suppresses judgement, creates workarounds and burdens attention; protect discretion where conditions genuinely vary.

Further reading

• Heath, C. and Heath, D. (twenty ten). Switch: How to Change Things When Change Is Hard. Broadway Books.
• Gollwitzer, P.M. (nineteen ninety-nine). “Implementation Intentions: Strong Effects of Simple Plans.” American Psychologist.