Heitor Gouvêa

Research About


The last 20%

I like to dig into old publications from people or companies that created something I consider truly relevant, especially texts written before their major breakthroughs, to understand how their thinking was being shaped.

This morning I was reading some posts from the Cognitect blog, the company behind Clojure and later acquired by Nubank, and one title caught my eye: “The last 20%.” The author reflects on how most of the work seems to flow smoothly in the first 80%, but it is in the last 20% where the true perception of quality is defined. That is precisely when details matter most and mistakes become more costly.

It made me think about something I often see in open source projects and personal initiatives. These ideas usually start full of energy, often as exercises in learning or research. But they rarely make it to the end. The last 20% becomes the real challenge, not because it is technically impossible, but because it is made up of tedious work: handling edge cases, writing documentation, eliminating technical debt, improving error messages, cleaning interfaces, and making sure the thing behaves well outside the happy path.

This work does not always feel creative. It does not always bring immediate learning. It rarely has the excitement of the first prototype, when everything is possibility and every new commit feels like visible progress. But it is exactly this effort that transforms a side project into something usable by others.

That is what separates a repository sitting on GitHub from software running in production, even if only a handful of people are using it. The difference is not only technical complexity. It is the willingness to finish the boring parts that make the work trustworthy.

This can also make a huge difference in job interviews. A finished project demonstrates more than technical skill. It shows the ability to take an idea all the way to real delivery. It shows that you can move beyond the fun part of invention and deal with the responsibilities that appear when someone else depends on what you built. That is when value goes beyond yourself and becomes shared.

In the end, the last 20% is not just about polish. It is about responsibility, discipline, and commitment to the people who will use what you have built. That is the point when a project stops being just an experiment and starts becoming a product with real impact.

And from a product perspective, the same logic applies. Paying attention to the last 20% is often what sets you apart from competitors by delivering a smoother, more reliable experience. In other words, the final details define not only perceived quality, but also long-term success.

This publication is also available in: Portuguese and Spanish.