I watched myself do it again last Tuesday. I caught a fix worth remembering, opened a note, and then spent the next ninety seconds deciding which folder it belonged in, what to tag it, and whether it was really a "task" or a "reference." Having the thought took about one second. Filing it took ninety. By the time I was done, the fix I had actually wanted to write down had gone soft at the edges, and I was no longer sure I had it right.
That ninety seconds is the thing I want to argue about. Not because it is long, but because of when it lands: at the exact instant I can least afford it.
Here is the claim, and I will spend the rest of the post earning it. Capture and curation are two different jobs with opposite requirements, and almost every note tool I have used quietly asks me to run both at once. That is the mistake. Do them together and you get the worst of each: capture slow enough that thoughts slip away, and curation done in a one-second window with none of the context that makes it worth doing.
What the tools actually ask of you
Open most capture flows and count the decisions before the thought is safe. Pick a notebook. Choose a project. Add tags. Set a type. Maybe a due date. Each of those is defensible on its own. Together they turn "write this down" into a small triage meeting, and they schedule that meeting for the one moment you are guaranteed to be busy: mid-thought, mid-task, mid-something.
The thing the apps get wrong is that they treat the tags and the folders as free, as if slotting a note into structure were part of writing it. It is not. It is a second, heavier job wearing the first job's clothes. And it is a job you are catastrophically bad at right now, because you are holding a thought in working memory and every keystroke spent on metadata is a keystroke not spent holding it.
I have measured the cost of interruptions like this on myself before, and it is not linear. A fifteen-second interruption that cost me forty minutes of re-entry taught me that the price of a context switch is not the switch, it is the climb back. Organizing at capture time is a context switch you volunteer for, on purpose, every single time you have an idea.
Why does doing both at once cost double?
Because you are running curation blind.
Curation is the act of deciding where a thought belongs and what it connects to. That decision is only good when you have information: what else is in the vault, what this relates to, whether it is still true next week. At capture time you have exactly none of that. You are deciding a note's permanent address at the one moment you know the least about it. So you either guess, and build a structure full of confident wrong guesses, or you stall for ninety seconds trying to guess well, and lose the thought you came to save.
There is a reason a thought you cannot capture in about a second is already gone. The window is that short. Anything you bolt onto the front of capture is spending a budget that was never yours to spend.
So the tax is double. You pay it once in lost thoughts, because capture got slow. You pay it again in a junk taxonomy, because curation got done at the worst possible time by the least informed version of you.
The split I actually run
Two jobs, two modes, and I keep them physically apart so I cannot cheat.
| Capture | Curation | |
|---|---|---|
| When | The instant a thought lands | Once a week, deliberately |
| Where | Phone, wherever I am | Laptop, at a desk |
| Time budget | About one second | Ten to fifteen quiet minutes |
| Mindset | Dumb, fast, no judgment | Slow, full of judgment |
| Allowed actions | One line, append it, done | Read, connect, rename, discard |
| What kills it | Any decision at all | Skipping it for a month |
Capture is append-only. One line, one action, timestamped by the world instead of by me, no folder, no tag, no type. The whole point of the tool I build for myself is that it opens in about a quarter of a second and turns a line into a saved, sent record before I have finished the thought. There is no place to put a tag because I removed the place to put a tag. That absence is a feature.
Curation is a separate act I do later, on a different device, on purpose. Once a week I sit down at the laptop, read the week's raw lines in a plain markdown vault, and decide what graduates: what becomes its own note, what links to what, what was noise and gets deleted without ceremony. Now I have context. Now the judgment is worth something, because I am reading a thought next to the six thoughts that arrived after it.
The device split does real work. If capture and curation lived in the same app on the same screen, I would drift into tidying at capture time out of sheer proximity. Making curation happen somewhere else raises the friction just enough that I stop trying to do it in the checkout line.
Where this breaks, and who should ignore me
I owe you the cases where I am wrong, because a rant that only flatters its own thesis is just a mood.
Dumb capture wins for a solo dev with a curation habit. It stops winning the moment your inbox is shared. If an untriaged item blocks a teammate, then "I'll sort it Sunday" is not discipline, it is a dropped handoff, and some structure at capture time is the price of not being the bottleneck. Team queues and personal inboxes are different animals, and I am only defending the personal one.
It also breaks if you never actually curate. An append-only inbox you never revisit is not a system, it is a landfill with timestamps. The whole split is load-bearing on the back half. If you know yourself well enough to know the Sunday pass will not happen, then a little structure at capture time is a hedge against your own neglect, and that is a fair trade. I am not making it, but I see it.
And there is a volume line somewhere. Capture a handful of lines a day and an unstructured inbox stays scannable. Capture two hundred and it does not, and you will want some coarse bucket at the door just to keep the Sunday pass finishable. I have not hit that line as a team of one. If you have, your mileage is honestly different, not wrongly different.
A couple of questions I get
Isn't a dumb inbox just inbox-zero with extra steps? No, and the difference is the timestamp. Inbox-zero is a pressure to clear. The dated line has no pressure at all, because nothing is overdue and nothing is unfiled, it is just a log. I am not racing a counter to zero. I am reading a week.
What if the one-second capture saves garbage? It saves some, and I delete it on Sunday in about the time it would have taken to tag it on Tuesday. The asymmetry is the point: deletion is cheap and late and well-informed; tagging is expensive and early and blind. I would rather throw out ten cheap lines than misfile one expensive one.
The one line I want from you
I am curious where other people draw the exact border, because I suspect mine is slightly wrong and I cannot see which side.
So, concretely: what is the one thing you let yourself do to a note at the moment you capture it, and what is the one thing you had to forbid yourself from doing because it kept eating the thought? A single allowed move and a single banned one. I want to see where the line lands for work that isn't mine.
Simple Memo is an iOS app I build by myself: type one line and it is a sent email before your thumb leaves the screen, with nowhere to file it and nothing to tag. I post here every few days about the mechanics of doing this solo. You can find it on the App Store.
Top comments (0)