Why simple is hard
Complexity never announces itself. It arrives as a series of good points, one reasonable request at a time, and nobody's job is to say no.
Watch a homepage die sometime. It’s educational.
It starts clean. One idea, one image, one thing to do next. Everyone in the first meeting loves it, and everyone means it. Then the reviews begin. Legal needs a disclaimer above the fold. Sales wants the phone number bigger, and also a banner for the trade show. The founder’s spouse thinks the photo feels cold. Someone from the board asks, gently, where the video is. Each request is reasonable on its own. The people making them are smart. And eighteen reasonable requests later the page is a parking lot, and nobody can tell you exactly when that happened.
Nobody in those meetings was wrong, either. That’s what makes simplicity so hard to defend. Complexity never arrives announcing itself as complexity; it arrives as a series of good points.
Nobody’s job is to say no
Here’s the structural problem underneath it all: addition has a constituency and subtraction doesn’t. Every element on a page has someone who asked for it, someone whose job it validates, someone who will notice if it disappears. Removal has no sponsor. No department head walks into a review demanding less. So the forces acting on any design are permanently lopsided, a dozen hands pushing things in and, on a good day, one tired voice suggesting something come out.
Simple, then, isn’t a style. It’s a score. It tells you who won the fight.
Removal has no sponsor.
When you see a genuinely simple thing (a page with one message, a product with three buttons, an identity that fits on a napkin), you’re not looking at minimalist taste. You’re looking at the residue of a hundred arguments somebody had the stamina to win. Every absence on that page was defended. Someone caught each addition heading in and turned it away at the door, meeting after meeting, and kept doing it long after it would’ve been easier to just let the banner through.
What simple isn’t
It helps to be clear about what simple isn’t, while we’re here. Simple isn’t sparse for its own sake, and it isn’t the absence of thought wearing the costume of restraint. An empty page that fails to answer the visitor’s first question isn’t simple; it’s just unfinished. Real simplicity means the hard decisions got made upstream so the reader never has to make them downstream. One is a gift. The other is homework.
This is why simplicity costs more, not less, which clients occasionally flinch at. The simple version looks like less work because there’s less on the screen, but the screen isn’t where the work happened. The work happened in the versions that don’t exist, in the features that got argued back out, in the fourth round where somebody said “what if we cut the whole section” and then had to prove it wouldn’t hurt. Subtraction under pressure is expensive precisely because the pressure never lets up.
Defending the white space
Our job, a lot of days, is to be the constituency for what’s missing. We represent the empty space in meetings where it has no other friends. Somebody has to say the annoying things: that a reader gets one first impression and it can’t be nine things at once, that a page which says everything ranks last in memory, that white space is doing work even when it looks unemployed. It’s not a beloved role. It is, as far as we can tell, the whole reason to hire people like us instead of just buying a template and a thesaurus.
One more inconvenient truth, then we’ll let you go. The fight never fully ends. Ship the simple version and the additions start again the following quarter, one reasonable request at a time, because the forces that crowded the page the first time are structural and structures don’t retire. Simplicity isn’t a launch state. It’s a maintenance discipline, like weeding.
The lot never paves itself all at once. It’s one parked car at a time, each with a perfectly good reason to be there.
