In 1927, a Russian psychologist named Bluma Zeigarnik sat in a busy Berlin restaurant and noticed something about the waiters. They could recall the details of an unpaid order with almost perfect accuracy: who ordered what, at which table, in what sequence. The moment the bill was settled, the memory evaporated. Ask a waiter about a table that had already paid and he drew a blank. The open order lived in his head. The closed one did not.

Zeigarnik took that observation into the lab and confirmed it. People remember interrupted or unfinished tasks far better than completed ones, because an incomplete task keeps a kind of tension alive in the mind. Almost a century later, that finding has a name managers should know, and a practical consequence most of them are paying for without realizing it.

The tax you pay for work you haven’t finished

Every task you start and do not finish leaves a tab open in your head. Not a metaphor exactly, a measurable cognitive load. Your brain keeps a background process running that quietly checks, over and over, whether that thing got handled. The report you half-drafted, the difficult message you meant to send, the decision you deferred until “later this week.” None of it is in front of you, and all of it is using capacity.

Sophie Leroy, a researcher then at the University of Minnesota, put a sharper edge on this in 2009 with a concept she called attention residue. In a series of experiments published in Organizational Behavior and Human Decision Processes, she moved people from one task to another under time pressure and measured how they performed on the second task. The result: when the first task was left unfinished, part of their attention stayed stuck on it. They did worse on the task actually in front of them, because a slice of their working memory was still occupied by the one they had walked away from.

For a manager, this is not an occasional problem. It is the shape of the entire job. You do not work one task to completion and then start the next. You get pulled off the budget to answer a question, off the question to handle an escalation, off the escalation into a one-on-one. Microsoft’s 2025 Work Trend Index found that workers are interrupted up to 275 times a day, roughly once every two minutes across the working day, and that 80% report lacking the time or energy to do their job effectively. Managers sit at the center of that storm. Every interruption is a task left mid-air, and every task left mid-air keeps drawing a small tax on the work that comes after it.

The insidious part is that you cannot feel the tax directly. You just notice that you are busy all day and somehow foggy, that you reread the same paragraph three times, that you snapped at someone over something small. That fog is the accumulated hum of a dozen open loops running in the background. This is closely related to why your brain runs out of capacity by mid-afternoon, and it compounds the switching cost I have written about in the switching tax.

The fix is not “finish everything”

Here is where most productivity advice goes wrong. It tells you the answer is to finish what you start, to stop leaving loops open, to power through. That is not advice, it is a wish. No manager finishes everything they start in a day. The interruptions are the job.

The genuinely useful finding came in 2011, when E. J. Masicampo and Roy Baumeister ran a study with a title that gives away the ending: “Consider It Done! Plan Making Can Eliminate the Cognitive Effects of Unfulfilled Goals,” published in the Journal of Personality and Social Psychology. They confirmed that unfinished goals interfere with concentration on other tasks, exactly as Zeigarnik and Leroy would predict. Then they did one more thing. They asked some participants to write a specific plan for when, where, and how they would complete the unfinished task.

The interference disappeared. Not because the task got done, it did not. Because the mind got what it was actually asking for. Your brain’s background process is not checking for completion. It is checking for a credible commitment to a resolution. Give it a concrete plan, and it stops nagging. “I’ll finish the budget draft tomorrow at 8am before standup” quiets the loop almost as well as finishing the budget does.

That distinction is worth sitting with, because it changes what you do at 5pm on a day where nothing got finished. You do not have to work three more hours. You have to close the loops on paper.

What closing the loop actually looks like

David Allen built an entire methodology, Getting Things Done, on a version of this idea. He calls unfinished commitments open loops and argues that anything you consider unfinished has to be captured in a trusted system outside your head, because your mind is for having ideas, not holding them. When you trust that a commitment is recorded somewhere you will actually see it again, your brain relaxes its grip. When you do not trust the system, the brain refuses to let go, and you carry the whole list around all day.

You do not need his full apparatus to get the benefit. You need two things, done consistently.

First, capture the loop the moment it opens. When someone stops you in the hallway with “can you look at the vendor contract,” the task is now open whether you write it down or not. The only question is whether it lives on a list or in your head. Put it on the list. The physical act of writing it somewhere reliable is what tells your brain it is safe to stop tracking it.

Second, give each open loop a next action and a when. This is the part people skip, and it is the part the research says matters most. “Vendor contract” is not a closed loop, it is a vague worry with a noun attached. “Read section 4 of the vendor contract Thursday morning and send legal my two concerns” is a plan. Same task, entirely different weight in your head. The specificity is not bureaucratic tidiness. It is the exact thing that satisfies the mind’s demand for a resolution pathway.

I learned this the hard way running IT operations. During a large network rollout years ago, I was holding somewhere north of forty active threads: vendor timelines, staffing gaps, a budget that kept moving, three escalations that could each blow up the schedule. I was working fourteen-hour days and still felt behind at every moment, including the moments when I was objectively ahead. The problem was not the workload. It was that I was trying to hold all forty loops in my head at once, and my head was rebroadcasting every one of them on a loop while I tried to focus on any single one. The week I started doing a hard end-of-day pass, writing the specific next step and the specific time for every open thread, the fourteen-hour days did not get shorter. But the fog lifted. I slept. I stopped waking up at 3am with a “did I forget the firewall change” jolt, because the firewall change had a plan and my brain believed it.

The manager’s multiplier

There is a version of this problem that hits managers specifically, and it is worth naming. You do not just carry your own open loops. You carry your team’s. Every “let me get back to you” you say in a one-on-one is a loop you now hold on someone else’s behalf. Every decision your team is waiting on is a loop parked in your head that is also blocking theirs.

This is one of the strongest arguments for real delegation, the kind I described in handing off work so it actually gets done. When you delegate a task cleanly, with a clear owner and a clear next step, you are not just moving work. You are closing a loop in your own head and opening it in someone else’s, where it belongs. When you delegate badly, with a vague “keep an eye on that,” you have done the worst possible thing: the loop is now open in two heads and owned by neither. It will nag you both and get done by no one.

The same logic applies to how you run your intake. A manager who says yes to every incoming request is not being generous, they are opening loops faster than any human system can close them. I have argued before that what you decline is what protects your team’s throughput, and the open-loop research is the cognitive version of that same truth. Every commitment you accept is a background process you have agreed to run until it resolves.

The five-minute habit worth building

If you take one practice from this, make it the end-of-day loop close. Before you shut down, spend five minutes doing exactly what Masicampo and Baumeister’s participants did. Look at everything still open. For each one, write the next physical action and the time you will do it. Not a to-do list of nouns. A short list of plans.

You will not finish more work by doing this. You will carry less of it home. And the version of you that shows up tomorrow, rested instead of rehearsing a mental list at 3am, is a measurably better manager than the one who tried to hold all forty threads in his head overnight.

The waiters in Zeigarnik’s restaurant had it easy. Their loops closed when the bill was paid. Yours close when you write down what happens next. Do that reliably, and your mind will finally do what a good system lets it do: respond to what is actually in front of you, and let go of what isn’t.