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.
We may not like to admit it, but many of us can describe a time when we’ve made a mistake during the progress of a study. These mistakes can range from mixing up wires or forgetting to turn on an amplifier to forgetting to collect an essential piece of information that either requires additional processing time or prevents you from analyzing a certain variable altogether. Increased computing power and technological advancements have also made it easier than ever to collect data.
Everything seemed fine, until the patient stopped responding and his heart rate skyrocketed. The patient's blood pressure was barely detectable. Nothing his medical team did improved it, so he was rushed to surgery. Only when he was opened up did the doctor finally realize the stab wound went much further inside the patient than he'd thought, cutting right into the aorta—the main artery from the heart. Although it seemed like a small knife wound, the patient had actually been struck by a bayonet—part of the assailant's costume.
Every construction job begins with a massive checklist of tasks that have to get done and each task has an accompanying deadline. While that to-do list plays an important role in ensuring stuff gets done, an equally valuable checklist is also used. Called a “submittal schedule,” it centers on communication. The submittal schedule details which project managers need to talk to which project managers during a specific phase and about a specific process. The submittal schedule’s purpose is to get teams that are working on different yet co-dependent projects to regularly connect so they can discuss any potential sticking points. For example, there might be an item on the checklist for carpenters and plumbers to meet up at a specific time to discuss their progress on their respective tasks. Maybe a problem has come up with the pipes that affects when the carpenters can get started on their work, but perhaps there’s something the carpenters can do to help the plumbers. The trick is to keep each other in the loop so each respective team can take care of these “known unknowns” as quickly and as effectively as they can. Once the teams talk, they check the communication task as complete, and move on with their work.