First, the structure varies from the design of aviation checklists, in that it combines procedures with formal team discussion; these processes are not mixed in the cockpit but remain distinct because they serve different purposes. The WHO checklist consists of a checklist (Sign In), a briefing (Time Out) and a checklist with a short briefing at the end (Sign Out). Checklists are suited to verification of procedures for linear processes; whereas briefings are suited to support execution of complex processes that may require appropriate adaptation and variation. Briefings are important because surgical outcomes are complex and emergent, and optimal performance of surgical procedures may require flexibility to accommodate the unexpected, however briefings should be instituted separately from the checklist. If briefings are too closely coupled to checklist completion, teams may miss the cognitive shift required to move from linear or procedural work to complex or adaptive work.
2. Checklists free up mental RAM. People often bristle at using a checklist because it feels constraining. They want to be flexible and creative, and the checklist seems to take away their autonomy. For this reason, implementing checklists among surgeons has proven difficult, even though studies show checklists dramatically reduce the number of preventable, life-threatening errors. Surgeons feel that their work requires an intuitive judgment that’s born from years of training and experience and can’t be reduced to a simple checklist.
Let’s take a simple example. When you get in a car, you can’t just drive because there is a set of specific operations to be done. These include fastening your seat belt, removing the handbrake, putting a transmission gear lever into neutral position, starting the engine, checking the indicators, etc. After you have checked and accomplished all these routine tasks, you can press the accelerator pedal and drive. Every driver has this checklist in his/her memory because of its regular use. If your set of tasks is bigger or varies frequently, it’s challenging to keep it memorized all the time.
3. Checklists instill discipline. Checklists continue to play a vital role in aviation. Every time pilots and co-pilots take off and land, they verbally go through a checklist. A lot of what they review is of course the stupid simple stuff, but it’s important stupid simple stuff. When you’re responsible for the lives of 120 passengers, you have to have the discipline to make sure you do even the small things right. If there’s ever an incident in air, investigators will go back to see if the pilot and co-pilot went through the checklist. There’s no fudging with it. You either did it or you didn’t.
And the tragic thing is it’s often the “stupid” simple stuff that gets people killed or keeps them in the hospital for longer than they needed to be. I have an acquaintance who ended up in the hospital for two weeks because he got the wrong heart medicine. The problem was ultimately one of miscommunication — a basic thing you think would be a given, seeing as how hospitals can transplant human faces and whatnot.
Aviation checklists are designed for modern aircraft that are complicated, not complex; it is usually possible to define a single process path that offers optimum performance for each flight condition. These process paths are flight tested, endorsed (with minor modifications) by airlines when they purchase a new aircraft type, and published in procedural manuals and checklists. There are two categories of checklist used in the cockpit: normal and non-normal (or emergency) procedures.
Published by the BMJ Publishing Group Limited. For permission to use (where not already granted under a licence) please go to http://group.bmj.com/group/rights-licensing/permissions This is an Open Access article distributed in accordance with the Creative Commons Attribution Non Commercial (CC BY-NC 4.0) license, which permits others to distribute, remix, adapt, build upon this work non-commercially, and license their derivative works on different terms, provided the original work is properly cited and the use is non-commercial. See: http://creativecommons.org/licenses/by-nc/4.0/
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.
If you do not want to exhaust your team members’ creativity, checklists are a must-have tool for production. Their function is simple - to check whether anything is forgotten or unfinished. And the most important thing is that you do not have to create a new checklist every time a task appears. Creative energy can be channeled to the more exacting tasks.