The Graveyard of Good Starts

You have a folder, a drawer, a corner of your desk, or a tab you haven’t closed in four months. It contains the half-finished thing you were genuinely excited about. Probably more than one. You don’t talk about them much anymore.

Most men in this position diagnose themselves as lazy or undisciplined. Both are wrong, and that misdiagnosis is part of why the pattern holds.

The standard advice is time management: block your calendar, protect your mornings, build the habit. Some men try accountability partners. Some buy new notebooks. What they’re working with is a system designed to solve a commitment problem, when the actual problem is a protection problem. The projects don’t stay unfinished because you can’t organise your time. They stay unfinished because an unfinished project cannot be judged. It sits in the drawer radiating pure potential. It never has to face the world and be found ordinary. Unfinished, the novel is still great. The business idea is still viable. The project is still proof of who you could be, not evidence of who you are. That’s not laziness. That’s a fairly rational psychological operation running on bad assumptions.

The mechanism underneath it has two parts that feed each other. The first is neurological. Dopamine is not a pleasure chemical — it’s an anticipation chemical. It drives wanting, not having. The hit comes from the pursuit: the new idea, the fresh start, the open horizon of a project just begun. Once the novelty settles and the work becomes grinding, incremental, and boring, the dopamine drops off. Starting a new thing restores it. So the pattern of serial starting isn’t a character flaw. It’s a system responding to incentives.

What they’re working with is a system designed to solve a commitment problem, when the actual problem is a protection problem.

The second part is psychological. For men who’ve built an identity around being capable, finishing creates exposure. A finished thing can be criticised, dismissed, or found to be less than the idea of it. An unfinished thing preserves the possibility that it might have been exceptional. Unconsciously, the incomplete project is a shield. The real intervention has to address both.

Run the audit first

Run the audit first. Before any system, you need five minutes of honest accounting. Open your notes app, your drawer, your browser history — wherever your abandoned projects live. Write down every incomplete thing you’ve started in the last three years that still carries weight for you. Not every half-thought, just the ones you’d feel something about if someone asked you directly. Then, for each one, ask a single question: is this unfinished because life got in the way, or because you’ve unconsciously kept it in draft so it can’t be evaluated? You’re not looking for a confession — you’re looking for a pattern. If three or more of the same type of project (creative work, side businesses, fitness goals) are sitting in that graveyard, you have your answer. The first time most men run this audit honestly, the number is higher than expected. That’s useful. Write it down. Don’t file it.

Serialise ruthlessly

Serialise ruthlessly. The most effective structural change you can make is also the one most men resist: one major project at a time. One. If you’re running two jobs, that might mean one major non-work project. The ceiling is two — one in each domain — and that’s the absolute limit, not the target. Everything else goes onto a waiting list that you write down and do not act on. The anxiety of deferral is real and it will feel urgent. That’s the dopamine system telling you the new thing would feel better than the hard middle of the current thing. It’s right. It would. That’s not a reason to switch. The rule holds: you do not start anything new until the current major project reaches a declared finish line. When the anxiety spikes — and it will, usually around week three of a hard project — the protocol is to add the new idea to the waiting list, not to act on it. Writing it down reduces the urgency by about 70% for most people, because the brain stops treating it as something that might disappear.

Declare the finish line before you start

Declare the finish line before you start. This sounds obvious until you realise how rarely it happens. Most projects begin with a vague aspiration and no specific definition of done. That ambiguity is structural protection — if done is undefined, you can never technically fail to reach it, and you can never be held to having finished something that then gets judged. The protocol is specific: before you commit a single hour to a project, write one sentence that defines what completion looks like. “A 2,000-word draft submitted to one publication by March 31st” is a finish line. “Getting my writing out there” is not. The finish line needs a deliverable, a standard, and a date. All three. Without all three, the project will drift. Make the standard “good enough to release” rather than “good enough to be proud of forever” — those are not the same thing, and conflating them is where perfectionism does its damage.

Lower the bar on purpose

Lower the bar on purpose. When you hit the wall where the project stops feeling exciting and starts feeling like work that might embarrass you, the move is deliberate de-escalation of the standard. Ask yourself plainly: is the imperfect version that exists better or worse than the perfect version that doesn’t? This isn’t a motivational trick. It’s a real decision about tradeoffs. The published piece with three flaws teaches you something, creates something, and earns something that the flawless draft on your hard drive cannot. Pick a concrete threshold — 80% of what you’d consider ideal — and treat reaching it as the actual goal. The additional 20% is usually where projects go to die, and the marginal improvement rarely justifies the cost of never finishing.

One honest caveat

One honest caveat. This approach will not resolve a project that genuinely shouldn’t be finished. Some things on the graveyard list are there because they were wrong fits from the start — wrong timing, wrong direction, ideas you chased for external reasons rather than real ones. Serialising and lowering the bar on one of those won’t produce satisfaction; it’ll produce a finished thing you don’t care about and a loss of time. The audit is supposed to catch this, but it’s not foolproof. If a project survives the audit and still feels dead when you sit down with it three sessions in a row, the question isn’t how to push through — it’s whether this one belongs on the list at all. Killing the right projects deliberately is different from abandoning them.

The ceiling is two — one in each domain — and that’s the absolute limit, not the target.

Tomorrow morning, run the audit. Twenty minutes, no more. List what’s in the graveyard, mark the ones that are shields rather than casualties, and pick one to finish. Write its finish line — deliverable, standard, date — in one sentence before you close the document.

is the imperfect version that exists better or worse than the perfect version that doesn’t?

That’s the start. Don’t start anything else.