For a long time I optimized my note-taking. I changed apps every six months. I switched from tags to backlinks to graph views and back. I read books about Zettelkasten. I had three different ways of marking confidence in a claim.

I produced almost nothing.

The pattern was simple in hindsight: each "improvement" was a way to put off finishing the actual work. As long as the input system needed tuning, I had a legitimate-sounding excuse for not shipping. The output queue grew. The notes stayed pristine.

The break came from setting a stupid little rule: anything I started in posts/ got shipped or killed within four weeks. No drafts living indefinitely. The first month was hard — I killed three pieces I'd been carrying for a year. By month three, the queue had cleared.

What I learned:

1. The "input system" was hiding the real bottleneck, which was finishing.
2. Killing a draft is information, not failure. The draft didn't survive contact with the deadline because the idea wasn't ready. Better to know.
3. Tools you've used for two years are good enough. New tools don't write the essay.

This is the finishing rule essay version, with more context.

The deeper point is that production has a different shape than consumption. Reading more, taking better notes, building better tools — these are all consumption-shaped activities. Finishing is production. They are different muscles. Optimizing the first never builds the second.

The opposite of finishing isn't "still working on it". The opposite is making it indefinitely fixable.

Related: Why I distrust productivity systems, Quitting tools that didn't help me write.

Comments

Comments are moderated. No email, no IP collection.