Pilots run a checklist before every flight. Not just the first time, not just the hard flights, not only when they are tired. Every flight. The captain on a Boeing 787 with twenty thousand hours of experience still reads the same items aloud as the first officer flips the same switches in the same order. The reason is not that pilots are forgetful. The reason is that complex performance under pressure leaks small mistakes that a checklist catches.
Deep work has the same shape. The task is cognitively demanding. Conditions vary. Energy varies. Memory and attention are unreliable, especially at the start of a session when you are trying to translate a vague intention into actual work. A checklist will not give you discipline you do not have, but it will stop you from launching with a tab already open to the news, a phone in arm's reach, and no clear definition of what "done" means in the next hour.
This post defines the FocusFlight pre-flight checklist. Five items, three minutes, run before every serious focus block. The items are deliberately boring. That is the point.
Why Pilots Use Checklists Even on Their Ten Thousandth Flight
The aviation checklist is one of the most studied safety interventions in any field. Atul Gawande's The Checklist Manifesto is the most accessible book-length treatment, and his account is straightforward: pilots adopted checklists in the 1930s after a Boeing prototype crashed during a demonstration flight because the crew forgot to release a control lock. The aircraft was technically sound. The crew was technically excellent. The crash happened anyway. The fix was not more training. It was a printed list of items to verify in order, every time, regardless of who was flying.
What checklists do is offload memory and judgment for predictable, high-cost mistakes. The pilot still needs skill, situational awareness, and judgment for the parts of flying that vary. The checklist handles the parts that do not vary. That separation is useful because human attention is finite. Spending it on what should be automated is a small disaster waiting for a busier day.
Cognitive load research backs this up. When a working memory is occupied by routine setup, less of it is available for the actual problem. A short, repeatable pre-flight ritual moves setup out of working memory and into a habit. By the time you sit down to do the hard work, your attention is fresh because it has not been spent on whether the right tab is open or whether your phone is reachable.
For deep work, this matters more than most people realize. The first ten minutes of a focus block are when the session usually fails. If the task is unclear, you will drift. If a notification arrives, you will respond. If you remember you forgot water, you will leave the desk and not fully come back. A checklist closes those small holes before takeoff.
The Five-Item Pre-Flight Checklist
FocusFlight's checklist is short on purpose. Long checklists are skipped. Five items can be run in three minutes and still cover the predictable failure modes of a deep work session.
- Close the tabs you are not using. Not minimize. Close. Open browser tabs are pre-loaded distractions. Each one is a single click away from a different topic, a different mood, and a different timeline. Leave open only the documents and references the session actually needs. If you are writing, you do not need email. If you are coding, you do not need the news.
- Bring water. A full glass, on the desk, before takeoff. This sounds trivial. It is not. Mid-session thirst becomes a reason to stand up. Standing up becomes a reason to check the kitchen. Checking the kitchen becomes a reason to look at the phone. The chain breaks the session more often than the original distraction would have. Water removes the first link.
- Define done. Write one sentence describing what will exist at the end of the block that does not exist now. "Outline the introduction" is better than "work on the report." "Solve problems 1 through 4 of the practice set" is better than "study chemistry." A defined finish line gives the session a direction and lets you know whether the work succeeded or just filled time. Our post on deep work timer rituals goes deeper on this.
- Phone elsewhere. Not face down. Not on do-not-disturb. In another room, or in a drawer, or in a bag across the desk. Research on attention drain has found that the mere presence of a smartphone reduces available cognitive capacity, even when the phone is not used. Adrian Ward and colleagues at the University of Texas published this finding in 2017 in the Journal of the Association for Consumer Research. The implication is direct: a phone in your sightline costs you focus you would otherwise have.
- One task. Pick the single thing this session is for. Not a list. Not a plan. One task. If you finish it early, you can start a new flight. But you do not switch mid-air. The whole point of the block is that one piece of work gets your full attention until the timer ends.
That is the entire list. No icebreaker, no breathing exercise, no journal prompt. Five items, in order, every time. The discipline is in the repetition, not in the elaboration.
The Boarding Ritual
Once the checklist is done, the session has a clean takeoff. Open FocusFlight, choose the flight length that matches the task, and press start. Headphones on. Sound bed playing. The transition from setup to work is now sensory: when the cabin sound begins, the focus block has begun. Over time this becomes a conditioned cue. Your attention learns that this sound means you are working, and the warm-up phase shrinks.
Aviation has the same logic. The "sterile cockpit rule" was issued by the FAA after several accidents traced to non-essential conversation during critical phases of flight. Below ten thousand feet, the crew may only discuss what the flight requires. The rule is not about silence; it is about attention discipline during the moments where attention matters most. The first ten minutes of a deep work session are your sterile cockpit. No Slack, no email, no quick check of anything. Below ten thousand feet, you fly the aircraft.
One practical rule that helps: if you remember something during the session that you would normally context-switch to handle, write it on a small capture pad next to your keyboard and keep working. The thought is not lost. It is parked. You will deal with it after landing. This is the same logic pilots use when something non-urgent appears during a high-attention phase: note it, address it later, do not lose the aircraft.
What Changes When You Skip the Checklist
The cost of skipping the checklist is not visible in any single session. It shows up as a pattern. You sit down to work, write three sentences, check a notification, lose ten minutes, return, realize you needed the other document, get up, come back with a coffee, and the first useful work happens at minute thirty. Multiply that by every focus block in a week and you have lost hours to a setup problem that could be solved in three minutes.
The pattern is sneaky because each individual leak feels small. Five minutes here, eight minutes there. None of it is dramatic. But Sophie Leroy's 2009 research on attention residue found that switching between tasks leaves a measurable cost: part of your attention stays attached to the previous task even after you have moved on. Her paper "Why Is It So Hard to Do My Work?" published in Organizational Behavior and Human Decision Processes showed that the residue is largest when the switch is unexpected. A checklist reduces the number of unexpected switches per hour. That is most of the gain.
For developers, this pattern is especially expensive because the work has long warm-up curves. Coding requires loading a model of the system into memory, and that model is fragile. One context switch and you are reloading. Two and you are exhausted. The checklist is cheap insurance against the more expensive habit of starting before you are ready.
When Not to Use the Checklist
A checklist is a tool, not a personality. There are sessions where running it is overkill. Five-minute tasks do not need a pre-flight. Replying to two emails does not need a defined-done sentence. Pulling up a document to verify one fact does not need a phone-elsewhere policy. If the task fits in the time it takes to set up the checklist, just do the task.
The checklist is for sessions of thirty minutes or longer where the work matters and the failure modes are predictable. That probably covers most of the work that pays your rent or earns your degree. It does not cover the small administrative tasks that fill the edges of the day. The deep work versus shallow work distinction is useful here: the checklist is a deep-work tool. Shallow work has its own rhythm, and forcing it through a pre-flight ritual just adds friction.
There is also a fatigue question. If you have been working at high intensity for several hours and you are attempting one more session, a checklist is unlikely to rescue you. Sometimes the right answer is to stop, recover, and run a clean checklist on the next session tomorrow. A pilot who is exhausted and behind the aircraft does not push harder. They reduce the workload. The same applies to deep work. The checklist is for sessions you genuinely have the resources to fly.
Frequently Asked Questions
How long should the pre-flight checklist take?
Three minutes for an experienced practitioner. Five at most. If your checklist takes longer than that, you are probably doing more than the five items, which usually means you are using setup as a way to delay starting. Keep it short. The point is to begin, not to optimize forever.
Do I really need to put the phone in another room?
Yes, and the research is clearer than most productivity advice. The 2017 University of Texas study showed measurable cognitive impairment from a phone simply being on the desk, even silenced and face down. Distance is the active ingredient. A drawer works. A bag on the other side of the room works. Face-down on the desk does not.
What if the task is too vague to define done?
Then the first session is not the work. It is the planning. Run the checklist with "produce a one-sentence definition of what done means for this project" as your defined task. That is a legitimate session. Trying to do work with no defined finish is how most focus blocks fail.
Does the checklist work for creative tasks?
Yes, but the "define done" item needs translation. For a writer, done can be "draft 500 messy words" rather than "produce good prose." For a designer, done can be "produce three rough sketches" rather than "find the right idea." Creative work does not benefit from output quotas being too high, but it does benefit from a finish line that lets you know the session is over.
What about checklist fatigue?
Checklist fatigue is real in aviation, and it is the reason cockpit checklists are kept short. The same applies here. Five items is enough. Adding a sixth and a seventh and a meditation prompt and a gratitude journal makes the ritual heavier than the work. If you find yourself skipping the checklist, shorten it before you abandon it. A simpler schedule that you actually run always beats an elaborate one that lives in your head.
The checklist is not the work. The work is the work. But the three minutes before the timer starts have an outsized effect on the next ninety. Run the same five items, in the same order, every time you mean to do something that matters. By the tenth flight you will not need to think about it. By the hundredth, you will have a focus practice that does not depend on motivation showing up first.