Somewhere in your life there is a graveyard. The course that stops at forty percent. The novel with three chapters. The half-learned language, the app with the dead streak, the business idea with a name and no customers.
The business idea is the one most likely to still be there in five years, and it stalls for reasons of its own.
The usual verdict is discipline, and it does not survive contact with the evidence. You finish things constantly. Work projects ship. Other people's deadlines get met. The pattern is specific: what dies is your own projects, in their middles, quietly.
That specificity is good news, because it means the cause is structural rather than personal. What follows: why starting and finishing are different skills, what the middle of a project actually does to you, how to tell an abandoned project from a finished decision, and the mechanic that gets things over the line.
Starting and finishing are different activities, and you are good at the fun one
A new project pays you immediately. An old one asks you to pay.
Starting something is genuinely rewarding. There is a vision, a plan taking shape, supplies to buy, a version of you on the far side of it that you like. All of that arrives on day one, free, and none of it requires the project to go anywhere. Planning is imagination wearing a productivity costume, and imagination is a pleasure.
Finishing is a different job. By the end, every interesting decision has been made, what is left is the unglamorous remainder, and the vision has been replaced by a real thing with real flaws. The people who finish are not people who feel differently about that trade. They are people who stopped relying on feelings to carry the middle.
So the graveyard is not evidence that you lack follow-through in general. It is evidence that you have been funding projects entirely out of the starting excitement, and that currency always runs out.
The middle is designed to lose you
Novelty is gone, results have not arrived, and that gap is where projects die.
Seth Godin gave the stretch a name in his short book The Dip: the long middle where the early thrill has worn off and the payoff is still out of sight. The shape matters more than the name. Early on, progress is loud, since going from nothing to something feels enormous. In the middle, progress goes quiet. Chapter seven does not feel different from chapter six. Week nine of training looks a lot like week eight.
Nothing is wrong when this happens. The project has simply stopped generating its own motivation, which was always going to happen, and was never a sign about the project or about you.
Readers of the procrastination pieces have seen this mechanism at a smaller scale: goals tend to die in week three, the first week that has no built-in event in it. The middle of a project is week three stretched over months, and it responds to the same fix, which is structure that does not depend on enthusiasm.
Worth knowing: the middle is also when a new project looks most attractive, because a new project offers the day-one rewards your current one has stopped paying. That is not a coincidence and it is not a signal. It is the same gap, seen from the other side.
You planned the project, not the boring weeks
Plans get written on day one by the most optimistic person you ever are.
There is a name for this in the research literature: the planning fallacy, described by Daniel Kahneman and Amos Tversky, the tendency to plan around the best case even when your own history argues otherwise. Day-one plans assume the energy of day one continues indefinitely. They contain the work, but not the weeks: no tired Tuesdays, no stretch where the whole thing feels pointless, no month where life interrupts.
So the plan quietly expires the first time reality misses it, and a project with an expired plan has nothing holding it up but mood.
The fix is to plan the dull stretch on purpose:
- Milestones you could actually walk. Four or five, small enough that the next one is always reachable this week. A short plan beats a long list, and it beats a grand one too.
- A named fallback for bad weeks. Decide now what counts when everything goes wrong: one page, fifteen minutes, one exercise. Deciding it in the middle of the bad week does not work, for the reason the week-three piece lays out: nobody invents anything on a bad day.
- A finish line you can point at. "Get into photography" cannot be finished. "Print twelve photographs I am glad I took" can. Projects without edges do not end, they fade.
Unfinished is not always a failure, but check which kind this is
Quitting on purpose is a decision. Drifting away is a pattern. Only one needs fixing.
Some projects deserve to die. The interest was borrowed, the goal was inherited, or the first month taught you what you needed and the rest would be sunk-cost theater. Godin's own argument in The Dip is that strategic quitting is what makes finishing possible, because nobody has the capacity to push through every middle.
The test is whether a decision ever happened. Take one item from the graveyard and ask: did I choose to stop, or did I just stop? Choosing looks like a sentence you could say out loud: this is not worth the remaining cost, and I am taking the lesson and closing it. Drifting looks like a project nobody closed, still technically alive, quietly draining attention every time you notice it.
Close the drifted ones deliberately, in either direction. A project formally killed returns its attention to you. A project formally continued gets the structure above. What corrodes is the third state, and most graveyards are built entirely out of it.
Finishing is a skill with a mechanic, not a personality upgrade
Visible progress, a weekly look backwards, and someone expecting something.
None of what actually finishes projects requires a new personality. It requires three pieces of scaffolding, all buildable this week:
- Progress you can see. In the middle, real progress goes invisible, so make it visible artificially: a milestone list where things get crossed off, a chapter count, a wall calendar with marks on it. The point is that on any given day you can see the line moving, because the work alone has stopped showing you.
- A weekly look backwards. Ten minutes, three honest questions, including what moved this week and what the next smallest step is. The review is what catches a stall at one week old instead of at three months, back when it is still cheap to fix.
- Someone expecting something. A project that exists only in your head can die without witnesses. Tell one person what you are finishing and when they should ask about it, or set up accountability without a partner if there is no obvious someone.
This scaffolding is also what coaching is, structurally, and it is the part of it we built Odyssey to do, which you should weigh in how we describe it: the plan lives somewhere outside your head, the check-ins arrive on a rhythm you set, and the weekly review reads your week back to you. Whether the scaffolding is an app, a friend or a paper calendar matters much less than whether it exists.
Why projects die, in five lines
- Starting pays immediately, finishing asks you to pay, and both are normal
- The middle kills projects: novelty gone, results not yet visible
- Day-one plans contain no bad weeks, so they expire on the first one
- A drifted project is not a decision. Close it or continue it, out loud
- Finishing runs on scaffolding: visible progress, a weekly review, a witness
Common questions
Why can I finish things at work but never my own projects?
Because work supplies the entire finishing mechanic for free: deadlines, visible progress, and people expecting things. Your own projects come with none of that installed, which is why they run fine on enthusiasm and stall when it fades. The fix is not to care more. It is to install for yourself what work installs for you.
Is it bad to leave projects unfinished?
Leaving them is fine. Drifting from them is the expensive part. A project you deliberately close, with the lesson taken, costs nothing and often pays something. A project in the permanent maybe-state charges rent every time you remember it. The skill worth building is closing things in either direction, on purpose.
How do I finish a project I have lost interest in?
First decide whether the interest is gone or just the novelty, because they feel identical from inside the middle. Shrink the next step to something walkable this week and take it. If motion brings any of the interest back, it was the dip. If it brings nothing back three weeks running, close the project deliberately and keep the lesson.
Does starting lots of things mean I lack discipline?
Starting is evidence of appetite, and appetite is the raw material. What the graveyard usually shows is not weak discipline but missing structure: no milestones, no fallback, no witness, so every project relied on the one fuel that always runs out. Discipline is what carrying that structure builds, not the prerequisite for it. If the pattern feels older and deeper than any one project, the habit piece covers unwinding it.
Which unfinished project should I go back to?
Run the regret test: which one would sting most to still be unfinished a year from now? Continue that one, with the scaffolding above, and formally close the rest for now. One project moving beats four projects technically alive, and closing the others is what frees the attention the one you chose needs.
The takeaway
The graveyard was never a verdict on your character. It is what happens when projects get funded entirely out of starting excitement, planned by day-one optimism, and left to survive a middle that pays nothing. Structure is the whole difference, and structure is buildable in a week.
One thing to do today. Pick one project from your graveyard and make the decision that never happened: closed, or continued. Say it out loud. If it is continued, write the next milestone small enough to reach this week.
