How is this different from the 90% rule concept page?

The 90% rule is a phenomenon — projects die at 90% complete. This guide is the counter-measure: the 5 things you do specifically to push through the 90% barrier. The phenomenon is the diagnosis. This guide is the prescription.

Can I use this guide to revive an old project?

Yes. The 5 reasons projects die apply to revived projects too — the polish phase is the same, regardless of whether it's the original polish or the re-polish. Many revival projects die at the 90% re-polish barrier, not at the original 90% barrier.

Guide · Universal

Finish what you started

Q: What does 'done' mean?

Done means: a person can use it. A draft exists. A song can be played. A room is painted. A product has shipped. The functional definition of done is the only one that matters. The aesthetic definition of done is the enemy of shipping.

Q: What if I can't ship the 90% version because it's bad?

Ship it anyway. The 90% version is bad in 100% of cases. The 100% version is bad in 100% of cases. Bad-and-shipped beats good-and-unpublished every time. You can't revise a draft that doesn't exist. You can't pivot a product that hasn't launched. You can't learn from feedback you haven't received.

Most projects die at 90% complete. The polish phase is where they die. This is the guide to finishing what you started — for code, writing, art, music, home, business, and learning projects alike.

Published July 13, 2026 · ~6 min read

The 90% problem

Across every project type, the same pattern shows up: 70-90% of projects die in the last 10%. The creative work is done, but the project doesn't feel "done." The founder can see all the imperfections at once. The writer can see all the prose that needs revising. The musician can hear all the parts that need re-recording. The gap between "the work is good enough" and "the work is perfect" is where projects die. This guide is about closing that gap.

The 5 reasons projects die at 90%

Each reason has a specific counter. Pick the one that sounds like your project.

Reason 1: Perfectionism spiral

You're polishing chapter 1 when you should be writing chapter 12. Or fixing the homepage button color when you should be writing the docs. Or re-recording the vocals when you should be mixing the album.

Counter: the "no backward edits" rule. Don't edit anything you've already written/coded/painted until you've completed the next 10%. The polish phase is the end, not the middle.

Reason 2: Scope creep

"If I'm already 90% done, I might as well add that one feature / write that one more chapter / record that one more song." Scope creep turns 90% into 70% of a larger project. The new features are exciting; the original 90% is now invisible.

Counter: the "ship now, ship next version" rule. The version that ships is the version that exists. The next version can be a different project.

Reason 3: Audience anxiety

The closer you get to shipping, the more real the audience becomes. The novel you're writing is just a draft. The novel you're about to publish is a book. The code you're refactoring is just a branch. The code you're about to deploy is a product. The product has users. The users have opinions.

Counter: the "ship to 5 people, not 5,000" rule. Find 5 trusted readers, users, or listeners. Ship to them. Their feedback is the antidote to imagined audience judgment.

Reason 4: Energy depletion

You started with 4-hour weekends. You're now in the 9th month of the project. The 4-hour weekends are gone. The 90% phase is the phase where you no longer have the original energy, but you're also not yet seeing the payoff of shipping. The energy budget is depleted.

Counter: the "10% in 10 days" rule. The last 10% can usually be done in 10 days of focused work. The time it took to get to 90% is not the time it takes to finish. The finish-line is closer than it feels.

Reason 5: "Not quite ready" syndrome

The project is "not quite ready" — for shipping, for showing, for testing, for whatever. The "not quite ready" feeling is a constant. It never fully goes away. The only way to ship is to ship while it's not quite ready.

Counter: the "ship date, not ship moment" rule. Pick a ship date. Tell 5 people. Ship on the date, regardless of readiness. The date is a forcing function.

The 3 universal finishing rituals

The 5-person review. Before shipping, show the work to 5 people you trust. Their reactions will reveal what really matters and what's just polish.
The 1-week cooldown. After you think the project is done, walk away for 1 week. When you come back, you'll see the work with fresh eyes. The 1-week break also tells you which projects you actually want to ship (vs. which projects you've outgrown).
The public ship date. Pick a date. Announce it. Ship on the date, even if the work isn't perfect. The public date is the strongest forcing function.

Frequently asked questions

Why do most projects die at 90%?

The polish phase is the worst phase. The creative work is done, but the project doesn't feel "done."

What does "done" mean?

A person can use it. A draft exists. A product has shipped. The functional definition of done is the only one that matters.

What if I can't ship the 90% version because it's bad?

Ship it anyway. Bad-and-shipped beats good-and-unpublished every time.