The Last 10%: Why "Done" Isn't Really Done

There's a theme in my work I'm constantly reminded of—and if you're a creator or developer, you've probably seen it too. It's that moment where we finish a task, feel 100% done, and excitedly deploy it—only to get quick feedback that we missed some tiny but crucial detail. Maybe it's something that didn't work properly, something that broke everything, or just something I forgot. That small blunder can overshadow all the hours you poured into the project.

Attention to detail is a professional must-have, and it's something I've struggled with my entire career. At one point it became almost routine, and I believe it marred my reputation. Reputation takes a long time to rebuild—if it can be rebuilt at all.

For me, awareness of the problem was almost enough to fix it. The rest came from raising my standards: now, being 100% done means finishing the last 10%. Usually we just need to resist that urge to deliver right away. Chances are, it can wait one more day—long enough to look at it with fresh eyes. After hours of work, the last thing anyone wants to do is review the entire thing against requirements. Something about it just feels like school in the summertime.

The world is different now, the old 100% done is now only 90% of the way there. Real completion means more than just finishing the work—it means testing it, reviewing it, comparing it against requirements, and questioning whether those requirements even make sense. That's the last 10%.

So I urge you: do the unsexy thing. When something feels "finished," put it aside and give it one last look tomorrow with fresh eyes. If it can't wait until tomorrow, go for a walk or take a break and come back. If it's big, it deserves the last 10%. Your reputation will thank you, and nothing is sexier than consistent excellence.