The Psychology of Done

I have a folder on my computer called "Graveyard." It contains 47 abandoned projects. Some are just empty folders with ambitious names. Others have hundreds of lines of code, designs half-implemented, dreams half-realized. They all have one thing in common: I never finished them.

Starting is intoxicating. The blank canvas, the new repository, the first lines of code — everything is possibility. The project exists in a perfect state, unsullied by the realities of implementation. In your mind, it's already successful, already beautiful, already complete.

Then comes the middle. The messy, grinding, doubt-filled middle. And that's where most projects go to die.

The Valley of Despair

Every project has a phase where the initial excitement wears off but the end is still far away. I call it the Valley of Despair. The code is messy. The architecture needs refactoring. There are bugs you don't understand and features you don't know how to implement.

This is where the siren song of new projects becomes loudest. "Start fresh," it whispers. "This time will be different. This time you'll do it right." And so you abandon the current project for a new one, trading the valley of despair for the mountaintop of possibility.

But the cycle repeats. Every project has a valley. The only way out is through.

The Shame of the Unfinished

There's a particular shame to unfinished projects. It's not just wasted time; it's broken promises. Promises to yourself, mostly. "This time I'll finish it." "This time I'll see it through." Each abandoned project is evidence of your lack of discipline, your inability to commit, your fear of completion.

Or at least, that's the story we tell ourselves. The truth is more complicated. Some projects should be abandoned. Some ideas don't survive contact with reality. Knowing when to quit is as important as knowing when to persist.

But most of my abandoned projects weren't abandoned because they were bad ideas. They were abandoned because finishing is hard. Because the last 20% takes 80% of the effort. Because polishing, testing, documenting — the unglamorous work of completion — is boring compared to the thrill of creation.

Defining "Done"

One problem with finishing is that we rarely define what "finished" means. Is a project finished when it works? When it's deployed? When it's perfect? That last one is a trap. Perfect is the enemy of done. If perfection is the standard, nothing ever finishes.

I've started defining "done" explicitly at the start of projects. What does version 1.0 look like? What are the minimum features? What can wait for later? This isn't about limiting ambition; it's about creating achievable milestones.

Done is a scope decision. It's saying: "This is enough for now." It's accepting that good enough is, in fact, good enough.

The Power of Ugly Finished

Finished is better than perfect. An ugly, buggy, incomplete thing that exists is infinitely more valuable than a beautiful thing that doesn't. You can iterate on something that exists. You can learn from something that exists. You can't do anything with something that only exists in your head.

I have a personal rule now: ship before you're ready. Not recklessly — I still test, still review, still make sure things work. But I don't wait for perfect. I don't wait until every feature is implemented. I ship when it's useful, even if it's ugly.

The first version of this website was embarrassing. The design was basic, the content was sparse, and there were bugs I didn't discover until weeks later. But it was live. It was real. And that made all the difference.

The Discipline of Completion

Finishing is a skill. Like any skill, it can be developed through practice. But it's a peculiar kind of practice because each project is different. You can't just repeat the same motions. You have to apply the principles of completion to ever-changing circumstances.

What are those principles? For me, they're:

Define done upfront. Know what you're aiming for before you start. Change it if you need to, but have a target.

Work in public. Tell people what you're building. Create accountability. The fear of public failure is a powerful motivator.

Embrace the grind. The middle is supposed to be hard. Expect it. Don't interpret difficulty as a sign to quit.

Set deadlines. Even arbitrary ones. Constraints force decisions. Without a deadline, you can polish forever.

Celebrate completion. Actually finish, actually celebrate. Reflect on what you learned. Then start the next thing.

The Projects That Made It

Looking at the projects I actually finished, I notice patterns. They're usually smaller than the ones I abandoned. They have clearer definitions of done. I worked on them consistently rather than in bursts. And most importantly, I shipped them before I felt ready.

None of my finished projects are perfect. Most of them have issues I still want to fix, features I still want to add. But they're real. They exist in the world. People use them, or at least could if they wanted to.

That existence is what separates the finishers from the perpetual starters. It's not talent. It's not even discipline, really. It's the willingness to accept imperfection and ship anyway.

Finishing as Practice

I've started treating finishing as a practice in itself. Not just a means to an end, but a skill worth developing. Each completed project makes the next one easier. You build confidence. You build processes. You build a portfolio of evidence that you can, in fact, finish things.

That's why I now prioritize finishing over starting. I'd rather complete one project than start ten. I'd have a small portfolio of finished work than a large graveyard of possibilities.

The projects in my Graveyard folder aren't failures. They're lessons. Each one taught me something about what I want to build, how I want to work, who I want to become. But lessons without application are just information. The goal is to apply what I've learned.

So here's my commitment: finish before starting. Complete what's in progress before beginning something new. Ship the imperfect thing rather than chasing the perfect thing that doesn't exist.

Starting is easy. Everyone starts. Finishing is rare. Finishing is valuable. Finishing is everything.

What will you finish today?