Not Every Idea Deserves a Finish Line: What Killing Projects Taught Me About Creative Judgment

Somewhere on an old hard drive, there's a podcast I recorded twelve episodes of and never released. There's a newsletter I designed a whole brand around, wrote four issues for, and then quietly let expire. There's a short film treatment I spent three weekends outlining before I finally admitted I didn't actually want to make it — I just wanted to have made it.

For a long time, I thought that graveyard was evidence of failure. Like every abandoned project was proof that I lacked discipline, or follow-through, or whatever quality separates the people who finish things from the people who don't.

Then I started paying attention to what I was actually learning every time I walked away.

The Podcast That Wasn't Mine to Make

The podcast idea made sense on paper. I had the topic locked, the format planned, a friend lined up to help with editing. I recorded the first episode and felt... fine. I recorded the second and felt the same kind of fine. By episode four I realized I was making something I would listen to, not something I needed to make.

That's a distinction that took me way too long to understand.

There's a difference between ideas that excite you because they seem like good ideas, and ideas that excite you because something inside you genuinely has to get them out. The podcast fell into the first category. It was a smart concept. It probably would have found an audience. But it wasn't coming from anywhere real in me, and I could feel that every single time I sat down to record.

I shelved it after episode twelve. I never published a single one.

And honestly? Best call I ever made.

What 'Sunk Cost' Looks Like When It's Your Own Creativity

Here's what nobody tells you about creative work: the sunk cost fallacy hits differently when the thing you've already invested isn't money — it's your identity.

When you've told people about a project, when you've posted about it, when it's become part of how others see you, walking away feels like a public admission of something. Quitting. Flaking. Not being someone who finishes what they start.

I've pushed through projects I should have dropped specifically because I'd announced them. I published things I wasn't proud of because I felt obligated by my own earlier excitement. And every single time, I could feel the difference between work that came from genuine creative necessity and work that came from not wanting to look inconsistent.

The newsletter was like that. I launched it with real enthusiasm, got a decent subscriber count right out of the gate, and then slowly realized the format was wrong for how I actually think. I'm not a newsletter person. I tried to become one because newsletters were having a moment, and I spent months producing something that felt like a costume I couldn't quite zip up all the way.

Killing it wasn't failure. Killing it was finally being honest.

The Skill Nobody Talks About Developing

Every conversation about creative growth focuses on output: post more, finish more, ship more. And yeah, there's real value in learning to push through the messy middle of a project instead of bailing the second it gets hard.

But there's a completely separate skill that I think matters just as much, and almost nobody talks about it: learning to tell the difference between this is hard and this is wrong.

Hard projects feel like resistance. They feel like friction, like you're pushing something uphill, but the hill is real and the destination is worth it.

Wrong projects feel like performance. Like you're doing the motions of creating without anything actually driving the work forward. The effort doesn't build toward anything — it just accumulates.

I got better at recognizing that feeling after I stopped treating every abandoned project as a personal flaw. Once I gave myself permission to kill things without guilt, I started noticing patterns. What did the work I abandoned have in common? What did the work I couldn't stop making look like?

That information is genuinely useful. It's not defeat — it's data.

The Short Film I Was Never Going to Make

The treatment I mentioned at the top — three weekends of outlining — that one stings a little differently because I knew pretty early it wasn't right. I kept going anyway because I liked the version of myself who was developing a short film.

That's the sneaky one. Sometimes you're not in love with the project. You're in love with the identity the project lets you perform.

When I finally admitted that, I felt embarrassed for about a day. Then I felt free. I stopped pretending I was a filmmaker for a season and went back to the formats that actually fit how my brain works. Everything I made in the months after that felt more honest than anything I'd touched in a while.

What the Graveyard Actually Means

I look at that hard drive differently now. The podcast, the newsletter, the film treatment, the three other things I haven't even mentioned — they're not evidence of wasted time. They're proof that I was paying attention.

Every project I killed taught me something I couldn't have learned any other way. The podcast taught me the difference between wanting to create and needing to. The newsletter taught me that platform trends are a terrible reason to start something. The film treatment taught me to watch out for identity-performance disguised as genuine creative drive.

Mature creators — and I say this as someone who's still very much in the process of becoming one — don't publish everything. They develop judgment. They learn to feel the difference between the work that's theirs to make and the work that just seemed like a good idea at the time.

Saying 'this one's not it' isn't giving up. It's one of the most sophisticated creative decisions you can make.

The finish line isn't the point. The right work is the point. And sometimes the bravest thing you can do is refuse to cross the wrong one.