16/The Zeigarnik effect

The Tab You Can't Close

The unfinished thing is not in your head because it matters. It is there because it is unfinished.

5 minute read · 2 sources, linked · by Joe Lee

1927the study everybody cites
Shakywhat its replication record looks like
Lewinwho actually wrote the paper at that DOI

You are forty minutes into good work and a thought arrives about the invoice.

Not a useful thought. There is nothing you can do about the invoice at 10:40 on a Tuesday, and you know that, and it does not matter, because it is going to come back in about four minutes and it is going to keep coming back for the rest of the hour.

The invoice is not important. It is open. Those turn out to be very different properties, and only one of them explains why it keeps interrupting you.

The idea, named, with the receipt problem stated up front

The Zeigarnik effect. Bluma Zeigarnik, 1927, working out of Kurt Lewin's group in Berlin. The claim you have heard: people remember interrupted or unfinished tasks better than completed ones, because an incomplete task maintains some kind of open tension until it is closed.

Two honest problems with that sentence, and I would rather hand you both than have you find them.

One: the replication record is shaky. This is one of those early findings that got repeated into the status of a law, and the follow-up work has been considerably less tidy than the story. I am not going to tell you it is a robust effect, because I do not know that it is.

Two, and this one is a genuinely good trap. Go looking for the Zeigarnik citation and you will land on a DOI in Psychologische Forschung, volume 9, 1927, pages 1 to 85. Journal matches. Volume matches. Year matches. Pages match.

It is Kurt Lewin's framing piece for that series. Not Zeigarnik's paper. Ask Crossref for the metadata and the author comes back as Lewin. A link checker would pass it, because the link resolves perfectly. It is simply the wrong paper.

So there is no URL on this piece for the 1927 study, and that is a decision, not an oversight. Zeigarnik, B. (1927), on finished and unfinished tasks, cited by author and year, which is what an honest citation looks like when you have not verified more than that.

Where the story starts: waiters who could recall every open order and forgot them the moment the bill was paid.
Where the story starts: waiters who could recall every open order and forgot them the moment the bill was paid.
The practice is defensible and the famous study is not, so I am going to build on the practice and tell you which is which.

What survives, and it is enough

Strip out the 1927 study entirely and the practical claim still stands on its own feet, because it does not depend on the study.

An unresolved thing you are holding in your head costs you something while you hold it. Write it down somewhere you trust and the cost drops. That is the entire operating principle of David Allen's Getting Things Done, which is a book, not a paper, and which has been run by an enormous number of people who all report roughly the same thing.

Allen, D. (2001). Getting Things Done. Cited by author and title. No DOI, because there is no journal article.

The thought in your head versus the thought on a pageHeld in your head, an unresolved thought keeps returning through the hour. Written down once, it stops. The externalisation is the part of this mechanism that does not depend on the 1927 study.ZEIGARNIK 1927 · ALLEN 2001One hour, one unresolved invoice, and the only variable is where you put it.HELD IN YOUR HEAD:12It comes back.WRITTEN DOWN, ONE FIELD:12It does not.MONDAY 09:00The defensible claim is externalisation, not the 1927 finding.And the DOI most people cite for Zeigarnik resolves to a paper by Kurt Lewin.

Externalisation is what is defensible here. Not the tension, not the memory finding, not the neat 1927 story. Just this: the thought is taking up room, and paper is cheaper room than your head.

That is a smaller claim than the one usually made for this mechanism, and it is the one I am willing to build on.

Closed orders. The spike is where a thought stops costing anything.
Closed orders. The spike is where a thought stops costing anything.

Why your notes app is not doing this job

Because a capture tool with tags, projects, due dates and a priority field is not a place to dump a thought. It is a place to file one, and filing is work.

Watch what actually happens at minute forty. The invoice arrives, you reach for the app, and now there is a small decision tree: which list, does it need a date, is it a task or a note. Ten seconds of that and you have left the hour. You have not closed the loop. You have opened a second one and gone to live in it.

The requirements for a working version are almost aggressively low. It has to be within reach without leaving the work. It has to take the thought with no structure attached. And you have to believe you will see it again, or the thought will not let go.

That last one is the whole thing. A dump you never revisit stops working within about a week, because some part of you keeps checking, correctly, that nothing is looking after this.

The lineage, credited

The direct parent of what I built is Matthew Larsen's Work Form System: a 60-minute unit, a written record of every hour, a wall of documents you read back, a small group that knows whether you showed up. Larsen is openly assembled from Hill on autosuggestion, Maltz on self-image, Cardone on 10X sizing, Hormozi on beliefs, traits and skills, Jobs via O'Leary on signal versus noise, Clear on the habit loop.

His version of this is the worry list, and the part I took wholesale is what he does with it afterward. It does not just sit there. Monday's first hour is an Anti-Worry Hour, list open, and the worries get worked rather than admired.

That is the piece nearly every capture system is missing. Capture is half a mechanism. The other half is a standing appointment where the captured things get dealt with, because that appointment is the reason the dump is believable in the first place.

What we built

A worry box, open for the whole hour, one field.

No tags. No projects. No due dates. No priority. You type the invoice, you go back to work, and the box holds it.

WHERE THIS LIVES IN THE PRODUCT

Deep Mode, included with Full Access. One box, open the whole hour, no tags and no due dates. It exists to get the thought out of your head, not to become a second system you have to run.

Two rules, and both of them are the mechanism rather than the interface.

It does not become a task manager. Every instinct says add structure to it, because structure is what software is good at. Structure is precisely what makes it too expensive to use at minute forty. It stays one field, and the cost of that is that it will never look impressive in a screenshot.

Monday's first slot defaults to an Anti-Worry Hour, list open, straight out of Larsen. That is the appointment that makes the dump trustworthy. The loop actually closes, on a schedule, and you can point at when.

This is Deep Mode, which is Full Access. The free session gives you the room, the person, the timer and the intention box.

The ask

You do not need my software for this one, and it is one of the cheapest wins on the whole list.

Put a blank page next to you for the next hour. When something arrives that you cannot act on right now, write four words and go back. Then, and this is the part people skip, book a real slot later in the week to actually look at the page.

Capture without a review is a drawer. It works for a while and then everybody stops believing in it, including you.

Paper is cheaper room than your head. The review is what makes the paper believable.
Paper is cheaper room than your head. The review is what makes the paper believable.

That's why I built this. I needed it. I lost a lot of good hours to an invoice I could not have paid at the time anyway.

Free, one session a day, no card

Sources

  • Zeigarnik, B. (1927). On finished and unfinished tasks. Cited by author and year only: see the honesty note, there is no URL published for this one on purpose.
  • Allen, D. (2001). Getting Things Done. Book, cited by author and title, no DOI.