Why You Start Things and Never Finish Them

You have three or four things that are eighty percent done. A document that needs one more pass. A side project that got as far as working and never got as far as finished. Something you told people about six months ago and quietly hope they have forgotten. Why do I never finish anything, you ask, usually at eleven at night.

And you have probably concluded that the problem is you. That other people were issued a reserve of discipline you got a smaller share of.

That diagnosis is wrong, which is why every fix built on it fails. Discipline advice assumes finishing is the same activity as starting, performed with more effort. Finishing is a separate activity with its own failure modes, and almost none of them have anything to do with willpower.

Starting is a decision made under optimism. You have a clear picture, you have had no contact with reality yet, and the whole thing exists in your head in its best possible version. Finishing is a long stretch of work after the interesting part is over, made up almost entirely of the tasks you postponed because they were dull or unresolved.

From the outside those two look identical. Both are called working on it. That is most of the confusion.

Here is what is actually happening, and what follows from each part of it.

The Interesting Part Ends Before the Project Does

Most people are motivated by a problem. The problem is the interesting bit: how would this work, could it be done, what would it look like if it existed. And the problem gets solved early, usually somewhere in the first fifth of the work.

After that it is execution. Nobody is intrinsically motivated by execution. The thinking is over and what remains is transcription, formatting, testing, chasing the one person who has not replied, and the fourteen small decisions you left open because they were boring.

This is why the same person can start brilliantly and finish nothing. It is perfectly consistent behaviour. They are motivated by one specific thing, and that thing runs out with four fifths of the work still in front of them.

The planning fallacy sits on top of this and makes it worse. In the 1994 study by Buehler, Griffin and Ross on why people underestimate their task completion times, psychology students predicted they would hand in their theses in an average of 33.9 days. The average reality was 55.5 days, and fewer than a third finished by the date they had picked themselves. Asked how long it would take if everything went as well as it possibly could, they said 27.4 days, and roughly one in nine managed that.

So you commit to the project on the strength of a timeline that assumes the dull part does not exist.

You Never Defined Done

This is the most common cause of unfinished work and the easiest thing on this list to fix. It stays invisible because it looks like a detail.

Ask someone what finished looks like for the thing they have been carrying around for a year and you usually get a direction rather than a state. Better. Cleaner. Ready. Properly sorted out. None of those are conditions a project can satisfy. If there is no state the work can reach that counts as done, every version is a draft, permanently. There is nothing to fail at, because there is nothing to hit.

An undefined target does something quieter as well. It lets the scope drift upward every time you return to the work, because each time you come back you are slightly better than you were and can see improvements the earlier version could not. The thing gets further from done the more you work on it.

This is the same failure that turns any goal stated as a direction into a treadmill. It is worth reading the case for actually answering how much money is enough alongside this, because the structure is identical. More is not a target. A number you have never written down cannot be reached, only approached.

So write one sentence, before you start, describing the state at which the thing is over.

Finishing Forces a Verdict

While it is unfinished, it is still potentially good.

That sentence is doing more work in your life than you would like. A half-built thing sits in a protected state where it could still turn out to be the best thing you have ever made. Shipping converts that possibility into a result, and a result can be judged, ignored, or found perfectly ordinary.

Almost everyone does this. It is not a character flaw and it does not need a dramatic explanation. The instinct to protect something unproven is sensible in most parts of life. It happens to be fatal here, because the protection only lasts while the work stays incomplete, and the price of keeping it is that the thing never exists.

The tell is fairly specific. You feel fine about the project right up until the last stretch, and then the final ten percent starts generating an unusual volume of reasons to wait. Some research you should do first. A better approach worth trying. A month that is not quite the right month to put it out.

The New Idea Arrives Exactly on Schedule

Notice when the brilliant new idea shows up.

It almost never arrives at the start of a project, when you have spare capacity and enthusiasm to burn. It arrives about two thirds of the way through the current one, at the precise moment the current one stops being interesting.

The new idea feels like inspiration because it has every quality the current project has lost: clarity, novelty, an absence of known obstacles, and the particular pleasure of an unsolved problem. Of course it feels better. It is at the stage where everything feels better.

The timing is the tell. An idea that arrives the week you get bored is usually avoidance in better clothes. The idea might well be good. Its arrival time is still the thing to distrust.

You Already Got What You Came For

Conventional sunk cost says people stay with bad projects because they have invested too much to walk away. Unfinished personal projects tend to run the other way.

You started because you wanted to understand something. Could I build this. Would this argument hold up. What would it actually take. By the time the thing is two thirds built, you know. The understanding has been extracted, and it stays extracted whatever you do next.

What remains is pure cost with no learning in it. That is a genuinely rational reason to stop, which is why so many abandonments feel oddly guilt-free in the moment and terrible six months later.

The catch is that the value you took is private. You cannot show anyone the understanding. The only version of the work that other people can use is the finished one, so the part you skipped is the entire part that had any value to anybody else.

Parallel Projects Are How Nothing Gets Finished

Every project you have running is individually defensible. That is the trap. Nobody adds a fifth project by deciding to become scattered. They add it because it is good, or timely, or small, or because somebody asked.

Taken together, parallel projects guarantee that nothing gets the uninterrupted stretch finishing requires. The final phase of anything is the phase that most needs continuous attention, because it consists of loose ends, and loose ends have to be held in your head all at once. Split that across five things and each one restarts from cold every time you come back to it.

There is a supply problem underneath this too. Starting has never been cheaper. You can have a draft, a prototype or a working demonstration in an afternoon. The generation step has become enormously faster while the checking step has not, which is how AI can make work feel quicker while the net time goes up. The same asymmetry governs your project list. Anything that lowers the cost of starting without lowering the cost of finishing will increase the number of unfinished things you own.

Why Do I Never Finish Anything? What Actually Fixes It

Each mechanism above points at a specific fix. None of them involve trying harder.

• Write the definition of done before you start. One sentence, including what you are deliberately leaving out. “Done is a two thousand word piece with one worked example, published on the site, with a plain text version and nothing else.” The exclusions carry as much weight as the inclusions, because scope drift always arrives as additions that each look reasonable on their own.
• Cut scope rather than extend time. When a project overruns, the instinct is to give it more weeks. Give it less work instead. A finished small thing beats an abandoned large one on every measure, including what you learn, because everything you need to know about finishing lives in the last twenty percent and an abandoned project never takes you there.
• Run one thing to completion before the next. This is the least popular item and the one that changes the most. Two projects is often survivable. Five is a system that produces unfinished work by design.
• Keep a written list of the new ideas. Write each one down with the date and carry on. The list separates having an idea from acting on it, which is the whole job. If it still looks good when the current thing is finished, it was real. Most of them will not survive the wait, and that tells you what they were.
• Design the boring stretch to be shorter. This is the one people skip, and it is the highest-return decision available. The length of the last twenty percent is set at the design stage, before any of the fun part happens. The format you choose, the scope you can hold in your head, whether publishing takes an hour or a fortnight: all decided early, while you are still optimistic, and all of it determines how much dull work is waiting at the end. Build the ending you are actually willing to do.

Notice that four of those five happen before the work starts. Finishing is mostly decided in advance, which is why trying to rescue a stalled project with effort so rarely works. The conditions were set months ago.

Some Things Should Be Abandoned on Purpose

Not everything deserves to be finished. Some projects were built on an assumption that turned out to be wrong, and the correct response to that is to stop.

But drifting away from a project and deciding to stop it are different acts with the same visible outcome, and only one of them keeps charging you afterwards.

Abandoning on purpose looks like this. You write down what the project was for, what you learned, why it is stopping, and what would have to change for you to pick it up again. Three or four sentences. Then it is closed, and it stops occupying the part of your attention that keeps a running inventory of unfinished things.

Drifting looks like nothing at all, which is exactly the problem. The project stays technically alive, so it collects a small tax every time you remember it exists.

Most people carrying a bad feeling about unfinished work are not carrying it about the work. They are carrying it about the ambiguity. Four projects that were formally closed with a written reason feel entirely different from four projects in an undefined state, even though precisely the same amount of work went unfinished in both cases.

So the next time the question is why do I never finish anything, go through the list. Some of them get a definition of done and a date. Some of them get a closing note. What none of them should get is another year of being neither.

Why do I never finish anything? Because finishing is a skill with unglamorous conditions: a defined target, a scope small enough to reach it, and one thing at a time for long enough to get there. Nobody has a natural aptitude for the last twenty percent. The people who finish things have simply arranged the work so that the last twenty percent is short enough to survive.