Your estate plan has never been tested. Not once. You did the hard part — wrote the will, filled the binder, listed the accounts — and felt the door of relief click shut behind you. But no other human being has ever tried to actually follow it. In software terms, you shipped straight to production with zero users. And your first user will be someone who is sleep-deprived, crying, and meeting your filing system on the worst week of their life.

A backup you've never restored is not a backup

Systems administrators have a grim adage: every data-loss catastrophe features backups that existed. They ran every night for years. Nobody ever attempted a restore. When the moment finally came, the archive was corrupted, the encryption key was gone, or the job had faithfully captured everything except the one database that mattered. Until someone actually restores from it, a backup is not a safety net. It is a hypothesis with good posture.

An estate plan is exactly this kind of artifact. It is a set of instructions written for a reader who has never once shown up for a comprehension check. Aviation figured this out generations ago: pilots don't merely own checklists, they rehearse them in simulators until the procedure survives adrenaline. Office fire drills exist for the same reason — not because anyone forgot where the exits are, but because knowing and doing-under-stress are different skills, and only one of them gets people out of the building.

Your binder deserves the same skepticism. It is not a plan yet. It is a plan-shaped document.

Why you can't proofread your own plan

In 2002, Yale psychologists Leonid Rozenblit and Frank Keil documented what they called the illusion of explanatory depth. Ask people how well they understand everyday mechanisms — a zipper, a flush toilet, a helicopter — and they rate themselves confidently. Then ask them to explain the mechanism step by step, and confidence collapses. We routinely mistake familiarity for understanding, and we only discover the gap when we're forced to walk through the details out loud.

The estate-plan version of this pairs with a second well-studied bias, the curse of knowledge: once you know something, it becomes nearly impossible to simulate not knowing it. When you wrote "transfer the domain at the registrar," the sentence felt complete because your brain silently supplied the rest — the registrar is Namecheap, the login is in the password manager, the 2FA code goes to your phone, and ICANN imposes a 60-day transfer lock after ownership changes. Your reader gets nine words and none of that.

This is why rereading your own binder tells you almost nothing. As you read, your knowledge quietly patches every hole before you can notice it. The only way to see the document as your executor will see it is to watch someone else try to use it. From inside your own head, the gaps are structurally invisible.

The 30-minute fire drill

Here is the entire protocol. Pick the person who would actually step in — your spouse, a sibling, the friend you named as executor. Hand them the binder, or the login to wherever your instructions live. Give them a scenario exactly one sentence long: "I died on Tuesday. Walk me through your first day."

Then enforce three rules:

  1. They narrate out loud — what they'd read first, click first, and whom they'd call.
  2. You stay silent. No helping, no "oh, that just means—". The only sentence you're allowed is "What would you do next?"
  3. Thirty minutes, and you write down every stall — every pause, every "wait, which account?", every password that doesn't work.

The goal is not for them to finish. The goal is to find the first three walls. Most drills hit the first one inside five minutes, and it is almost never where the author would have guessed.

There's a sharper variant you can borrow from research psychologist Gary Klein: the premortem. Instead of asking "what could go wrong with my plan?", you assume it already failed: "It's six months after my death, and the handoff was a disaster. Write the story of why." Klein built the exercise on prospective hindsight — imagining an outcome as though it has already happened — which researchers Deborah Mitchell, J. Edward Russo, and Nancy Pennington found sharply improves people's ability to generate specific, concrete reasons rather than vague worries. The premortem you can run alone tonight with a pen. The fire drill needs a second human. Do both; they find different holes.

What the drill always finds

Run enough of these and the failures sort into five families.

Entry. The password manager's emergency access was never actually configured, or the invitation was never accepted, or the master password in the binder is two rotations old. This is the single most common wall, and it sits in front of everything else.

Sequence. The email account requires a code sent to your phone; the phone requires a passcode that's written in a note stored in the email account. Circular dependencies cost nothing while you're alive, because you're already logged in to everything. They become airtight after.

Vocabulary. "Registrar." "API keys." "The prod server." Words your reader cannot parse and will be too overwhelmed to research in the middle of a crisis.

Staleness. You switched banks in 2023. The doc points to a task manager you abandoned. Every line was true the day you wrote it.

Weight. The binder says where the money is but not what matters in the first hour versus what can wait a month. Acute stress measurably impairs working memory and prefrontal function — this is textbook stress physiology — so an unprioritized list turns into a wall of noise at exactly the moment your reader has the least capacity to triage it.

None of these are character flaws, and none are drafting failures. They are precisely the class of defect that no author can catch and that any real test surfaces almost immediately.

Your next moves

  • Book the drill this week. Text your would-be executor right now and ask for thirty minutes this weekend. Use the one-sentence scenario: "I died on Tuesday — walk me through your first day." You observe in silence and take notes.
  • Run a ten-minute premortem tonight. Write "The handoff failed completely" at the top of a page and list every reason it could be true. Each reason is a to-do item wearing a costume.
  • Test the front door for real. Trigger your password manager's emergency-access request yourself and confirm the waiting period actually ends in access — or print the recovery kit, seal it, and verify the other person knows which shelf it lives on. Don't assume; observe.
  • Rewrite page one for a stressed stranger. First hour only, zero jargon, plain names: "Namecheap — the company where I rent our web address. Log in using the password manager above."
  • Put the re-drill on the calendar. A recurring reminder every tax season. Plans rot quietly; thirty minutes a year keeps yours tested instead of theoretical.

The plan that's been read before it's needed

This is the premise Heirloom is built on: a death binder is for the reader, not the writer. It puts a solo founder's vault, handoff instructions, and beneficiaries in one app, structured as a sequence a person in shock can actually follow — entry first, priorities ordered, jargon spelled out — instead of a document that only makes sense with you standing behind it. But tool or no tool, run the drill. An untested plan is a hope with a table of contents. If yours has never met its first reader, give it one before it counts: heirloom.lumenlabs.works.