"I want a really simple website, just one button that does everything automatically, without asking for too much data. Since it's so simple and clean, it'll cost next to nothing to build, right?"
This is perhaps the sentence I've heard most often during first briefs with clients. Spoiler: creating something "extremely simple" for the end user is, paradoxically, the most technically complex (and expensive) thing a design and development team can do.
Behind a clean, intuitive, friction-free interface lies a golden rule of software engineering and UX: Tesler's Law, also known as the Law of Conservation of Complexity.
Complexity isn't destroyed, it's transferred
Larry Tesler, the famous computer scientist (who, among other things, invented copy and paste), argued that simplicity always has a hidden price. Here's how his principle works, in 3 key steps.
1. The fixed-share principle
To work properly, every digital product or process (like booking a flight or buying a product) has a "fixed", intrinsic share of structural complexity. This complexity can't be magically wiped away with the magic wand of design: it simply exists. It has to be managed.
2. Shifting the load
The game of web design comes down to one crucial decision: who takes on this complexity? Either you offload it onto the user, forcing them to fill in endless forms, read instruction manuals, remember passwords or do mental arithmetic, or you decide to absorb it yourself, inside the system.
3. The visual illusion of Big Tech
Companies like Apple, Google and Amazon have got us used to products that do incredible things with a single, utterly ordinary "tap" on the screen. But behind that spotless, elegant button there are extremely powerful servers, decision trees, conditional rules and thousands of lines of code written by teams of engineers who literally "sweated" to hide all that algorithmic effort from the end user's eyes.
True elegance is invisible
An important detail to remember: when you ask a web professional to "simplify the navigation flow", you're not asking them to work less. You're literally asking them to take the cognitive and operational weight off your potential customer and carry it on their own shoulders, solving it on their behalf through design and code.
This is the essence of true elegance in design: making things that are technically very hard to get working look natural, obvious and incredibly easy.
