Everything You Quit Was Trying to Tell You Something

I have a folder on my laptop I haven't opened in about a year. It's called — and I'm a little embarrassed to admit this — "The Vault." Inside are seventeen unfinished projects. A novel I started in 2019 and abandoned at chapter four. A podcast concept with a full production plan and zero recorded episodes. A newsletter series I wrote three installments of before going completely silent. A documentary outline. Two short films in various states of incompletion. A personal essay that I rewrote eleven times before deciding it wasn't ready, and then never touched again.

For a long time, I thought of that folder as a museum of my failures. Every time I stumbled across it, I'd feel a little stab of guilt — all that work, all those intentions, all that wasted time.

But I've been sitting with a different idea lately. What if the work in that folder isn't evidence of failure? What if it's evidence of something much more useful?

The Myth of the Finished Thing

Our culture has a deep, almost religious attachment to completion. We celebrate launches, ship dates, publications, premieres. We talk about finishing as the goal, the proof, the thing that makes the effort real. Unfinished work is treated like a personal shortcoming — a sign that you lack follow-through, discipline, or commitment.

But that framework only makes sense if the purpose of creative work is to produce a finished object. And I'm not sure that's actually true.

What if the purpose of creative work — at least some of it — is to figure out what you actually think, want, and believe? What if some projects aren't meant to be finished? What if they're meant to be experienced, to teach you something, and then set down when the lesson is complete?

I know that sounds like a convenient excuse for quitting. Bear with me.

Three Kinds of Abandoned Projects

When I finally opened The Vault and went through everything honestly, I started to notice patterns. Not everything I'd abandoned was abandoned for the same reason. And the reason matters a lot.

The first kind: projects that were never actually mine. These are the ideas that came from external pressure — something I thought I should do, or something I started because it seemed like the kind of thing a person in my position ought to be working on. The podcast concept fell squarely into this category. I didn't genuinely want to make a podcast. I wanted to want to make a podcast, because it seemed like the obvious next step. There's a difference, and I ignored it.

These projects die early and they die hard, and they should. They're your instincts doing their job. The fact that I couldn't make myself care enough to record a single episode wasn't a discipline problem. It was information.

The second kind: projects that were real but premature. These are the ideas that were genuinely yours — you had real energy for them, real investment — but you didn't yet have the skills, perspective, or life experience to execute them the way they deserved. The novel I abandoned at chapter four lives here. I had something true I was trying to say. I just didn't know how to say it yet. The abandonment wasn't a failure of commitment. It was an honest reckoning with my own limitations at that moment in time.

These are the projects worth revisiting. Not all of them, and not right away — but they deserve a second look every few years, because you change, and sometimes the project you couldn't crack at twenty-seven becomes the thing you were born to make at thirty-five.

The third kind: projects that completed themselves before they were technically finished. This is the strangest category, but I think it's the most interesting one. Sometimes a project teaches you exactly what it was there to teach you, and then there's nothing left to do with it — even if it's technically unfinished. The eleven-draft essay that I never published? I think I understand now that I wasn't writing it to publish it. I was writing it to understand something that happened to me. Once I understood it, the essay didn't need to exist anymore.

These projects look like failures from the outside. From the inside, they're complete.

What the Pattern Reveals

Here's what surprised me when I looked at The Vault honestly: my abandoned projects, taken together, told a much clearer story about my creative evolution than my finished work did.

The things I quit revealed where my real interests were (and where they weren't). They showed me which mediums actually fit the way I think and which ones I was forcing. They mapped my shifting priorities over time — what mattered to me in 2019 is genuinely different from what matters now, and the abandoned work from that period reflects that honestly.

Finished work, by contrast, often reflects commitment more than it reflects truth. Sometimes I've finished things out of stubbornness, or because I'd already announced them publicly, or because I was afraid of what it would mean to stop. Those finished projects don't always represent my best thinking. They represent my best follow-through.

I'm not arguing against follow-through. But I am arguing that it's one value among several, and we've elevated it so far above the others that we've lost the ability to read the information that incomplete work is trying to give us.

Knowing When to Kill It vs. When to Come Back

This is the practical question, and I'll be honest — there's no clean formula. But here are the things I ask myself now when I'm sitting with something unfinished:

Why did I stop? Was it fear, boredom, external circumstances, a skills gap, or a genuine loss of belief in the project? These have different implications.

Has anything changed? Sometimes a project that was wrong before is right now — because you've grown, or the world has shifted, or you finally have the collaborator or resource or life experience it needed.

Does thinking about it still feel like anything? Even dread is a signal. Complete indifference is the real sign that something is finished.

Was it mine to begin with? If I'm honest, was I doing this for me, or was I doing it for someone else's version of who I should be?

The Breadcrumbs

Look, I'm not going to pretend there isn't real grief in abandoned work. There is. You put time and hope and energy into something, and then it doesn't become what you thought it would be. That's a real loss.

But the breadcrumbs are there if you're willing to follow them. Every project you quit — every false start, every abandoned chapter, every half-built thing gathering digital dust — was pointing you somewhere. Toward what you actually want. Away from what you don't. Deeper into who you're becoming as a creator.

The graveyard isn't a monument to your failures. It's a map.

Open the folder.