Most focus advice is about takeoff. How to start. How to get into the work. How to defeat resistance and begin. The descent gets very little attention, which is strange because in aviation the landing is where most accidents happen. Statistically, the riskiest phase of flight is not the takeoff and not the cruise. It is the approach and landing, the part where most of the energy has already been spent and the temptation is to relax.
Closing out a focus session is the same. The work is mostly done. The timer is running down. You are tired and a little proud and one Slack notification away from drifting into the rest of the day. Almost no one has a ritual for this part. Most sessions just sort of end. The timer beeps, you stand up, and the work goes back into the unsorted pile of things you might pick up tomorrow if you remember where you left off.
This post is about how to land well. Not because the landing is more important than the takeoff — they are roughly symmetric — but because no one teaches it and the cost of doing it badly compounds faster than the cost of a rough start.
Why Endings Matter as Much as Starts
Bluma Zeigarnik's research from the 1920s found that people remember unfinished tasks better than finished ones. Her experiments at the University of Berlin showed that interrupted work continues to occupy mental resources after the interruption ends. The mind keeps a small process running on tasks it does not consider closed. Modern attention research has reinforced and refined the finding: open loops cost cognitive bandwidth, and they cost it whether you are conscious of them or not.
This is why a focus session that ends with the timer simply running out is more expensive than it looks. You stop working, but the work does not stop running in the background of your mind. You half-remember that you were in the middle of something. You half-remember what was about to come next. By the time you sit down to the next session, half a dozen open loops are draining the working memory you needed for the new task. The session feels slower because part of your attention is still on the previous one.
A clean ending closes the loop. It tells your brain that this work is done for now and the next moment can have your full attention. It also makes the next session easier to start, because the runway has been left clear instead of cluttered with half-finished thoughts. The real payoff of a good descent is not the current session. It is the next one.
The Three-Step Descent Ritual
A good landing takes three or four minutes. Like the pre-flight checklist, the items are deliberately small and concrete. The point is repeatability, not elegance.
- Write what you finished. One or two sentences, in plain language, about what now exists that did not exist when the session started. "Drafted the introduction and the first two body paragraphs." "Solved problems 1 through 4, stuck on the integration in problem 4." "Refactored the auth module, tests still passing." This is not for posterity. It is for closure. Naming what got done makes the session real to you, which lets the mind release it.
- Capture what is still in the air. Anything you noticed during the session that needs attention later — open questions, things to check, ideas you do not want to lose, blockers — gets written somewhere external. A note, a task list, the back of an envelope. The medium does not matter. The act of externalizing it does. You are telling your brain: I have written this down, you are allowed to stop holding it.
- Close the cabin. Close the documents, close the tabs, close the IDE. Save what needs saving and put it away. If the next session is later today, leave one breadcrumb open — the file you will start with — and close everything else. If the next session is tomorrow, close everything. This step is the most physical of the three and it is the one most people skip. A closed workspace is a finished session. An open workspace at midnight tells your brain you are still working.
That is the descent. Three steps, three to four minutes, run before you leave the desk. If you have a deep work ritual, this is the closing half of it. Most people remember to start their ritual and forget to finish it.
What Bad Landings Cost
The cost of a bad landing shows up tomorrow. You sit down to work and you cannot remember exactly where you left off. You open three files trying to find the right one. You re-read the last paragraph you wrote, then re-read it again because the thread is gone. The first fifteen minutes of the session are spent reconstructing context that you would have had for free if you had spent two minutes capturing it the day before.
This is the energy debt. It compounds. A week of bad landings produces a Monday where the actual work does not begin until eleven, because every project requires a context-loading run. Cal Newport's "shutdown ritual," described in Deep Work, is built around exactly this problem: closing each day cleanly costs five minutes and saves thirty in the morning. The arithmetic is hard to argue with. Most people do not run a shutdown not because they disagree with the math but because the day ends in fatigue and they want to be done.
The other cost is mental. Open work sits at the back of the mind during evenings and weekends. It is not loud. It is not specific. It is the low hum of unfinished business that makes rest feel less restorative. People who cannot stop thinking about work in the evening usually cannot stop because the loops are still open. A descent ritual will not solve everything — some work is genuinely emotionally heavy — but it solves more than most people expect.
The Go-Around Rule
In aviation, a go-around is when the pilot decides not to land on this approach. The aircraft was not lined up correctly, the runway was not clear, the speed was wrong. Instead of forcing the landing, the pilot adds power, climbs back to a safe altitude, and tries the approach again. It is not a failure. It is a normal procedure. Pilots are trained to call go-arounds without hesitation because forcing a bad landing is far worse than redoing the approach.
Focus sessions deserve the same rule. If you reach the end of a block and you were not really focused — if you spent half of it scrolling, half of it daydreaming, half of it doing shallow work that was not the defined task — do not log the session as a successful focus block. Call a go-around. Note honestly that this one did not land. Take a real break, run the pre-flight checklist again, and start a fresh flight.
This sounds harsh. It is not. The point is not punishment. The point is that lying to your tracking system — telling yourself you focused for ninety minutes when you focused for thirty — corrupts the data you need to know how you actually work. If you only log clean landings, your weekly numbers reflect reality. You can see which times of day your focus actually holds, which tasks you can sustain, and which conditions tend to blow the approach. A schedule built on real data is much more useful than one built on optimistic counting.
The go-around rule also helps with self-honesty in the moment. Halfway through a session that is going badly, you have a choice: pretend it is fine and log it anyway, or admit it is not working and reset. The descent ritual makes that choice explicit. You sit down at the end and you ask: is what I did actually what this block was for? If not, the block did not land. The work might still have value, but it was not a focus session.
The Weekend Descent
The end of the work week deserves a longer landing than the end of a single session. Friday afternoon is the natural place for it. The ritual is the same as the daily descent, scaled up: write what got done this week, capture what is still in flight, close the cabin. The capture step matters more on Fridays because the open loops you do not externalize will run all weekend.
This is not a productivity hack. It is closer to a sleep hygiene principle. The mind needs to know that work is done before it can fully rest. People who cannot enjoy a Saturday usually cannot enjoy it because something they did not finish is still asking for attention in the back of their head. Five minutes on Friday afternoon spent writing down what is unfinished — not solving it, just naming it — is one of the most leveraged five minutes of the week. Remote workers especially benefit because the line between work and home is already thin, and an open laptop on the kitchen table at 9pm Friday is what makes weekends feel like spillover.
Re-entry the Next Morning
The other reason landings matter is that they make starts easier. The first thing you do on Monday morning, if you landed well on Friday, is read the note you left yourself. Not check email. Not open Slack. Read the note. It tells you what you finished, what is in flight, and where to begin. The session now has a defined start because past-you defined it.
This is the closing of the loop that the pre-flight checklist opens. The pre-flight has you define done. The descent has you write down what got done, what didn't, and what's next. The next pre-flight reads what's next and uses it to define done. Each session becomes a hand-off to the next one, and the time spent reconstructing context drops to nearly zero.
Pilots call this a flight log. Each leg is closed out so the next crew knows what they are inheriting. Even if the next crew is the same crew, the log gets written. The work of writing it down is not the same as the work of remembering it, and the difference is the entire point.
Frequently Asked Questions
How long should the descent take?
Three to four minutes. If it is taking longer, you are probably writing too much detail or trying to plan tomorrow inside the descent. The descent is for closing this session. Tomorrow's pre-flight will plan tomorrow.
What if I do not have time to land properly?
Then the session was scheduled too tightly. A focus block needs a finish, not just a duration. If you regularly run out of time before the descent, shorten the work portion of the block. A clean fifty-minute session that ends well is more useful than a sixty-minute session that just stops.
Do I need to do all three steps every time?
For sessions over forty-five minutes, yes. For shorter sessions, the "what's still in the air" step matters most — that is the one that prevents loops from staying open. The other two scale with how much got done.
What is the best way to capture open loops?
Whatever you will actually use. A paper notebook works. A single text file works. A task manager works. The medium matters less than the consistency. Pick one and use it for everything. Switching capture systems mid-week is how loops escape.
What if the session was a go-around?
Be honest in the log. Note that the approach did not work and what threw it off. That information is the most valuable kind, because patterns in failed sessions tell you more about your real working conditions than patterns in successful ones. Distracted days are not failures of character. They are data.
Takeoffs get all the attention because they feel like the hard part. They are not. The hard part is keeping the work clean, session after session, week after week, in a way that does not leak energy into the rest of your life. That requires landings as much as it requires takeoffs. A focus practice without a descent ritual is a flight that never quite ends. Close the loop. Land the aircraft. Then go enjoy the rest of your day.