I started to brain storm other areas that checklists could be beneficial. In the construction industry, Gawande explains that checklists are used so that key points are discussed between those in different aspects of the building process. For research, are there things that you always need to talk about with other experimenters or your supervisor when it comes to a study? Maybe a checklist can help there too. Also, when editing manuscripts or proofs, you could have a structured set of points to assess such as, “check to make sure data in tables/figures is correct” or “make sure reference list is up to date”. These all seem so basic, but if taking the time to go over them and know that once you’ve handed in the manuscript that these things have definitely been checked, it could prevent you from having to submit an erratum due to something like an improper figure.
When ideas are translated from one industry to another, the assumptions underlying the original concepts may be lost or diluted. As checklists are increasingly imposed through a variety of professional and regulatory mandates in North America,5 Europe6 and elsewhere,7 perhaps it is time to review the fundamental principles of checklist use, including why they might work and how we can implement them better.

This week I made my first checklist for setting up one of my thesis data collections. I listed specific essential tasks and supplemented them with common errors I had either made or had encountered in the past. After making this specific checklist, I decided to see if I could make a general list that could be applied to all studies. Surprisingly, it was easier to do than I thought, although I’m sure it isn’t perfect. I was able to group many of my tasks together under one common point. What is not easy so far is trusting and not deviating from the checklist. It’s been easy to throw the checklist to the side when I get frustrated. In more stressful situations or even when things are running smoothly, I may forget that I’ve come up with a structured way to make sure I’m managing my data collection in the best way possible.


Perhaps, we have a complete picture of leveraging checklists in such industries as aviation or manufacturing. However, how has this tool proved itself in a more complex workflow - software development? In fact, software teams that follow Agile methodology appreciate the implementation of lists as acceptance criteria solutions, definition of done, progress tracking tools, etc. Moreover, each separate development process has its own advantages.
Gawande in 2009 introduced a hospital surgery checklist for doctors and nurses as part of a program developed with the World Health Organization. The checklist was designed to ensure basic checks were always completed before surgery. Run through the list, and you'll make sure everyone in on the same page about the surgery to be conducted, aware of who else was on the surgical team, and knows their role in the procedure.
Checkbox Form Object - Use the checkbox form field only if you are wanting to add interactivity to your checklist. The checkbox form field, found in the Forms toolbar, can link to a cell in the spreadsheet without requiring any Visual Basic programming. The linked cell will be a boolean value TRUE or FALSE. Like the drawing objects, working with a large number of checkboxes can get messy.

It is obvious that one can use a screwdriver as a hammer, but that won’t be efficient. It’s similar with leveraging Git. To make the most of it, you need a recipe to achieve the highest productivity. It is all possible with Git workflows. Besides, a consistent Git workflow ensures more chances to free your development pipeline of unnecessary obstacles. In that case, a checklist is a solution to avoid committing to memory every component of your software development cycle. The tool is able to guide anyone through the workflow jungles including user stories issues, solution coding, forking the code repository, and others.
It is obvious that one can use a screwdriver as a hammer, but that won’t be efficient. It’s similar with leveraging Git. To make the most of it, you need a recipe to achieve the highest productivity. It is all possible with Git workflows. Besides, a consistent Git workflow ensures more chances to free your development pipeline of unnecessary obstacles. In that case, a checklist is a solution to avoid committing to memory every component of your software development cycle. The tool is able to guide anyone through the workflow jungles including user stories issues, solution coding, forking the code repository, and others.
Our checklists and checklist templates are licensed for personal use only. However, to avoid a bunch of emails, I will also say that I am okay with you doing almost anything with these checklists except posting the checklist (or anything you have created using the checklist template) on the internet or selling it. That includes permission to print and distribute as many paper copies of your checklist as you need. Don't remove the copyright or hyperlinks that I've included in the spreadsheet, though.

Though Gawande admits he didn't expect to see the checklist make much difference in his own surgeries, he followed it to avoid hypocrisy and was surprised by the results. The checklist saved a life in at least one case, where a mistake by Gawande led to a critical need for blood while the mistake was corrected. Thanks to the checklist, extra blood had been prepared ahead of time, despite Gawande's confidence in performing a surgery he'd done successfully many times before.
Our checklists and checklist templates are licensed for personal use only. However, to avoid a bunch of emails, I will also say that I am okay with you doing almost anything with these checklists except posting the checklist (or anything you have created using the checklist template) on the internet or selling it. That includes permission to print and distribute as many paper copies of your checklist as you need. Don't remove the copyright or hyperlinks that I've included in the spreadsheet, though.
Boldface items are for immediate action, when the aircraft may be lost if the items are not completed quickly and in the correct order. Correct and rapid execution of these steps is so critical and essential, that pilots must complete them from memory. Through training and repetition, the paired cognitive and motor activities required to perform the checklist are stored by the pilot as procedural memory (or ‘motor skills’).10 Despite notable exceptions (such as ‘choking’ under pressure), procedural memory retrieval is less affected by stress than declarative or episodic memory retrieval.11 For this reason, aircrew practice time critical emergency procedures regularly to aid in forming the correct ‘habits’. However, as soon as time permits, the checklist is used to confirm that the steps were executed as required.8
Checklists seem simple, Gawande says, and are sometimes hard for us to accept as a necessity when we're in high-powered jobs that rely on our skills and knowledge. But humbling ourselves by using a checklist can improve our performance and help us achieve more consistent results. "They remind us of the minimum necessary steps and make them explicit," writes Gawande. "They not only offer the possibility of verification but also instill a kind of discipline of higher performance."
Checklists don't have to be boring. Pocket Lists is a fun, personal checklist iOS that lets you organize your checklists with icons. Organize the things you need to do, then add an icon to each checklist to make it easy to identify. It can manage your daily tasks, with due dates and notifications, and can also keep track of your more detailed checklists to help with your work routines.
1. Checklists verify that the necessary minimum gets done. With increasing complexity comes the temptation to skip over the stupid simple stuff and instead focus on the “sexy” parts of one’s work and life. Because the stupid simple stuff is so stupid and simple, we often fool ourselves that it’s not important in the grand scheme of things. But as we’ve seen, it’s often our most basic tasks that can spell the difference between success and disaster.
Pre-flight checklists are a good example. A regular pilot is aware of the importance of checking a list of tasks to prepare an airplane for takeoff. These include checking the operation of the altimeter, fuel gauges, flight controls, magnetos, engine idle, and other system parameters. Besides, preflight checklists are usually segmented in a way that the accomplishment of final items (status of doors/windows, mixture, lights, camera, and action) is completed after the set of initial tasks. The same thing is with the before-landing checklist. According to the FAA's practical test standards, these sets of tasks must be in a written form for pilots’ use.

Checklist compliance is increasingly monitored in healthcare.5 Often, institutions conduct internal audits of checklist compliance in anticipation of regulatory inspections. Using ‘compliance with checklist’ audits as a measure of safety or quality, however, is problematic, as high checklist compliance is no guarantee that the task is well-executed,18 or that patient safety culture is high.20 In addition, some of the benefits that have been found to be associated with checklist usage, such as enhanced team building and nurses speaking up, are likely to be negated if compliance audits lead to sanctions.
Checklists make it easy to delegate tasks if someone offers to help you. If you are lucky enough to have assistance, you can refer to your list and know what to ask them to do right away. You can even share your list with them and let them pick what appeals to them. The disadvantage to delegating in this way is losing control when other people choose what they want to do. If you are concerned about giving away easy tasks and getting stuck with the challenges, keep your list to yourself.

Agile software development leverages a technique called the user story to get enough information for implementing software features from an end-user perspective. Shaping acceptance criteria is an integral part of this process that can be improved with a checklist's help. You can create a special format containing categories, point assessments, labels, names, etc. For example, a Definition of Ready can be transformed in Definition of Done category after changing the story specification. On the picture below, you can see an implementation plan, which is, in fact, a ToDo list containing guidance on how to handle the user story written in the description section.
Thanks for this great post. I was very skeptical about the idea for being an automaton by following a checklist or a schedule of all day, day or mounth. And then my life was a real impasse. I ignore what great things I did it and so for. Afte that I decided to get a plan of my live. I decided to savor my live by listing waht I did and what I want to do.

Mental checklists to improve thinking. Berkshire Hathaway vice-chairman Charlie Munger uses a mental checklist of biases and cognitive flaws that he reviews before making any big decision to ensure he’s thinking clearly about it. He’ll go down the list and ask himself if any of these biases are clouding his thinking and what he can do to mitigate it. Ever since I’ve learned about that, I’ve tried using something similar in my life. Crafting this list is still a work in progress for me, but here’s what I have so far:


Investigators discovered the crash wasn’t caused by a mechanical malfunction, but rather pilot error. The problem was while the new bomber could carry more and fly faster and further than any other bomber in history, it was also an extremely complex plane to operate. To fly it, a pilot had to pay attention to four different engines, retractable landing gear, wing flaps, electric trim tabs, and much, much more. Because the pilot was so preoccupied with all these different systems, he forgot to release a new locking mechanism on the elevator and rudder controls. Overlooking something so simple killed the two men at the helm.
The crux of this problem is while the world around us is becoming more and more complex, we’re still stuck with a brain that hasn’t changed much in 100,000 years. Sure, we’ve figured out ways to off-load memory storage to books and computers so we can know more; we just haven’t figured out a good way to overcome our evolved biases, cognitive flaws, and intrinsic forgetfulness. And so, despite owning a brain brimming with ever more knowledge, we continue to make stupid mistakes.
Daniel Bryant sat down with Dave Sudia, senior DevOps engineer at GoSpotCheck, to discuss the benefits of PaaS; building a platform with Kubernetes as the foundation; selecting open source components and open standards in order to facilitate the evolution of a platform; and why care should be taken to prioritize the developer experience and create self-service operation of the platform.
×