Power of Lists

A checklist turns critical but forgettable steps into a shared external routine. Its power comes from making omissions visible before they become consequential errors.

A 19-item surgical checklist—containing basics such as confirming the patient’s identity and counting sponges afterward—was associated with a 40% reduction in deaths and a 50% reduction in infections.

R1

Move memory outside the mind

High-stakes failures do not always come from ignorance. People may know every required step and still omit one amid pressure, handoffs, and divided attention. A checklist converts that vulnerable sequence into an external record: the necessary actions become visible, ordered, and confirmable. It also coordinates the group. Asking whether everyone knows the patient’s allergies or whether blood is available turns privately held information into shared operational knowledge.

R1

Where it shows up

Before the first incision

Confirming the patient, procedure, and location catches catastrophic mismatches while they are still cheap to correct.

R1

Making hidden knowledge shared

Explicitly checking allergies and blood availability exposes information or resources that someone may know about but the whole surgical team may not.

R1

Accounting before closure

Counting needles, sponges, and instruments after surgery makes a dangerous omission detectable instead of relying on someone to notice that an item is missing.

R1

A list cannot supply judgment

The reported gains come from a checklist designed around concrete surgical failure points. That does not show that every task improves when converted into a list, or that mechanically ticking boxes can replace expertise. The list helps when known, consequential steps are easy to omit; it is weaker when the real problem is deciding what ought to be done.

R1

Write the omissions, not the whole job

Choose one repeated task in which a missed step causes real trouble. Write a short checklist containing only the items most likely to be forgotten—especially identity, dependencies, shared information, required resources, and final accounting—and require an explicit confirmation for each.

R1

Episodes that teach this