Review

This book makes a compelling case for the adoption of checklists, presenting logical arguments through well-crafted stories and anecdotes. I recommend reading the book, as this summary will not attempt to replicate its storytelling.

One drawback, is that any practical advice about how to adopt checklists or make them is distributed throughout. I’d have loved to see the author distil everything into a concise 'how-to' guide at the end.

You Might Also Like:

Nudge

What is it about? Was it worth reading?

andrewclark.co.uk

Thinking in Systems

This book has the most captivating opening chapter I've ever read. In just 25 pages, the author skilfully explains the fundamental concepts of systems thinking using simple language and numerous examples. Moreover, she successfully ignites your enthusiasm for perceiving the world from a fresh perspective. The most talented people I work with are all intuitive systems thinkers. They have the ability to see the big picture and identify high leverage intervention points, which makes them disproportionately effective. If that doesn’t sound like you, then it might be worth reading this book!

andrewclark.co.uk

Thinking in Bets

Thinking in Bets provides a valuable introduction to decision theory and the associated psychological principles. As Product Managers, we often don't see the immediate impact of our decisions. It's crucial to integrate long-term strategic goals into our real-time decision-making processes to enhance the likelihood of positive outcomes. Although this book isn't about product development, it helped cement the importance of Product Discovery for me (validating our assumptions allows us to peek into the future, and increase the chances that we're successful).

andrewclark.co.uk

Key Takeaways

The 20% that gave me 80% of the value.

Why checklists are needed:

• The volume and complexity of knowledge has exceeded our individual ability to deliver its benefits correctly, safely, or reliably.
• Checklists provide protection against failures, reminding us of the minimum necessary steps and making them explicit.
• Checklists establish a higher baseline of performance by helping with memory recall and getting out the minimum necessary steps.

Key lessons for designing and implementing effective checklists:

• Keep checklists simple, focusing on the most critical tasks that are often overlooked.
• Ensure the effects of the checklist are measurable and aim for widely transmissible benefits.
• Include brief team huddles to foster communication, participation, and shared responsibility.
• Use clear, unambiguous language and keep the checklist concise to avoid distractions.
• Define clear pause points for when the checklist should be used and choose an appropriate format based on the situation.
• Test and refine checklists in real-world or simulated scenarios until they work consistently.
• Recognize that checklists support expert skills rather than replace them, allowing for flexibility and judgment.
• Anticipate initial resistance but expect faster, more thorough processes and improved teamwork overall.
• Continuously revisit and refine checklists to ensure they remain helpful and relevant over time.
• Embrace the power and simplicity of checklists as a tool for managing complexity and fallibility while fostering a culture of teamwork and discipline.

Deep Summary

Longer form notes, typically condensed, reworded and de-duplicated.

Introduction

• Gorovitz and MacIntyre (1970s) identified three ways in which we fail:
• Necessary fallibility: when we take on something impossible.
• Ignorance: when current science only gives us a partial understanding of how to do it.
• Ineptitude: the knowledge exists but we fail to apply it.
• As science advances the balance of ignorance and ineptitude is shifting, in many fields the problem we’re now facing is ineptitude. Our failures remain frequent, and persist despite remarkable individual ability. We need to focus on eptitude → making sure we apply the knowledge we have consistently and correctly.

The reason for ineptitude is increasingly evident: the volume and complexity of what we know has exceeded our individual ability to deliver its benefits correctly, safely, or reliably. Knowledge has both saved us and burdened us.

• Despite appearing too simple, the checklist can help.

Chapter 1: The Problem of Extreme Complexity

Medicine has become the art of managing extreme complexity—and a test of whether such complexity can, in fact, be humanly mastered.

• In an attempt to manage complexity Medicine has split into various specialties, but despite a growing number the work can become overwhelming.
• Most doctors (and other professionals) are tempted to believe that no one else’s job could be as complex as theirs. But extreme complexity is common.
• It’s not just growing knowledge that’s making medicine complicated, complexity in execution is growing too.
• The average patient in an ICU requires 178 individual actions each day, nurses and doctors performed them with a 1% error rate. That’s two errors a day per patient.
• The medical profession has gone from specialisation to super-specialisation. Expertise is the mantra of modern medicine. Despite that, mistakes are still made.

Chapter 2. The Checklist

• Test pilots of the Boeing B17 found it too complicated to fly. Checklists for takeoff, flight, landing and taxiing helped. They were simple, brief and short enough to fit on an index card.
• We all believe that OUR jobs are too complicated to be reduced to a checklist.
• With ‘all-or-none processes’ if you miss one thing, you might as well not have made the effort at all. Faulty memory and distraction become more dangerous.
• In complex processes certain steps don’t always matter. A check can be pointless most of the time, until the day when it really matters.

Checklists provide some protection against such failures. They remind us of the minimum necessary steps and make them explicit. They not only offer the possibility of verification but also instil a kind of discipline of higher performance.

• Some of the results from adopting checklists in medicine were so dramatically positive they weren’t sure whether to believe them.
• Checklists establish a higher baseline of performance by helping with memory recall and getting out the the minimum necessary steps.
• Doctors and nurses on rounds move from patient to patient with constant interruptions. Perfect ground for the checklist.

Chapter 3. The End Of The Master Builder

• Problems can be categorised into three types:
1. Simple: Like baking a cake from a mix, following a recipe leads to likely success.
2. Complicated: Like sending a rocket to the moon, these problems require multiple teams, specialised expertise, and handling unanticipated difficulties. Timing and coordination are crucial.
3. Complex: Like raising a child, each situation is unique and requires a different approach. Expertise is valuable but not sufficient, and outcomes remain highly uncertain, though success is possible.
• We are besieged by simple problems.
• Big construction projects look much like medicine there are specialists and super-specialists. They are complex to build and coordinate, but go up quickly and have a low failure rate.
• Big construction projects use a couple of forms of checklists:
• The construction schedule: makes sure simple steps are not missed or skipped. It’s drawn up by a cross-disciplinary group of sixteen trades, and sent to subcontractors for double-checking.
• Submittal schedule: makes sure that everyone talks through and resolves all the hard and unexpected problems. A checklist not for construction tasks but communication tasks. Project managers deal with the unexpected by making sure the right experts spoke to one another: who had to talk to whom, by which date, and about what aspect of construction or who had to share particular kinds of information before the next steps could proceed.
• In the face of the unknown, the builders trusted in the power of communication and the wisdom of the group.
• The biggest cause of serious error in this business is a failure of communication.

Chapter 4. The Idea

• When you’re confronted with complex, non-routine problems and risk you should decentralise authority and decision making.
• Push the power of decision making to the periphery and away from the center. Give people the room to adapt, based on their experience and expertise. All you ask is that they talk to one another and take responsibility. That is what works.
• You don’t want to end up in a situation where everyone is waiting for the cavalry. Instead set goals, measure progress and maintain communication.
• To handle a complex situation (were conditions are unpredictable) don’t issue instructions, instead just make sure people talk.
• People need room to act and adapt. Yet they cannot succeed as isolated individuals, either. They require a seemingly contradictory mix of freedom and expectation. Expectation to coordinate and measure progress toward common goals.
• Effective checklists should:
• Ensure critical tasks aren't overlooked
• Facilitate communication
• Assign responsibility
• Leave room for judgement
• Van Halen's Clause 126, known as the "no-brown-M&M's" rule, served as a confirmation that their checklists were being adhered to.
• In restaurants checklists are abundant too (recipes and orders). As orders come through cooks read them back to confirm they heard it right. There’s a standup to discuss challenges for the evening. The check reviews every plate, sending 5% back.

Chapter 5: The First Try

• Keep checklists simple, focusing on critical tasks that are often overlooked.
• Ensure the effects of the checklist are measurable.
• Aim for widely transmissible benefits (high ROI or leverage).
• Include brief team huddles to foster communication, participation, and shared responsibility. Have team members introduce themselves by name and role to activate engagement.
• Use clear, unambiguous language in the checklist items.
• Keep the checklist concise to avoid distractions and maintain focus on the task at hand.
• Make sure the checklist format (e.g., verbal vs. written) is explicitly stated and followed.
• Iterate and refine the checklist based on real-world use and feedback.

6. The Checklist Factory

• Create separate checklists for different scenarios, each one brief and easy to read.
• Be precise, efficient, and practical, focusing on the most critical steps.
• Provide reminders without spelling out every step, allowing users to maintain thinking and judgment.
• Define clear pause points for when the checklist should be used.
• Choose between a "DO-CONFIRM" (complete tasks first, then check) or "READ-DO" (check off tasks as completed) format based on the situation.
• Limit the number of items to between five and nine, or the limit of working memory, when possible.
• Use simple, exact wording and familiar language of the profession.
• Design for clarity, fitting the checklist on one page with minimal clutter and easy-to-read fonts.
• Test and refine checklists in real-world or simulated scenarios, making changes until they work consistently.
• Recognize that checklists support expert skills rather than replace them, remaining concise and usable.
• Translate necessary knowledge into simple, usable, and systematic forms to aid adoption.

7. The Test

• Improve usability through clarity, speed, and a DO-CONFIRM format that allows flexibility while ensuring critical steps are not overlooked.
• Test and refine the checklist in simulated scenarios, tweaking each line and timing the process to ensure swift use.
• Balance brevity and effectiveness by focusing on the most critical items and dropping non-essential ones.
• Consider varying perspectives on what is critical when deciding which items to include.
• You can incorporate checks for rare but serious errors, certainly if quick to do.
• Expect a learning curve when introducing a checklist, as it may feel strange or socially difficult at first.
• Anticipate improved teamwork and better responses to challenges as a result of using the checklist.
• Evaluate the impact of the checklist through measurable outcomes and staff feedback.
• Share success stories and results to encourage wider adoption and support.
• Recognise that even with some resistance or skepticism, the majority of staff may appreciate the value of the checklist for their own care.

Chapter 8: The Hero in the Age of Checklists

• Use checklists as a starting point to embrace a culture of teamwork and discipline, not just to tick boxes.
• Recognize that checklists do not replace the need for skill, judgment, and improvisation, but rather support them.
• Create checklists to guard against known mistakes and errors at each step of a process.
• Use checklists to ensure critical information is available when needed and that decisions are made systematically.
• Expect initial resistance and slower up-front work when introducing checklists, but faster and more thorough processes overall.
• Design checklists to handle routine tasks, freeing up focus for more complex and critical aspects of the job.
• Incorporate discipline and adherence to protocol as a key element of professionalism, alongside selflessness, skill, and trustworthiness.
• Continuously revisit and refine checklists to ensure they remain helpful and relevant over time.
• Pay attention to how components of a system fit together, not just the quality of individual components.
• Embrace the power and simplicity of checklists as a tool for managing complexity and fallibility.

Chapter 9: The Save

• Checklists consistently catch potential issues, even in routine operations, due to patient variability.
• Checklists promote teamwork and attentiveness, helping teams stay focused and coordinated during critical moments.
• When faced with complications, teams using checklists are better prepared to respond calmly and effectively.
• Checklists serve as a reminder of past mistakes, encouraging continuous learning and improvement.