A single sharp, glowing filament of light persisting among many faded, dissolving threads in the dark Brain Science
AI-generated, Working Theory
Brain Science · the neuroscience of building · ◉ Evergreen

The best memory is mostly forgetting

by · ·4 min·Working Theory

When you give a product memory, the hard design work isn't what it stores — it's what it demotes, decays, and drops. A memory that returns everything with equal confidence isn't serving your user.

Everyone is bolting memory onto their products right now. The assistant that remembers your name, the agent that recalls last week’s project, the feed that has quietly memorized every thing you’ve ever paused on. The pitch is always the same, and it always sounds like more is better: it remembers everything. Hold that thought against what neuroscience actually knows about memory, and the pitch starts to look less like a feature and more like a bug you haven’t hit yet.

Here is the uncomfortable finding. Forgetting is not your brain running out of room, and it is not the tape wearing thin. Forgetting is a process — an active, energy-spending, purpose-built process the brain invests in as deliberately as it invests in remembering. There are mechanisms whose entire job is to weaken and clear memories, and they run in a healthy brain that has plenty of capacity to spare. A well-known synthesis of this work put it bluntly: the goal of memory isn’t to transmit the most accurate record of the past, it’s to guide good decisions in the future. And for that goal, keeping less is often better. Transience — the graceful decay of detail over time — lets you generalize, notice what recurs, and stop tripping over specifics that no longer matter.

You can see why by looking at the rare people who can’t forget. The most famous case in the literature was a man who could memorize essentially anything — pages of numbers, poems in languages he didn’t speak — and hold them for years. It reads like a superpower until you learn how he actually lived: buried in detail, unable to grasp a metaphor or recognize a face across a change in lighting, drowning in the particular. He remembered every tree and could not see the forest. Fiction got there first — Borges wrote a character so incapable of forgetting that he couldn’t think, because thinking requires throwing detail away. A perfect memory is not a sharper mind. It’s a clogged one.

There’s an even deeper point hiding in how the brain decides what to drop. One influential analysis showed that the human forgetting curve isn’t arbitrary — it closely tracks how likely a piece of information is to actually be needed again, based on how it’s shown up in your environment. Things you’ve encountered often, or encountered recently, are held onto; things that appear once and vanish are let go. In other words the brain runs a quiet, constant bet on relevance, and forgetting is how it collects. Memory is tuned to the world’s statistics, not to completeness.

REMEMBER EVERYTHING nothing decays → noise buries signal which of these mattered? FORGET ON PURPOSE decay + salience → signal stays legible relevance + recency filter what you'll actually reuse
Two designs for a product's memory. Keeping everything at equal weight doesn't preserve signal — it buries it. A memory that decays and weights by relevance is what stays useful. Original diagram · Working Theory

So here’s the build decision, and it runs against the marketing instinct. When you give your product a memory, the hard and valuable design work is not in what it stores — storage is cheap and nearly infinite, which is exactly the trap. The work is in what it demotes, decays, and drops. A memory that returns everything with equal confidence is not serving your user; it’s handing them the mnemonist’s problem, a pile of undifferentiated detail they now have to sort themselves. The intelligence your product appears to have is almost entirely in its forgetting: what it lets fade, what it declines to resurface, what it quietly decides wasn’t worth keeping.

Concretely, that means a few things. Weight by salience, not by occurrence — the thing the user acted on, returned to, or corrected matters more than the thing they scrolled past, and your memory should hold them differently. Let recency and relevance decay the rest, so old context loosens its grip instead of competing forever with what’s true now. Give the user a way to prune — an editable, forgettable memory is more trustworthy than a perfect one, because a system that can never forget is a system that can never be corrected. And when you resurface, resurface a little: the correct output of a good memory is usually one well-chosen thing, not a transcript.

The products that will feel like they have a mind are not the ones that record the most. They’re the ones that forget well — that mistake nothing important for noise, and let the noise go. Completeness is what a hard drive does. Judgment is what’s left after you throw the rest away.

The science, to look up: adaptive forgetting and transience (Richards & Frankland, “The Persistence and Transience of Memory,” Neuron, 2017); the rational analysis of memory / need-probability (Anderson & Schooler, 1991); directed and motivated forgetting (Bjork); the case of Solomon Shereshevsky (Luria, The Mind of a Mnemonist); and Borges’ short story “Funes the Memorious” as the literary illustration. Mechanisms and the strength of the “forgetting is adaptive” claim are still debated — the robust core is that forgetting is an active, functional process, not merely decay or storage failure.

Sources

  • Adaptive forgetting and transience (Richards & Frankland, Neuron, 2017)
  • the rational analysis of memory / need-probability (Anderson & Schooler, 1991)
  • the case of Solomon Shereshevsky (Luria)
  • Borges' "Funes the Memorious"

Liked this? Get the next one in Working Theory.

Going weekly in August (it's in beta now). One genuinely interesting read on building, the brain, and the science most people missed.

Subscribe →
Got a reaction, a counter-example, or something I missed? Reply by email — I read everything.
◉ join in

Where have you hit this — in a product you use, or one you're building?

Threads open here soon. For now, the conversation lives two clicks away — discuss on GitHub, or just reply by email. I read and answer everything.