As the year comes to a close, it’s a good moment to notice what we finish — and how we finish it.
Concept of the week - Designing for Completion
Calm systems help people finish before they move forward.
In complex, high-stakes environments, explicit closure is required. Surgical teams in operating rooms worldwide run a checklist together before the first incision, not because they lack expertise, but to ensure alignment and shared closure. Aviation follows the same principle: pilots use checklists not to fly the plane, but to ensure nothing essential is left implicit when transitioning between phases of flight.
The origin of this practice is revealing. The modern checklist emerged in 1935 during the introduction of a new, highly complex aircraft. After a fatal crash, investigators found no technical failure. The cause was simple: a pilot had missed a newly added step in an unfamiliar control system. The aircraft itself was sound—the challenge was managing growing complexity with human memory alone.
Rather than demanding more training or perfection, the response was remarkably modest. A group of test pilots created a small, index-card-sized checklist covering key phases of operation—takeoff, flight, landing, and taxiing. With this simple external memory aid, the same aircraft was subsequently flown over long distances without further accidents. Complexity had not been reduced—but it had been made manageable.
The same failure pattern appears far from cockpits and operating rooms—in product teams, handovers, reviews, and releases where small omissions quietly compound.
This is the deeper lesson of calm design. Checklists are not about rigid compliance or control. They are interfaces for completion. They move critical steps out of individual memory and into shared, visible practice. When closure is designed explicitly, systems become safer, calmer, and easier to live with.
Today, the next evolution is already underway. Digital systems, automation, and AI can move checklists from static lists to adaptive support. Instead of asking people to remember when to check, systems can sense context, detect transitions, and quietly prepare the right prompts at the right moment.
Completion becomes anticipatory rather than manual.
Asset
Book — The Checklist Manifesto by Atul Gawande
Gawande shows how checklists support professionals in complex, high-stakes environments by making the invisible visible. Read this to apply high-stakes rigor to design, sprints, and retrospectives.
Use these five questions to create and review your own checklist:
Is this checklist short enough to actually use right now (5–9 items)?
Can I complete it quickly without breaking my workflow?
Which steps here are critical if missed—even if they feel obvious or routine?
Have these questions been tested in real work, not just imagined?
At which exact moment should we pause and run this checklist together?
Light wisdom & reflection
“The checklist gets the dumb stuff out of the way so the smart stuff can shine.”
What we often label as “dumb” is usually not trivial—it is critical. These are the steps that feel obvious, repetitive, or beneath expertise, yet cause the most harm when missed. Checklists exist precisely because these tasks matter too much to rely on memory, attention, or good intentions.
Where in your work do small, unglamorous steps carry outsized risk if forgotten? Which critical tasks deserve to be quietly protected by a checklist, so your team’s attention can focus on judgment, care, and insight rather than recall? The question is not whether something could go wrong—but what it would cost if it does.
Mindful practice
Before you finish work today, take two minutes to design a checklist for one recurring task in which missing a step would be costly.
Inspired by The Checklist Manifesto, choose a moment that looks routine but carries real risk if steps are forgotten—such as preparing a sprint review, presenting to stakeholders, designing a component, or handing work over for implementation.
Write a short checklist (5–7 items):
Focus only on the critical steps most likely to be missed
Anchor it to a clear pause point (before sending, before presenting, before handing over)
Keep it simple enough that you would actually use it next time
Don’t aim for completeness. Aim for reliability. This small act turns experience into shared memory—and closes loops before they become problems. If you want to take it one step further, identify two external data points (context) that a digital system could sense to automatically prompt this checklist at the exact right moment.
Best,
Andreas Walden
Share this with someone designing for clarity.