Good design feels simple
Not because it is simple on the surface, but because someone wrestled with the chaos behind it.
The honest answer
A friend asked me last week why a Stripe checkout feels good and a bank app feels like work. Same primitives. Same fields. Different posture.
The honest answer: someone fought for it. Someone said no to a feature, picked a default, killed a column. The polish is downstream of the fights, and the fights are downstream of having one person who cares enough to lose sleep over a dropdown.
What gets cut
Look at any checkout you trust and you can reverse-engineer the cuts. The country dropdown is preselected from IP. The card type icon is inferred from the first six digits. The CVV field is the right width because some designer measured it three times. None of these were arguments anyone wanted to have, and all of them were arguments.
Most product surfaces show the opposite. Twelve fields where five would do. A second button labelled Cancel sitting next to Save because someone in legal asked for it. The screen reads like a meeting transcript.
Why most teams avoid the fight
Fighting is expensive. It bruises relationships, it puts you on the wrong side of a roadmap, and it usually means going back to the PM who pushed for the extra field with a research deck the PM has already seen.
The cheap path is the additive one. You add the field, you add the button, you add the upsell. Nobody loses face. The product gets a little uglier. Repeat for two years and the surface is unrecognisable.
A fight I lost
In 2023 I lost an argument about a settings refactor in payroll. The setting in question was visible to roughly nine percent of accounts and changed behaviour for almost none of them. The compromise was to keep the toggle and hide it behind a 'more options' affordance. Months later the same toggle showed up in three support tickets, because hidden does not mean gone.
The right call was deletion. I knew it then. The reason I lost is that the cost of removal sat with me and the cost of keeping it sat with no one.
What I look for now
When I open a product I want to learn from, I look for the cuts. Empty space where a field should be. A default that obviously took a meeting to defend. Sometimes a button I expected to find and cannot.
Those are the fingerprints of a designer who held the line. The polish is everywhere. The conviction is in what is no longer on the screen.