What's the difference between a writing project and a coding project?

The artifact is the verb, not the noun. A writer who writes 200 words a day for 6 months finishes a novel. A developer who codes 30 minutes a day for 6 months finishes a feature. The cadence is similar. The difference is that writing is more exposed — the writer's voice is the artifact, and stepping away makes the voice harder to recover.

What if my writing has gotten worse since I stopped?

It hasn't. You just forgot how to read your own writing. Read 10 pages of the old draft out loud. The voice is still there. The 'worse' feeling is the gap between your current skill and the skill you had when you wrote it. The skill comes back when you start writing again.

Guide · Writing

How to revive a writing project

Q: Why do writing projects die?

Three reasons: loss of momentum, the messy middle (the chapter-3-to-30 problem), and the perfectionism trap (the sense that every sentence needs to be great). Writing is uniquely susceptible to the Zeigarnik effect — incomplete tasks stay in your mind, generating guilt, which makes it harder to start. The cure: ship a draft, then revise.

Q: Should I write a new draft or revise the old one?

Always revise the old one. The old draft is the work. The voice, the characters, the plot, the texture — they're all in the draft. A new draft is a different book, and the problem isn't the draft, it's the writer's relationship to the work. Revive the draft, not the writer's self-image.

Q: Can I hand off a writing project?

Yes, but it's rare. Co-authoring is a model that works (the second author brings fresh energy, the first author holds the vision). The more common outcome is a co-writing relationship where one person drafts and the other revises. Solo handoffs to a stranger are very rare — the voice is the artifact.

The unfinished novel. The abandoned blog series. The memoir that stopped at chapter 3. The article that lived as a 500-word draft for 2 years. 70% of writing projects die before completion. This is the 5-step playbook for reviving a writing project that you walked away from.

Published July 13, 2026 · ~6 min read

The 70% problem

Most writers have one — the project they keep coming back to, the manuscript that lives in a Google Doc, the article series that stopped at #5. 70% of writing projects die before they're finished. The 30% that finish share one thing: a specific moment when the writer stopped second-guessing and started shipping. This guide is about creating that moment.

The 5 steps

Step 1: Read the existing draft in one sitting

Before you write a single new word, read the existing draft in one sitting. From the first sentence to the last. No editing, no notes, no "I'll fix this later." Just read. The act of reading is the act of remembering. You'll remember why you started, what you were trying to do, and what the project actually is — not what you fear it's become.

Step 2: Identify the moment you stopped

The draft will have a moment — a chapter, a section, a paragraph — where the energy drops. That's where you stopped. The drop is rarely a quality problem. It's usually a structural problem: a missing scene, a character who disappears, a transition that doesn't land. The "I lost momentum" feeling is real, but it's a symptom of a structural gap. Find the gap.

Step 3: Write a 100-word "bridge" for the gap

Don't try to fix the whole structural problem. Write a 100-word "bridge" — the worst possible version of the missing scene. The worst possible version is the one that gets you back to the desk tomorrow. You can fix the bridge later. The goal of the bridge isn't quality, it's continuity. The goal is to make tomorrow's writing possible.

Step 4: Daily 200-word sprints, no exceptions

200 words a day. No exceptions. Not 500. Not 1000. 200. The number is small enough that "I don't have time" is never an excuse, and large enough that the project moves. 200 words × 365 days = 73,000 words — a full novel. The cadence matters more than the volume. 200 words a day for 6 months beats 5,000 words a week for 6 weeks.

Step 5: Ship the first draft before you revise

The single most important step. Ship the first draft before you revise. Most revived writing projects die in the revision phase — the writer starts editing chapter 1 in month 6 of the revival, gets discouraged, and stops. Don't edit the beginning until you've written the end. The first draft is allowed to be bad. The first draft's job is to exist.

The 4 ways writing projects die differently from code

Voice fade: a writer's voice is a state, not a trait. Long breaks erode it. The cure: read 10 pages of the old draft out loud before resuming.
The chapter-3-to-30 problem: most novel manuscripts die in the middle 30%. The cure: outline the missing middle before resuming the writing.
Perfectionism spiral: writers edit as they write. The cure: separate writing from editing. Two passes, not one.
Audience anxiety: the writer imagines an audience judging the work in progress. The cure: write for yourself first. Audience comes after the draft is done.
The "publish or quit" trap: the writer waits for the perfect moment to publish. The cure: publish anyway. Bad published work beats good unpublished work.

Frequently asked questions

Why do writing projects die?

Loss of momentum, the messy middle, perfectionism, audience anxiety. The cure: ship a draft, then revise.

Should I write a new draft or revise the old one?

Always revise the old one. The voice, the characters, the texture are in the draft.

Can I hand off a writing project?

Yes, but rare. Co-authoring works. Solo handoffs to a stranger are very rare — the voice is the artifact.