Checklists for Change

Checklists for Change are concise prompts that make a new behaviour easier to repeat and reduce omission of mission-critical steps. They shape the environment at the moment of action, supporting memory without asking people to hold an entire procedure in working memory.

When to use it

• Improve reliability in recurring or high-consequence work.
• Make essential practice easy to recall under pressure or distraction.
• Support a new habit without overloading the analytical “Rider.”
• Reveal omissions and coordination gaps in complex routines.
• Use it after the correct process is understood; a checklist cannot repair a fundamentally poor design.

Origins

The method comes from operational reliability rather than one management theorist. Aviation made checklists central during the twentieth century as aircraft became too complex for memory alone. Medicine adopted the same principle for high-risk routines; the World Health Organization launched its Surgical Safety Checklist in two thousand and eight after international and multidisciplinary development, with checks placed at three critical points in an operation. Atul Gawande’s The Checklist Manifesto (two thousand and nine) helped bring the idea to a broad management audience. In the context of behaviour change, the checklist is an environmental cue that turns an intended practice into a repeatable sequence.

What it is

A checklist is not a condensed manual and does not explain every action. It captures the few items that are easy to miss but necessary for a safe or effective result. A read–do list guides each step as work proceeds; a do–confirm list pauses at a defined point so a person or team can verify that essential actions are complete.

The checklist can educate a novice about what matters, coordinate specialists and provide a stable cue for a developing habit. It should preserve judgement: unusual conditions still require people to stop, diagnose and adapt.

How to use it

Define the target behaviour and the consequence of omission. Observe the real workflow and identify “killer items”: steps that are essential, vulnerable to being forgotten and not reliably caught elsewhere. Do not include every desirable action.

Choose whether the list is read–do or do–confirm and place a deliberate pause point where it fits the work. Write short, concrete actions in the language users employ. Specify who initiates the checklist, who confirms completion and what happens when an item fails.

Prototype the list in the actual environment. Watch real users under realistic time pressure, record ambiguity and remove decorative, obvious or overly broad items. Train people on both the checklist and its purpose, then monitor use, outcomes and workarounds. Update it when the process or risk changes; retire items that no longer protect a critical step.

Top practical tip

Design around the pause point. A one-page prompt used reliably at the right moment creates more value than a comprehensive manual that remains unopened.

Top pitfall

Do not let the list become a compliance artefact. Excess length, automatic tick-box completion or punishment for raising a failed item destroys the attention and communication it was meant to create.

Further reading

• Heath, C. and Heath, D. (twenty ten). Switch: How to Change Things When Change Is Hard. Broadway Books.
• Gawande, A. (two thousand and nine). The Checklist Manifesto. Metropolitan Books.