Craft Is the Last Ten Percent

Two projects can be identical in concept, structure and content, and one of them will feel expensive while the other feels approximate. The difference is almost never a big decision. It is a hundred small ones that nobody was asked to make.

Nobody notices craft, everyone feels it

Users do not report that the optical alignment on an icon is off or that a corner radius is inconsistent between two components. They report that something feels unfinished, or they simply trust the product slightly less. Craft is the difference between those two outcomes, and it never shows up in a feature list.

Where it usually goes missing

Edge cases and unglamorous states. The empty list, the error message, the loading skeleton, the very long name, the second page of results. These get built late, under time pressure, by whoever is available. They are also the moments where users are most uncertain and least forgiving.

Optical, not mathematical

Centred is not always centred. A play triangle needs nudging inside its circle. Uppercase text needs different tracking than lowercase. A cap-height headline sits differently against an image than the maths suggests. Trusting the eye over the numbers is most of what separates finished work from aligned work.

Craft is a budget decision

The last ten percent takes a disproportionate share of the time, which is why it is the first thing cut. If it matters, it needs to be scheduled at the start rather than hoped for at the end. Naming it as a phase makes it defensible when the timeline compresses.

Systems protect craft, they do not replace it

Tokens and components carry good decisions forward so nobody has to re-earn them. But a system cannot tell you that this particular headline needs a manual line break, or that this photo crop is fighting the copy. Judgement still has to be applied, just less often.

How we do it at Monaro

We schedule a dedicated refinement pass before every launch and treat it as non-negotiable scope. We review every state, not just the happy path, on real devices at real sizes. We keep a running list of small imperfections throughout the build so the pass has a target rather than relying on someone noticing on the day.