The last 10% is a different job
The first 90% of a project is solving problems. The last 10% is something else entirely — and most teams don’t switch modes in time.
There’s a specific moment in every project where the work changes shape. Up until that moment, you’re solving problems: figuring out structure, drafting designs, wiring up features. It’s generative. You’re adding.
Then, almost always without anyone announcing it, the project tips. The big problems are solved. What’s left is a long list of small ones. This is the last 10%. And it is a completely different job from the 90% that came before.
Why teams struggle here
Because most teams don’t switch modes. They keep trying to ‘build’ when what’s needed is ‘finish.’ The skills are different. Building rewards speed, decisiveness, big moves. Finishing rewards patience, precision, and a willingness to care about things nobody will consciously notice.
Teams that stay in build mode ship products that are almost-right. Teams that switch to finish mode — and give themselves permission to slow down — ship products that feel considered.
“The difference between shipped and finished is usually two more weeks of caring about things no one asked for.”
What the last 10% is actually made of
The hover states that nobody specced. The empty state when the list has zero items. The loading sequence that’s either 50ms too fast or 200ms too slow. The error message that’s condescending without meaning to be. The first 20 seconds of the mobile experience on a slow connection.
None of these will make or break the product. Collectively, they make the difference between a product users describe as ‘nice’ and one they describe as ‘polished.’ That word — polished — is the compound result of a hundred small cares.
Making time for it
The hardest part of the last 10% is that it doesn’t feel like progress. You end the day with no new features. The product looks the same. But a dozen small sharpnesses have happened that will pay back forever. Teams that protect this time — treat it as a phase, not an afterthought — build things that age better.
Teams that don’t end up treating ‘polish’ as a ticket type in their next quarter. It becomes technical debt with a different name.
What finish mode looks like
Slower standups. Longer pauses before decisions. More screenshots. Less new code. People sitting with something for ten minutes before touching it. The team goes from sprinting to carving.
If you’ve never worked this way, it feels wasteful the first time. It isn’t. It’s the difference between a good product and an unforgettable one.
Shipping is important. Finishing is rarer. Most teams conflate them. The ones who don’t build things that other teams end up quietly copying.