The Art of Simplicity

You start with a block. A block of marble, a blank Figma canvas, a fresh repo. For the briefest of moments, it’s perfect. Full of potential and promise.

Then we begin to add things. A menu here, a button there. A tooltip to explain the button, and perhaps a modal to explain the tooltip. Before long, that clean block has become a crowded roundabout of well-intentioned features, each politely insisting on its right to exist. That you need to explain with a JavaScript tour library… whilst your mouth is full of humble pie.

No one sets out to make something complicated. It just happens, one small decision at a time.

The Problem Of Extraneous Complexity

Every addition, however sensible it feels, adds weight. Each new element introduces a choice, a pause, a moment for the user to think… and thinking, in this context, is friction.

Cognitive load theory divides this friction into two kinds.

Intrinsic load is the unavoidable complexity of the task itself. Some things are just hard: transferring money, configuring privacy settings, submitting tax forms.

Extraneous load, however, is self-inflicted. It’s the confusing layout, the redundant option, the animation that looks nice in a demo but adds half a second to every interaction.

Extraneous complexity is what happens when our good intentions outpace our restraint. We equate activity with improvement, shipping with progress, features with value. The trouble is, each “quick win” comes at a cognitive cost. Each extra bit of load erodes the clarity and calm that make a product feel effortless.

Over time, those tiny decisions accumulate, until what was once a graceful tool starts to feel just a little heavy in the hand. Or maybe just plain weird, I’m looking at your Mr Spork!

Sculpture: The Path To Purity

Michelangelo has been quoted as saying:

“The sculpture is already complete within the marble block, before I start my work. It is already there, I just have to chisel away the superfluous material.”

Whether or not he truly said it hardly matters. It remains one of the best metaphors for design ever uttered.

Because product design, like sculpture, isn’t about adding. It’s about revealing. The essence of a good product, the part that makes it necessary, even delightful, already exists within the idea. It’s there before the Jira tickets, before the wireframes, before the brainstorm.

Our job isn’t to decorate the block; it’s to uncover the form within it.

Each decision to remove something brings us closer to that form. Each deletion clears a little more marble away from the figure underneath.

The Delete Key As A Creative Tool

Most people see the delete key as an instrument of Oppenheimer scale destruction, but in practice it’s the most creative key on the keyboard. It’s the designer’s chisel - small, decisive, and capable of bringing form out of noise.

Deleting forces us to confront purpose. What does this element do? Would the experience suffer without it? Would it, perhaps, improve? You learn a lot about a design when you start taking pieces away.

The wonderful thing about software is that, unlike marble, it forgives experimentation. You can branch, undo, revert. You can carve too deep and still put the nose back on. So there’s no reason not to explore what happens when you strip things away.

Often the most beautiful interface isn’t the one you finished building, it’s the one that’s revealed when you stop.

What To Remove, And When To Stop

Simplification is a form of discipline, not deprivation. It’s easy to make something minimal; it’s harder to make something essential.

A few honest questions help. Does this feature help someone achieve their goal faster or more confidently? Would it exist if no one inside the company had pushed for it? Does it add value, or just volume?

You can even mangle Marie Kondo’s famous question: does this feature spark joy? If it doesn’t, it’s probably clutter.

The trick, of course, is knowing where to stop. Too much removal and the product collapses under its own purity - users lose the feedback, context, or flexibility they need to succeed. This is the fine art of editing. Simplicity isn’t the absence of detail; it’s the presence of clarity.

Tesler’s law and the limits of reduction

Larry Tesler’s Law of Conservation of Complexity states that every system contains a certain amount of complexity that cannot be removed - only shifted. The question, then, isn’t whether complexity exists, but who should bear it.

Well-designed products shoulder as much of that weight as possible on behalf of the user. They hide the hard parts inside intelligent defaults, smart anticipation, and adaptive flows. Simplicity, in this sense, doesn’t mean “less work”. It almost always means more work - for the design and implementation teams, but crucially not the user.

You can look on that as empathy but if you want to be harder nosed, consider that you will “fix” something once that will be used by thousands of users thousands of times (because I know the products you build are winners!). The time savings here are enormous.

The irony of simple products is that they are almost never simple to make. They’re the result of many invisible decisions, all taken in service of the user’s ease. But that invisible effort pays off. Users who find your product calm, intuitive, and predictable don’t just complete tasks - they trust it more deeply.

Again we can look at this with a little hard boiled cynicism. Users that trust products generate less of a support burden and are willing to spend more with you.

Progressive, Adaptive, Predictive Simplicity

Not all complexity is avoidable, but much of it can be staged.

• Progressive simplicity: means showing only what’s needed at first, revealing depth as confidence grows.
• Adaptive simplicity: means responding to context — surfacing relevant controls and hiding the rest.
• Predictive simplicity: means quietly preparing what the user will need next, before they ask for it.

These are the modern chisels of design — ways to manage complexity without exposing it. Tesler’s law may define the boundary, but these techniques show how to dance on the edge of it.

Designing For Delight, Not Deprivation

There’s a cultural suspicion that simplicity means less - less choice, less innovation, less capability. But simplicity isn’t about restriction; it’s about focus. It gives back freedom to the user by removing the clutter that interrupts their intention.

The best tools aren’t ones we notice. They feel natural, even obvious, as if they’ve been there all along. That invisibility isn’t laziness, it’s love. Someone took the time to remove every moment of hesitation until only the task remained.

When we do that well, simplicity becomes generous. It makes the user feel clever, not confined.

Practising simplicity

To apply this in your own work, try approaching your next project as a sculptor would. Start with the block. Define the shape of success, the single outcome that matters most, and build only what serves that purpose.

Run regular deletion sprints where the goal isn’t to add, but to remove. Ask of every new feature: what will it make heavier? Design reviews often ask “what else could we add?” Try asking instead, “what would happen if we didn’t?”

Simplicity is not a phase of design; it’s a posture of care.

The sculptor’s patience

If you’ve ever watched a sculptor at work, you’ll know how slowly it goes. Each strike is measured, each pause deliberate. They spend more time looking than chiselling. That stillness isn’t hesitation; it’s listening - to the material, to the form, to what’s already there.

I’ve found a quiet version of that same patience in carving butter knives from wood. I use firewood from my stove… offcuts and odd bits, pieces already marked by the grain and their own eccentricities. Each knife is slightly different, shaped by the eccentricities of the wood itself. I follow its lead more than I impose my own. I carve until my hands ache, then I stop. When the knife feels right, I sand it, oil it, and give it away.

I don’t do it for utility or even for the result. I do it because the act of carving - of working with imperfection, of revealing the form that was already there… feels profoundly right to me. It’s a small, human expression of the same impulse that drives simplicity in design: to listen to the material, to respect its limits, and to uncover something honest inside it.

Conclusion

Simplicity isn’t the opposite of complexity. It’s the resolution of it. The sculptor knows that beauty isn’t in the marble, it’s in what’s left behind.

So next time you find yourself staring at a busy roadmap, or a cluttered interface, or a feature that exists mainly because someone once asked for it —-pause. Pick up the chisel. Look for the form that’s waiting underneath.

And start carving.

If you enjoyed this piece

Follow me for more articles about design-driven coding, usability, and the messy, wonderful middle ground between aesthetics and logic.

Author’s note:

I am currently deeply interested in using AI to generate both visual and text-based content. I am actively collaborating with AI on multiple platforms to explore my thoughts on what creativity is and is not.

My current approach is to collaborate with AI by using the output as a foundation upon which to build and modify.