Everyone focuses on addition. Ship the feature, add the page, copy the competition. And to me I believe its because addition is legible. 1 + 1 = 2 and you can point at the thing you added. Subtraction is invisible work. If I do 1 - 1 = 0 and point at the absence of what was once there; people have to trust you did something.
But the strongest things I’ve made got that way by removal. A service runs faster with tighter logic. A pitch gets sharper when a slide leaves. An interface gets faster when a panel dies.
Why we resist it
Deletion feels like loss because effort is sunk into the thing being cut. But stakeholders never see effort, they see the result; and the result is lighter without it. The cost you paid to make the thing is not a reason to keep it.
Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away.
It’s a cliché because it’s load-bearing. The discipline isn’t knowing the quote but to be willing to delete something good because something else is better, and two goods competing for the same attention leaves you with neither.
A practical rule
When a draft feels off, don’t ask what’s missing. Ask what could leave without anyone noticing. Cut that first. Then read it again. The thing that was actually wrong is usually easier to see once the clutter around it is gone.
This site is an argument in the same direction: no framework where none is needed, no card grid where a list will do, no dashboard where an inbox already lives in everyone’s head.