Done Is Better Than Perfect: Why Good Enough Isn't Settling for ADHD Brains

By Tim Williams · @AuDHD_Founder

The project has been ninety percent finished for three months. Not because you're lazy. Not because you don't care. Because the remaining ten percent is the part where you decide it's done and release it into the world, and every time you get close to that decision, the brain finds something else that needs fixing first. The font. The wording on page seven. The structure of the second section. One more pass to make sure.

That project is not going to help anyone. The version in your head, the perfect version you're endlessly circling toward — that one doesn't exist either. The only version that helps anyone is the one that ships. And the one that ships is, by definition, the good-enough version.

For ND brains, "good enough" isn't a surrender. It's a strategic decision about where to spend finite resources. It's understanding that completion has a value that perfection doesn't, because completion is the only version that exists in the world.

What's actually happening

The neurological piece here has two parts. The first is the perfectionism-as-anxiety mechanism — the nervous system that treats imperfection as a genuine threat and refuses to release the grip. The second is task completion and reward signaling. In neurotypical brains, completing a task produces a dopamine reward that reinforces the completion behavior. For ADHD brains, that reward signal is often delayed, muted, or inconsistent.

What this produces is a double bind: the perfectionism drive keeps you from finishing, and the muted completion reward means finishing doesn't feel as good as it should when you do it. So the behavior of "keep working on it instead of finishing it" gets reinforced, and the thing never ships.

There's also an interest piece. The working-on-it phase, especially early, is interesting — the problem is novel, the thinking is engaging. The finishing phase — editing, polishing, preparing for release — is often the least interesting part of any project. The ADHD brain loses the intrinsic motivation signal right when you need it most.

Psychology Today's research on perfectionism and procrastination documents the consistent link between perfectionism and avoidance — specifically, that perfectionism doesn't produce better outcomes, it produces delayed or abandoned outcomes. The fear of imperfection doesn't create perfect work. It creates the absence of finished work.

Why it feels this way

"Good enough" feels like settling because the culture around quality work has consistently sent the message that higher standards equal better character. The perfectionist identity gets praised — "you're such a perfectionist" is usually delivered as a compliment — which reinforces the very pattern that prevents completion.

For ND people with histories of being told they're not trying hard enough, the perfectionism also carries a compensatory quality. If the work is perfect, nobody can say you didn't try. If the standard is high enough, the criticism can't reach you. The perfectionism isn't just anxiety about the work — it's armor against the judgment that's been historically very painful.

The problem with armor is that it's heavy and it slows you down. The project that never ships because it's always being improved is safe from criticism, yes. It's also safe from helping anyone. The book you never finished. The app you never launched. The article that's been in drafts for two months. They're protected from judgment and completely useless.

Good enough that exists is infinitely more valuable than perfect that doesn't. The version you ship changes someone's day, week, or life. The version you're still improving changes nothing.

What actually helps

Define "done" before you start, in writing.

The most powerful thing you can do against perfectionism is remove the moving goalpost. Before you start a piece of work, write down what "done" looks like — specifically, in terms you could verify. "Three sections, introduction, body, conclusion, reviewed once, submitted." Not "as good as it can be" — that definition never produces done, because there's always another iteration. The completion criteria has to be external to your sense of quality.

Use timeboxing as a release mechanism.

If you've spent two hours on something and it's at a reasonable state, it goes. Not because two hours produces perfect — because two hours is the container you chose and the container is what creates completion. Without external time constraints, the perfectionism engine runs indefinitely. With them, it has to stop at an arbitrary boundary. That arbitrary boundary is your friend.

Ship smaller things more frequently.

One reason big projects become perfectionism traps is the size of the stakes. The bigger the thing, the more critical it feels that it be right. Break it into smaller pieces and ship those. The blog post instead of the book. The feature instead of the product. The draft shared with one person instead of published to everyone. Smaller things have smaller stakes, which gives the perfectionism mechanism less to grip.

Collect data on your predictions.

The catastrophe that perfectionism is protecting you from — the criticism, the failure, the judgment — how often does it actually happen? When you've shipped things that weren't perfect, what was the actual outcome? Most people find that their predictions of disaster significantly overstate the actual response. Accumulating real data about "I shipped an imperfect thing and the world didn't end" is the most evidence-based argument against perfectionism you can build.

Distinguish between "better" and "done enough to help."

Almost everything can be improved. The question isn't whether this could be better — it's whether this is good enough to be useful. A finished article that helps fifty people is better than an improved article that never goes out. Good enough to help is a meaningful standard. Good enough to withstand any possible criticism is not a standard — it's an impossibility used as a completion-prevention mechanism.

What doesn't help

• "Just lower your standards." Standards and perfectionism are different things. Finishing work to a good standard is healthy. Refusing to finish because it can always be improved is not about standards — it's about anxiety. Telling someone to lower their standards misidentifies what's happening.
• Positive feedback that raises the stakes for the next thing. Paradoxically, effusive praise for a piece of work can increase the perfectionism pressure for the next one. The perceived standard just went up. Good feedback: specific, about what worked, without superlatives that create impossible next-time expectations.
• "Done is better than perfect." True, often said, never once fixed perfectionism by being said. Knowing this intellectually doesn't override the neurological response. The intervention has to happen at the system level, not the thought level.
• Adding more feedback loops before shipping. "Let me get three more people to review this" is sometimes legitimate quality control and is sometimes adding more opportunities to delay completion through new information. Know which one you're doing.

The bigger picture

The things you build matter. The work you put out in the world — imperfect, real, shipped — accumulates into a body of work that helps people. The things you kept refining forever don't.

The SHIFT app wasn't perfect when we first shipped it. The Wired Different book wasn't perfect. Nothing worth doing is perfect, because perfect is a moving target that recedes at exactly the rate you approach it. What you can do is build something solid, something useful, something real — and then let it go.

Good enough isn't giving up on quality. It's understanding that quality is measured by impact, and impact requires existing. The good-enough version that helps someone is a higher quality product than the perfect version that never reaches them.

If the perfectionism is tied to anxiety, the perfectionism as anxiety piece goes deeper on the neurological mechanism. And if you're not finishing things because you can't start them, that's a different issue — covered in the executive dysfunction article.