mission as a working list, not a bucket list
A bucket list is decoration. A working list is a contract with the future you can read out loud. The difference shows up at year five.
I have kept a personal mission list since 2008. Across thirteen years it has been called many things — life goals, the project list, “things I want to do before I die.” None of those names fit it. The list is not aspirational. It is operational. It is the contract I make with the next version of me about what I am actually working toward.
The closest accurate name is working list, distinct from bucket list. The two are similar in surface — both are lists of things you want to do — but they behave very differently in practice. The working list compounds. The bucket list mostly sits.
Here is the difference, and why mine has stayed alive for thirteen years while most bucket lists die in their first one.
the bucket list problem
A bucket list is aspirational. The items are big, vague, and undated. “Travel to 50 countries.” “Write a book.” “Run a marathon.” Each item is more identity statement than plan. The list is curated for who the writer wants to be, not for what the writer will actually do.
The list mostly does not change. New items get added rarely. Old items get crossed off rarely. The list sits in a drawer or a Notes app, visible occasionally, motivating less often than it was supposed to.
The structural failure is that there is no feedback loop between what is on the list and what the writer is doing today. Bucket lists are decoration. Useful as identity expression. Not useful as a planning tool.
the working list
A working list is dated, sized, and ranked. The items are concrete enough to evaluate progress against. The list itself updates frequently — items get added when new commitments form, removed when reality changes, marked done-failed when an attempt did not work out.
The format I have used since 2008 is roughly this:
id │ title │ status │ year
01 │ ship a daily journal app │ in-progress │ 2026
02 │ build a public quant lab │ done │ 2026
03 │ run a half-marathon │ done-failed │ 2019
04 │ open-source a useful library │ done │ 2014
05 │ home library (1000+ books) │ partial │ 2030
06 │ teach at a university course │ todo │ —
07 │ visit Antarctica │ deferred │ —
08 │ ...Six statuses, mapped to the actual state of each item.
todo │ not started, no current commitment
in-progress │ active work in some specific quarter
partial │ partly completed, may continue
done │ accomplished
done-failed │ attempted, did not succeed, not retrying
deferred │ no longer pursuing, intentionallyThe done-failed status is the most important one. Bucket lists have no equivalent. Done-failed is the honest closure for an attempt that did not work — I trained for a half-marathon, ran 16km in training, got injured, did not finish. That item is closed. The list reflects reality.
why the structure works
Three structural features make the working list compound where bucket lists do not.
The list is live. It updates. Every quarter or so I sit down and review it. Status fields change. New items get added. Old items get removed when they no longer fit. The list reflects what I am actually doing, not who I wanted to be when I wrote it.
Items are sized. A bucket-list item like “travel” is unactionable. A working-list item like “spend 3 weeks in Japan in 2024” is actionable. Sizing forces the item to be the level of concreteness where it can be planned, scheduled, and executed.
Failures count. When an item gets marked done-failed, I learn something specific about my own limits. The half-marathon failure told me I am structurally bad at long-distance running. That information shaped the next decade of how I exercise. The bucket list version of the same attempt would have stayed open forever, an unmarked aspiration.
what compounds
Across 13 years of running this list, three compounding effects.
The honest tracking of what I actually did vs what I wanted to do. The gap between the two is the most useful piece of information about myself. The gap shrinks over time because the list itself trains me to be more accurate about what I will actually do. The me of 2020 has a much smaller gap than the me of 2010.
The accumulation of done items. Year on year, the done items pile up. Not flashy items — many of them are mundane (open-source a library, give a talk, finish a course). Cumulatively, they form a portfolio of evidence that the working-list method produces output. The bucket list method, by comparison, produces aspirations.
The accumulation of done-failed items. Knowing what I have tried and failed at is more valuable than I expected. It eliminates whole categories of future regret. I will not, at 70, wonder if I should have tried the half-marathon. I did. I cannot run them. That regret has been pre-spent.
the public version
In 2026 I made the working list public on my website at /mission. Forty items, with status fields. Updated when reality catches up.
Making it public changed two things. First, items I was vaguely tracking became items I had to articulate clearly enough for a reader to understand. The articulation killed maybe a third of the list — items I could not defend in plain language went into the deferred pile or got reworded into something I actually meant. Second, the accountability shifted. Readers email me asking about progress on specific items. The questions are useful even when they are uncomfortable.
Most people will never publish their working list. That is fine. The discipline of writing it down somewhere external — a Notion doc, a text file, a private repo — is the part that matters. The public version is optional. The written version is not.
the close
If you have a bucket list, that is fine. But also keep a working list. The two are different documents and serve different purposes. The bucket list expresses who you are. The working list determines what you will actually do.
Most people only have the first. The compounding only happens with the second.
My list has 40 items right now. It will have roughly 40 items next year too. Some will have moved from in-progress to done. Some will have moved from todo to done-failed. Some new ones will appear. The list itself is the trajectory.
Bucket lists are static. Working lists are alive. Pick the one that compounds.