It's 4:40 on the Thursday before your leave. You open a document and write: "Client check-in: usual stuff. Report goes out Friday, you know the one. If the portal acts up, do the thing." You read it back and it seems fine. It's even a little generous. You close the laptop feeling responsible.

On Monday, a colleague you like and respect sits in front of that page and can't tell what the usual stuff is, which report you mean, or what the thing is. They spend a morning guessing, or they message you on a beach. Neither of you is at fault in the way it feels. Something specific and well documented happened to your brain at 4:40 on Thursday.

The note that felt complete

The problem has a name, the curse of knowledge. Once you know something, it becomes very hard to imagine not knowing it.

The cleanest demonstration is a tapping experiment from Elizabeth Newton's 1990 Stanford doctoral work. She split people into tappers and listeners. Tappers picked a well-known song, such as "Happy Birthday," and tapped its rhythm on a table. Listeners had to name the song. Before the listeners guessed, the tappers predicted how often they'd succeed. They said about half the time. In reality, listeners identified roughly 2.5 percent of the songs, a handful out of 120.

The tappers weren't careless. They heard the melody playing in their heads while they tapped, and they could not un-hear it. To the listener, it was knuckles on wood.

Your handoff note is the tapping. In your head, "the usual stuff" has a full tune: who the client is, what they tend to ask, which answers calm them down. On the page it's knuckles on wood.

Why it's worst right before you leave

Three things make a pre-vacation note particularly prone to this.

You're mentally already gone. You're tired, you're sorting a dozen last tasks, and you want to be finished. Finishing feels like the goal, so a note that feels complete wins over one that is complete.

Your knowledge has gone automatic. Work you've done for months runs on habit. Habits don't announce their steps. You genuinely may not know that you always check the shared drive before sending, because you've never had to say so.

The reader is kind, and you know it. You picture a friendly colleague who will "figure it out." But figuring it out is exactly the expensive part. It's the cost the note was supposed to remove.

What makes this hard to fix is that rereading your own note doesn't help. You will always "understand" it, because you're the one person who can't fail to fill in the gaps.

The fix: write for the reader on their worst day

Researchers who study this bias generally find that being told to "be clearer" does little. What helps is changing your position relative to the material, forcing yourself to simulate someone who doesn't have your context.

Here's a concrete way to do that. Imagine your covering colleague on Monday at 9:15 a.m. You're unreachable. Something has just gone wrong. They have the note and nothing else. What do they need on the page so that they never have to ask you anything?

That framing moves the note from "things I know" to "decisions they'll face." Those are different documents. The first is a brain dump. The second is something a person can act on.

Say it out loud first

If you try writing this note while thinking about it silently, you'll produce the tapping version. A more reliable method is to explain the work aloud to an imagined colleague, as though they were sitting beside you, and capture what you say.

Speech forces sequence and context in a way typing shortcuts don't. When you say "the report goes out Friday," your own voice will nudge you into the next sentence: "which report? The weekly pipeline one, the one Dana asks about." You hear the hole as you walk into it. Explaining to a person, even an imaginary one, pulls out the step you'd never think to write.

Talk through each responsibility in this order:

  • What it is, in one plain sentence a stranger would understand.
  • Where the files, logins, or links live.
  • What "normal" looks like, so they can spot "not normal."
  • The most likely thing to go wrong, and what to do.
  • What they should leave alone until you're back.

That last item is the one people forget, and it's often the most valuable. A covering colleague's biggest risk isn't missing a step. It's confidently making a decision that was never theirs to make.

What a usable handoff entry looks like

Compare the tapping version with the same item written for a reader:

Before: "Report goes out Friday, you know the one."

After: "The weekly pipeline report goes to Dana and the sales leads by noon on Fridays. Export it from the dashboard (Reports, then Weekly) and attach it to last week's email thread so the history stays together. If the numbers look off by more than a few percent, don't send it. Message Dana and tell her it's delayed. She'd rather have it late than wrong."

The second version is four times as long, and it takes thirty seconds to read. The first one takes five seconds and costs a morning.

Notice that the "after" version includes judgment, the "she'd rather have it late than wrong" part. This is the knowledge that lives only in your head and does the most work. A checklist of clicks can be rebuilt from scratch. A sense of what the client actually cares about can't.

Your next moves

You can do all of these today, whether or not a vacation is on the calendar.

  • Run the 9:15 test. Pick one responsibility you're handing off. Write the first line of its entry by finishing this sentence: "If something goes wrong with this on Monday morning, the first thing to do is..." If you can't finish it quickly, that's the gap.
  • Talk it through for five minutes. Open a voice memo or dictation tool and explain your week to an imaginary colleague. Don't edit. Read the transcript afterward and underline every sentence that a newcomer would need explained.
  • Add a "leave alone" line to every entry. One sentence naming what shouldn't be touched, changed, or decided without you.
  • Hand the note to someone who doesn't know the work. Not your closest teammate. Ask a person outside the project to tell you what each line means. Every question they ask is a tap that didn't sound like a song.
  • Write down where you can be reached, and when you shouldn't be. Name one person who can make decisions in your absence, so your cover never has to choose between guessing and contacting you.

A note on why this is worth the effort

Something quieter is going on here too. A good handoff is a small act of trust, and it works in both directions. It tells your colleague you believe they're capable, and it spares them the unfair position of being held responsible for things nobody told them. It also lets you actually be away. Part of what ruins a vacation is the low hum of knowing your note was thinner than it should have been.

The curse of knowledge doesn't go away because you know about it. You still can't un-hear the song. You can only build habits that pull it out of your head and onto the page, and speaking aloud is the most dependable of those.

This is the kind of writing we built Quill for. You speak your explanation as if to a colleague across the desk, in any app, with the transcription happening privately on your device. A rewrite tool then tightens it into a clean, readable note, without the Thursday-afternoon shortcuts. If you'd like to try drafting your next handoff that way, you can find Quill at quill.lumenlabs.works.