Are you a starter or a finisher?

Most people who struggle to finish projects aren't lazy. They're caught in a loop: start, get excited, hit friction, start something new. Each new beginning feels like momentum. But six months later, nothing is done. The problem isn't motivation. It's that we never learned which assumptions we were actually testing.

Why does starting feel so much better than finishing?

New projects feel like momentum. Finishing old ones feels like grinding.

That's not a character flaw. It's how the brain works. Starting a new thing creates energy. Continuing a hard thing requires something else entirely.

So we start another one. Not because we gave up on the old one. But because the new one is still in the phase where anything feels possible.

What actually happens when we abandon a project?

We usually tell ourselves we're being strategic. Cutting our losses. Moving on.

But what we're really doing is skipping the part where we'd find out if the idea worked.

You launch three projects in parallel. None are finished six months later. Each one got exciting, then complicated, then deprioritized in favor of the next new thing. The pattern isn't bad luck. It's a system — just not an intentional one.

Without a system that makes completion the default, novelty always wins.

Why does the loop keep repeating?

The first time we build something, we often do finish. We have hope. We want to see the result.

But then the results don't come. Or they come slowly. Or differently than expected. So we assume we need to try something new.

We start something new and shiny from scratch. But already before we finish, we sense it's probably not working either. So we stop earlier. And earlier. And earlier. Until we've trained ourselves to stop right after the start.

I recognize this. I've done this. Not because the ideas were bad. But because I didn't know what I was actually testing.

What's the real reason we keep switching?

We often don't know what will work. And more importantly, we don't know why.

We don't capture our implicit assumptions. What we think the mechanism is. Why this particular approach should produce results. So when something doesn't work, we don't know if the idea failed or the implementation failed.

So we discard everything and start over. When often we should improve the implementation and keep the mechanism.

The difference between a starter and a finisher isn't drive. It's whether you know what you're testing and what success would actually look like.

What this comes down to

The start-and-abandon loop happens because we're treating every project like a lottery ticket instead of an experiment. We hope it works, and when it doesn't, we buy a new ticket. What breaks the loop is knowing which assumption you're testing before you start, and staying long enough to find out whether it holds. Finishing isn't about grinding through boredom. It's about having enough clarity on what you're learning that seeing it through actually means something.

The last thing you abandoned probably wasn't a failed idea. It was an incomplete test.

PS: A useful question before starting the next one: what would this need to show me in 60 days for me to know it's working? If you can't answer that, the project probably isn't ready to start.

Frequently asked questions

Why do I keep starting new projects instead of finishing the ones I have? Because starting creates energy and finishing requires discipline through friction. Without a clear picture of what you're testing and what completion means, the new idea will always feel more promising than the stuck one.

Is being a starter instead of a finisher a personality thing? Partly, but mostly it's a system thing. People who consistently finish don't necessarily have more willpower. They have clearer criteria for what done looks like and a process that makes stopping harder than continuing.

How do you break the habit of abandoning projects mid-way? The most practical fix is to define what you're testing before you start — not what you hope will happen, but what assumption you're trying to validate. When you know what you're testing, you can actually read the result and decide consciously whether to continue.

What's the difference between quitting too early and cutting your losses? Cutting losses makes sense when you've learned what you needed to learn. Quitting too early is stopping before you have enough information to judge. The question isn't "is this hard?" It's "do I know yet whether the core assumption holds?"

Why does everything feel like it's not working before it's finished? Because it usually is harder in the middle than at the start. The middle is where the initial energy runs out and the results aren't visible yet. Most people interpret that as a signal to stop. It's actually the phase where finishing has the most value.

How do you decide which projects are actually worth finishing? Before you start: write down the one assumption the project depends on and what evidence would tell you it's true. If you can't articulate that, the project probably isn't defined well enough to finish productively.