Open loops, the Zeigarnik effect and the cost of unfinished tasks

You close the laptop, but the bug follows you to dinner.

Or you start a new feature while half your mind stays on the pull request you did not finish. Most developers know this feeling. Productivity writers have a name for it: an open loop.

Here is what research says about open loops, a common myth worth correcting, and a simple way to close them.

In short

• The classic "Zeigarnik effect" (better memory for unfinished tasks) did not hold up as a general rule in a 2025 meta-analysis. A tendency to resume unfinished tasks did.
• In 2011 experiments, unfinished goals caused intrusive thoughts and worse performance on unrelated tasks.
• Making a specific plan for the goal removed those effects.
• In practice: write down the next concrete step for each loop, give it a when, and keep it where you will see it.

The Zeigarnik effect, and a correction

In the 1920s, psychologist Bluma Zeigarnik reported that people remembered interrupted tasks better than completed ones. The finding became the "Zeigarnik effect", and productivity articles cite it often.

The full story is more careful. A 2025 meta-analysis found no general memory advantage for unfinished tasks. It did find a general tendency to resume unfinished tasks, a related finding called the Ovsiankina effect (Ghibellini & Meier, 2025). The authors suggest the memory effect depends on the situation, for example how involved people are in the task.

So "unfinished tasks are always remembered better" is not supported. "Unfinished tasks pull you back toward them" has better support.

How unfinished goals intrude on other work

For developers, the most useful study is about intrusions, not recall.

Masicampo and Baumeister (2011) ran a set of experiments that activated a goal and left it unfinished. They found:

• Unfinished goals caused intrusive thoughts during an unrelated reading task.
• Goal-related words were more mentally accessible.
• People did worse on an unrelated anagram task.

Then some participants made a specific plan for the unfinished goal. The plan removed these effects.

There was a catch. The effect depended on how earnest the plan was: participants who later carried out their plans were the ones who showed no more intrusions. The authors concluded that once you commit to a specific plan, the drive to reach the goal can pause. It resumes at the time you set.

Open loops in a typical coding day

A developer's day is full of them:

• A failing test you will fix "after this"
• A code review comment you must answer
• A migration you need to run on staging
• A question for a teammate
• Three AI agent sessions that each wait for you

You cannot finish them all at once. The 2011 study suggests you do not have to. What you need is a specific plan for each one, written down where you will see it.

Compare the two. "Fix the test" is a vague intention. "Fix OrderTotalTest: the tax rounding, after lunch" is a plan.

Get loops out of your head

Using an external tool to reduce mental load is called cognitive offloading (Risko & Gilbert, 2016). A phone reminder, a sticky note and a checklist all count. In online experiments with 1,196 participants, external reminders improved performance on a task that required people to remember intentions for later (Gilbert, 2015).

A four-step method:

1. Capture. When a new loop opens, write it down at once. Do not wait for a good time.
2. Make it specific. Name the file, the test, the person or the command.
3. Give it a when. A deadline or a reminder turns an item into a plan.
4. Close it visibly. Remove the item when it is done.

Closing loops with Focus Pad

Focus Pad in DevWorkspace Pro fits this method well. It is a Markdown checklist in a small window that stays on top of your other windows.

Loops also arrive from your tools:

• GitHub issues: use Send to Focus Pad on any issue. When you complete the task, Focus Pad asks if you want to close the issue.
• AI agents: with the Focus Pad MCP server, an agent such as Claude Code can add its open items to your list.
• Unfinished AI sessions: after a restart, a to resume button shows each session that was still open. See Resume Claude Code sessions.

A five-minute end-of-day shutdown

This short routine puts the plan-making finding to work:

1. Open Focus Pad.
2. For each open loop, write the next concrete step.
3. Set a deadline on the ones that matter tomorrow.
4. Close the laptop.

The loops are still open. But each one now has a plan and a place, so it has less reason to follow you to dinner.

References

• Masicampo, E. J., & Baumeister, R. F. (2011). Consider it done! Plan making can eliminate the cognitive effects of unfulfilled goals. Journal of Personality and Social Psychology, 101(4), 667–683. https://doi.org/10.1037/a0024192
• Ghibellini, R., & Meier, B. (2025). Interruption, recall and resumption: A meta-analysis of the Zeigarnik and Ovsiankina effects. Humanities and Social Sciences Communications, 12, 962. https://doi.org/10.1057/s41599-025-05000-w
• Risko, E. F., & Gilbert, S. J. (2016). Cognitive offloading. Trends in Cognitive Sciences, 20(9), 676–688. https://doi.org/10.1016/j.tics.2016.07.002
• Gilbert, S. J. (2015). Strategic offloading of delayed intentions into the external environment. Quarterly Journal of Experimental Psychology, 68(5), 971–992. https://doi.org/10.1080/17470218.2014.972963