The Eulogy Test
“Death is the only deadline that matters.”
— The Human Manual
You are losing sleep over a quarterly review. You are rehearsing the perfect comeback to something someone said in a meeting three days ago — a reply that will never be delivered, to a slight that will not be remembered by either of you in six months. You are burning real hours of your real life running anxious simulations about embarrassing yourself in front of people whose names you will not recall in a decade.
This is a Perspective Error. The camera is so far zoomed into the noise that you’ve lost the map entirely.
The game has an end screen — hard, non-negotiable, coming on a date you do not know. Every decision you make is happening inside that constraint. And yet the hardware hides the end screen from you; the biological machine is not well-served by a constant awareness of its own mortality, so it renders infinite continues. You play as if the credits never roll. You optimize for not losing instead of winning. You guard a save file that will, with total certainty, eventually be deleted.
The terror of looking foolish has no power over a dead man. That is not a morbid observation. That is clarity, and it is available to you right now, without dying first.
The Eulogy Is Your Real Spec Sheet
Move the camera.
You are no longer in the meeting, the inbox, the comment thread. You are in a room with soft light and folding chairs. It is a nice day. The people who loved you, or were shaped by you, or simply knew you, are here in their good clothes. Someone is walking to the podium.
Now listen to the version they’d read if you died as the player you currently are.
“He kept an extremely organized inbox. He rarely offended anyone. He never took the big risk. He watched a lot of content.”
Notice what rises in your chest. That low, specific nausea — that flinch — is the most honest signal your system will send you today. It is the measured gap between the life you are currently rendering and the life you were built to render. Do not medicate it. It is diagnostic data.
Now overwrite the file. Draft the eulogy you actually want read over your body. Not a résumé. A legacy. “She built things that outlived her. He was terrified and shipped it anyway. She made the people around her fundamentally braver. He changed my life, and I can tell you the day he did it.” Get specific enough that it scares you a little.
You now hold two scripts. The distance between them is your real to-do list.
Everything else is noise the camera was zoomed into.
Why the Mirror Works
Steve Jobs ran a version of this audit for thirty-three years. Every morning, the same question in the bathroom mirror: If today were the last day of my life, would I want to do what I’m about to do? When the answer was “no” too many days in a row, he knew something had to change. He said it plainly in his 2005 Stanford commencement address: remembering that you’ll be dead soon is the most powerful tool he knew for making the large choices, because almost everything — the fear of embarrassment, the need for approval, the concern about other people’s opinions — falls away in the face of death, leaving only what is actually true.
The test does not require Steve Jobs’s certainty or charisma. It requires only honesty — the willingness to ask the question and not look away from the answer.
Social psychologists Jeff Greenberg, Tom Pyszczynski, and Sheldon Solomon built Terror Management Theory around a related but different phenomenon: when death is shoved at us suddenly and involuntarily — a near-miss, a sudden loss — mortality salience tends to make us defensive, tribal, approval-seeking. We grab status like a drowning man grabs a rope, because we need the crowd to validate that our life mattered. But Philip Cozzolino and colleagues studied a slower, deliberate variant called death reflection — sitting with your mortality on purpose, calmly, by choice — and the effect inverts. Deliberate death reflection tends to shift behavior toward generativity, toward intrinsic goals, toward what actually matters to you rather than what you think will impress the audience. The Funeral Thought Experiment is engineered death reflection: the calm version, chosen, so it sharpens you instead of scaring you.
And what people actually regret when the time runs out is documented. Palliative-care nurse Bronnie Ware catalogued the most common regrets of the dying in The Top Five Regrets of the Dying. None were about arguments lost, emails unanswered, or embarrassments endured. The first, returned again and again, was nearly universal: I wish I’d had the courage to live a life true to myself, not the life others expected of me. The dying did not regret the moments they looked foolish. They regretted the playing-it-safe. The unwritten eulogy they had spent eighty years earning for someone else’s approval.
The Reverse Engineering Protocol
Standard goal-setting starts at the present and projects forward, which is why it drifts. There is no fixed navigational point. The priorities keep shifting because the future is abstract. Invert it. Start at the only fixed point available — the grave — and engineer the path back to this morning.
Step 1 — Write the spec. Three to five sentences you want spoken at your funeral. Not résumé lines. Legacy lines. Write them in completed past tense, as if they are already true, as things that happened. “He rebuilt his relationship with his children while he still had time.” “She launched the project she kept drafting for seven years.” “He told the truth in the room where the lies were comfortable.” Make them specific enough that a stranger would know exactly what kind of person this was.
Step 2 — Run the diff. Hold this week’s calendar up beside the spec. For each line you wrote, ask honestly: what did I do in the last seven days that compiles toward this? Be honest about the spec lines getting zero commits. The blank lines in the diff are not opportunities for self-criticism. They are your actual priority list, revealed by subtraction.
Step 3 — Run the tragedy audit. Ask it plainly: If the server shut down tonight, which unwritten line would be the real tragedy? Not the unanswered messages. Not the unfinished spreadsheet. The unbuilt bridge. The unsaid words. The draft that has been a draft for three years. That line is your top-priority ticket. Not “someday.” This week. Write one sentence toward it this week.
Step 4 — Protect the spec from the inbox. The inbox is urgent. The spec is important. They are not the same category, and they fight for the same hours. Block one block per week — even ninety minutes — and label it for the spec line that is getting zero commits. The urgent will scream. Let it. The important does not scream. It just disappears.
Step 5 — Revisit quarterly, not annually. The spec evolves. You are not the same player you were a year ago. Check whether the eulogy you wrote six months ago still fits the person you are becoming — and update it if it doesn’t. The goal is not a rigid plan. It is a navigational heading, reviewed often enough to stay calibrated.
The Camera Pull-Back
Here is the inversion that the Eulogy Test actually delivers, once you run it honestly.
You came in carrying a quarterly review, a rehearsed comeback, a low-grade anxiety about what people think of you. Those things are real. They are not nothing. But from the angle of the end screen — from the eulogy room, looking back — they are not even visible. They are static in the signal, noise the camera was too close to distinguish from content.
The Reverse Engineering Protocol does not eliminate the noise. It relocates your position relative to it. Once you are navigating from the spec rather than reacting to the inbox, the noise has the same volume but a different weight. It is still there. It just does not drive anymore.
The render distance on your own death is set to zero by default — the hardware hides the end screen to keep you functioning. The Eulogy Test is a manual override. You load the end screen yourself, on purpose, in a quiet moment, so the full picture renders and the trivial stops looking large.
You are going to be dead. This is not news. It has always been the condition of the game. The question is whether you use that fact to clarify what the game is actually for, or whether you leave it in the background and keep optimizing for the quarterly review.
The spec sheet is waiting for you to write it.
Write it before someone else writes the other version.
This essay draws from The Human Manual: 101 Cheat Codes, 101 executable thought experiments for hacking your operating system. Read more about the book →
