Ask a solo founder whether their partner understands the business, and you'll usually get a confident yes. Ask the partner, and you'll get something else: I know he has clients. I know money comes in on the 1st. I think there's a company, like an LLC or something? I don't know where anything is.

Both people are telling the truth. That's the disorienting part. The founder genuinely believes the information has been transmitted, because for four years it's been mentioned at dinner — the churn problem, the annoying client, the Stripe payout that was late. The partner heard all of it. What they never received was the thing underneath: the map. And nobody noticed the gap, because the gap doesn't announce itself until the day one of you can't be asked a follow-up question.

The illusion that you already explained it

Psychologists have a name for this. In the 1990s, Thomas Gilovich and Kenneth Savitsky studied what they called the illusion of transparency — our tendency to overestimate how visible our internal states are to other people. Liars think their deception is obvious. Nervous speakers think the room can see their heart pounding. The findings generalize past emotion into knowledge: we assume the contents of our head are leaking out more clearly than they are.

Its older cousin is the curse of knowledge, first demonstrated by economists Colin Camerer, George Loewenstein, and Martin Weber, and later made vivid in Elizabeth Newton's tapping study — one person taps a familiar song on a table, the other tries to name it. Tappers expected listeners to guess about half the time. Listeners got roughly one in forty. In the tapper's head, the melody is playing. To the listener, it's just knuckles on wood.

You have been tapping your business on the table for years. You hear the whole arrangement — the vendor who has to be paid before the renewal or the domain lapses, the reason the business bank account is at that particular credit union, the fact that "the app" and "the LLC" and "the Stripe account" are three legally distinct things that happen to live in your body. Your spouse hears knuckles. They have no idea the song has a bridge.

This is why the death binder, on its own, doesn't work. A binder is a tapped melody in written form. It assumes a reader who already knows what the words point to.

The mutual knowledge problem

There's a second layer, and it's the one that actually strands families.

Coordination researchers distinguish between shared knowledge and common knowledge. Shared knowledge is when you both know something. Common knowledge is when you both know it, and you each know the other knows it, and you each know that — a recursive ladder that Herbert Clark's work on conversational grounding shows is what actually lets two people act together without checking in.

Most founder households have shared knowledge and almost no common knowledge. You know there's a password manager. Your spouse knows there's some kind of password thing. Neither of you knows whether the other knows the master password exists, is required, and cannot be recovered by pleading with a support agent. So no one asks. Each of you privately assumes the other has a handle on it. That mutual assumption is load-bearing, and it holds up perfectly right until it doesn't.

Grief makes this worse in a specific, mechanical way. The most useful frame here is cognitive load theory — working memory is a narrow channel, and acute stress and grief consume it. Bereaved people are not stupid; they are running at capacity. A widow trying to figure out what a "registrar" is, three weeks after the funeral, is not doing research. She is doing archaeology, in a language she doesn't read, under a deadline she didn't know existed, while her working memory is fully occupied with something else.

The conversation is not a data transfer

So founders resolve to "sit down and go through everything." It goes badly, usually one of two ways.

The first: it becomes a lecture. You talk for ninety minutes. Your spouse nods. Nothing is retained, because listening is not the same as encoding — the retrieval-practice literature (Roediger and Karpicke, among many) is unambiguous that pulling information out builds durable memory in a way that pushing it in does not. Your partner will remember the mood of the evening and none of the content.

The second: it becomes a fight about death. You wanted to discuss the domain registrar. Your spouse heard you are preparing to leave me. Terror management research — the body of work descended from Ernest Becker and formalized by Greenberg, Pyszczynski, and Solomon — documents how directly confronting our own mortality triggers defensive maneuvers: distraction, distancing, sudden irritation about something adjacent and safe. Both of you have a nervous system that would rather do the dishes.

What works is smaller, stranger, and much less noble. You don't explain the business. You make your spouse use it, badly, while you're alive to laugh about it.

This is a fire drill, not a briefing. Nobody learns a building by reading the evacuation map. They learn it by walking to the stairwell once while the alarm is fake and the stakes are zero.

What a fire drill actually looks like

Sit together. You do not touch the keyboard. Your spouse tries to answer one question — how much money did the business make last month? — out loud, doing the clicking.

They will get stuck at the first step, and the first step is never the one you predicted. Not the Stripe dashboard. The email account the Stripe login recovery code goes to. Or the phone that has the authenticator app. Or the fact that they typed your name into a login field and it needed a username they've never seen.

Every place they get stuck is a real failure your family would have hit at the worst possible moment. You just discovered it on a Tuesday, with the person who knows the answer sitting right there. That is the entire value of the exercise. Watching someone else fail to open your business is the only honest audit of whether it can be opened.

And it converts the vague, terrifying subject — your death — into the specific, boring subject: the 2FA code goes to your old phone, which is in a drawer, dead. Concreteness is what lets a couple actually talk about this. Nobody can hold "when you die" in their body for an hour. Anybody can fix a drawer.

Your next moves

  • Run a fifteen-minute drill this week. Hand your spouse or executor the laptop and ask them to find, unassisted, how much revenue the business made last month. You may not touch the keyboard or give hints for the first five minutes. Write down every place they get stuck — that list is your real to-do list, not the one you imagined.
  • Ask three retrieval questions instead of explaining. Where is the money? Who gets paid automatically every month? Who would you call first? Their answers, said aloud, reveal the gaps far faster than any explanation you could deliver. Silence is data.
  • Name the entity out loud, once. Say the legal name of your company, the state it's registered in, and where the formation documents live. Then have your spouse repeat it back. Most partners have never heard the actual legal name of the business that supports them.
  • Do one recovery test on the master key. Whatever unlocks everything else — usually the primary email account and its 2FA — verify today that a second human being could actually reach it. Not "knows it exists." Reaches it.
  • Schedule the next drill before you finish this one. Six months out, on a calendar, with a name that isn't grim. Access rots quietly: phones get replaced, recovery numbers change, accounts move.

The part you can't offload

Everything above is free, and you should do it whether or not you ever install anything.

But a drill produces a list, and a list needs somewhere to live that isn't a note on your laptop that only you can open. Heirloom exists for exactly that afterward: the vault your credentials and entity documents live in, the handoff that names who receives what, the beneficiary details written for someone in shock rather than someone in business mode — held in one place, so the person who fails your fire drill in June has an actual answer waiting for them in December.

Run the drill first. Then, if you'd rather the answers outlive the conversation, put them somewhere your family can reach: heirloom.lumenlabs.works.