The Curse of Knowledge: Why Your Old Notes Make No Sense

There is a well-known demonstration where one person taps out the rhythm of a famous song on a table and another tries to name it. Tappers expect listeners to get it around half the time. Listeners get it around two or three percent of the time.

The tapper hears the whole song. The listener hears knocking. And the tapper cannot make themselves hear knocking, because you cannot un-know a tune once it is playing in your head.

That is the curse of knowledge: once you know something, you lose the ability to model accurately what someone without that knowledge experiences. Including, crucially, your own future self.

The version that ruins notes

Every note you write is written by an expert in that moment. You have just had the conversation, read the paper, debugged the problem. The context is fully loaded, and it is invisible to you precisely because it is loaded.

So you write "check the fallback path" and it feels complete. Eight months later the fallback path could mean four things, you no longer remember which system was involved, and the note is a fossil.

This is not a memory failure. The information was never in the note. Your past self felt it was, because they were reading the note with the context still running.

The diagnostic

There is a reliable test, and it takes one second.

Could a competent stranger act on this note?

Not a stranger to the field, a stranger to this situation. If they would need to ask you a question to proceed, write the answer to that question now. Your future self is exactly that stranger, with the disadvantage of not being able to ask.

A few common gaps this catches:

What you wrote What is missing
"Ask Marta about the pricing thing" Which pricing thing, and what you need from her
"Doesn't work on staging" What doesn't, what you expected, what you saw
"Good point re: attrition" Whose point, what it was, why it was good
"Revisit in Q3" The condition that should trigger revisiting

Each fix is under ten words, and each one is the difference between a note and a fossil.

Why proofreading your own writing fails

The same bias explains a smaller, daily annoyance: you cannot reliably catch errors in your own text. You read what you intended, because the intention is loaded and the words are just a cue for it. A fresh reader has no intention loaded, so they see what is actually on the page.

This is closely related to inattentional blindness, and it is why every serious writing process involves either another person or a delay long enough to make you a stranger to your own draft.

The organisational version

At scale, the curse of knowledge is the reason documentation is bad almost everywhere.

The person who understands the system best is the worst-placed to explain it, because their model of what is obvious is calibrated to themselves. The person who just learned it is the best-placed and is rarely asked. This is a straightforward argument for having new joiners write the onboarding documentation while they are still confused, which is a practice that works and almost nobody does. See how to take notes in a new job.

The same applies to handover. A handover document written by the departing expert lists what they think matters. What the successor needs is the tacit part, and the expert cannot see it. The fix is to have the successor write the document from questions, with the expert answering. See note-taking for teams.

Practical defences

Write the because. Almost every fossilised note is missing a reason. "Moved the deadline" is a fact; "moved the deadline because legal review takes three weeks and we started late" is a note that still works later.

Date and name things fully at least once. Pronouns and shorthand are the first casualties of time. Spell out who and what once per note, then abbreviate.

Include what you rejected. Future you will consider the same alternatives again. A line recording that you tried X and it failed for reason Y saves a repeat.

Re-read something old on a schedule. A monthly pass over notes from a year ago tells you exactly which of your habits produce fossils. It is the only feedback loop available for this, and it is fast. See how to review your notes and the weekly review.

Prefer sentences to fragments for anything you intend to keep, for reasons set out in bullet points vs full sentences.

The uncomfortable part

Knowing about the curse of knowledge does not remove it. Experts told about it still overestimate how clear they are being. The bias operates below the level you can introspect on, which is why the defences above are all mechanical: a question you ask, a word you always include, a review you schedule.

You cannot think your way out of it. You can build the missing context into the note as a habit, and that works.

More in metacognition, the illusion of competence, and how to name notes.

More in Memory & Focus

75 more notes on this branch.

Clair Mind connects your own notes exactly like this — automatically, privately, on your iPhone. Get the app →