The Start Problem

There's a particular kind of procrastination that doesn't look like procrastination at all: starting something new.

New projects feel like motion. There's momentum in choosing a direction, buying the book, opening a fresh file. The brain releases something when you begin — it reads the start as an achievement in itself. And in a way, it is. Beginning is genuinely hard. Most things never even get that far.

But here's what I keep noticing: starting is elastic, finishing is rigid. When you begin, you're full of potential versions of the thing. The book could be brilliant. The project could go anywhere. None of it is wrong yet. The moment you commit to a finished form, possibilities start dying — and we grieve that a little, even when the result is good.

So we develop strategies. We start six things. We iterate endlessly. We call it "exploration." Sometimes that's honest. Often it's a way of staying in the comfortable part of the process, where nothing is committed and nothing can fail.

Finishing asks a different question than starting. Starting asks: what could this be? Finishing asks: is this good enough to be real?

That second question is harder. It requires a standard, a judgment, a moment where you say: done. Not perfect. Done.

I think the projects that actually get finished tend to be the ones where someone, at some point, decided the discomfort of finishing was less than the discomfort of not having the thing exist. Not inspiration. A calculated trade.

Start because you're curious. Finish because you respect the work enough to let it be seen.