“Simplicity is the ultimate sophistication.”

― Leonardo da Vinci

A very sensible thing to say Leonardo. Elegance and ease of use are often down to simplicity, not just in terms of design and aesthetics, but also features and functions. If an object has only a few features, it’s usually easier to understand and operate and is therefore perceived as sophisticated. This has become a truism: simplicity has become a contemporary design fetish.

As a model of simplicity of design a table chair is a good example. Possibly this nice Quaker number. Look at it – it’s beautiful. For me it seems to satisfy that famous Modernist principle: form follows function.



This chair is comfortable to sit on. It’s beautiful to look at as it’s unblemished by erroneous detail. It’s made with quality wood. I know this because I can see the raw material. If I could touch it I would be able to feel the grain of the wood.

I often hear this quote from ex-lifestyle salesman Steve Jobs: “Design is not how it looks but how it works” this chair works because it is comfortable to sit on. If this chair was uncomfortable I doubt it would be held in much regard. It would be a useless object, a bit like this useless cheese grater.

Useless cheesegrater by Jeremy Huchison

But surely this is a far too simple example for our complex, ever evolving digital world. A chair is an archetype. I have been sitting in chairs before I understood what a chair, or even the act of sitting, was. And they really only serve one major purpose; I don’t wish to stand, what shall I do? I shall sit. Simple.

But can – or should – we fetishise such simplicity when remembering our complex, ever evolving, digital world? Given more complex scenarios, do we require more complex solutions to govern how we interact with the world around us or should we always – as do Leonardo and Steve Jobs – fetishise the ‘simple’?

What got me thinking about our need for complexity was the upcoming demise of Google Reader, an RSS feed aggregator that has been part of my daily ritual for a number of years now. Its retirement prompted me to check out the raft of services that were popping up in my feeds, all excitedly selling themselves as the best alternative to Google Reader.

So I checked a few out – and got a little frustrated by the amount of compromise over control I would have to give up – many of the services were offering stripped down, overviews of my feeds (usually with a prominent and mysteriously curated selection I didn’t ask for) all so that they could offer a simpler product – simpler in its use, and simpler in it’s features and functionality: and this was exactly not what I was looking for – I wanted complexity. I wanted control. I wanted all the features Google Reader offered. This made me think a little on why I liked Google Reader so – I wanted the breadth of features Google Reader offered even though I didn’t use them all – I wanted options. I wanted features. I was used to Google Reader, it was like an old friend, a comfy tracksuit, my favourite mug to drink tea out of. It wasn’t perfect (what, or who is?) but I was used to its dense landing page, its no frills Windows-like setting and management areas – quite cumbersome at times, a little ugly, but lots of features, lots of control. The design is no way perfect, but once I had got used to it, it was my pal, my friend.

We expect a lot from the devices, websites and apps we use on a day to day basis. Much more than simply wanting to rest tired legs. My phone is no longer a phone, it has a multitude of uses. Think of the last time you had to learn a brand new operating system for a new mobile or computer – you had to learn how to use it. It might appear simple now, beautifully realised and a wonder of ease of use – but that didn’t happen instantly. There was a learning curve, however short.

So sometimes we need complexity to deal with complex tasks. And sometimes we actively desire complexity. UX/Design guru-type Don Norman uses a lovely example in his book ‘Living with Complexity’ of when we actively pursue a more complicated experience.

His example is the humble cup of coffee. I love coffee but try not to drink too much of the stuff, but I always have a mug after dragging myself out of bed. I don’t want to mess about in the morning – my coffee making priority is speed. I chuck some pre-ground coffee out of a packet into a cafetiere, pour over boiling water, wait a bit, pour into a mug. Add milk. Drink. Job done. I can set off to work riding my coffee buzz.

But there is another instance of coffee making, one which requires a lot more complexion for (basically) the same result. Here is Don Normans example of a complex way to make coffee:


“Put the water in the righthand container, the coffee in the left. Light the fire under the right-hand container and when the water boils, the resulting air pressure forces the water into the left-hand container, where the water mixes with the coffee. The left-hand side is now heavier than the right-hand side, which causes a cover to drop over the flame, allowing the right-hand side to cool, decreasing its pressure. The coffeemaker’s manual says this creates a vacuum on the right that sucks the coffee back into the container, straining the beans out as it makes its passage.”


The Balancing Siphon Coffee Maker by Royal Coffee Makers.

Now you could argue that this gives you a better cup of coffee – I would imagine you would certainly be more smug when drinking a cup – but is this complexity really needed? Or is this complexity all part of the experience, a cultural ritual?

I have hopefully illustrated that sometimes there can be a need or a desire for a complex experience, or, in digital terms, a complex interface. In other words, we should not fetishise simplicity above all else. We should not always run scared of complexity and assume that we can create a ‘one click’ solution to every problem.

Instead, as designers and user experience practitioners it should be our aim to tame complexity.

There is a wealth of writing and thinking around complexity and simplicity (there are links to a couple of books at the end of this post), but as a starting point, here are a couple of pointers that I have found useful when planning and designing interfaces.

Use compartmentalization – a very logical and obvious starting point, and a method that can be applied early in the planning stages of any project. Grouping features into logical ‘compartments’ is a way of defining focus – users can easily ignore whole ‘compartments’ of features if they can quickly deduce those features that are not needed for the task in hand. Design can really make a difference with compartmentalization with colour being a very useful tool in reinforcing the differentiation of feature sets.

If you are reading this at a desktop computer take a look at your keyboard. If it’s like mine, my numeral pad is separated into it’s own unit, and most of the time I ignore it unless I need it and when I do, I shift my focus. No colour difference involved or different styling, just grouping, compartmentalization. And as a user I did a little work – I shifted my focus from one area of my keyboard to another – not a huge ask at all and proof that you don’t always have to hide away features for users to maintain focus.

An easy solution to dealing with complexity is to hide features behind buttons or actions. This technique is often bandied about as a solution but I see it more as a last resort. Introducing an interaction to hide/show features down on the importance hierarchy when your feature list is huge I can agree with. Concealing features to maintain your minimal aesthetic is style over content. Only do it if all else fails.

Don’t fall for the white space aesthetic – beautiful, minimal design is appealing, it fulfills that ambiguous word ‘clean’ – minimal, simple layout designs look wonderful and I wouldn’t want to put people off striving for this aesthetic, but the temptation with minimal design is to hide functionality behind buttons and actions, or to remove features completely. Start with the worst case scenario, keep all your functionality visible – that is the complexity you need grapple with. Chasing an aesthetic trope before you have done any planning can give you a headache later on in the design process.

One last point. Get your noise to signal ratio right,  avoid superfluous graphical elements that serve as decoration only.

So there are various methods that can be put to good use in taming complexity and designing useful interfaces – and its worth remembering that sometimes we need users to put in a little effort too.

Going back to my Quaker chair. I could take this lovely chair, paint it hot pink and varnish it. I am sure it would look quite mad, and someone out there would think it just right for their post-modern brutalist-pop loft apartment in rejuvenated Hackney. I haven’t designed a new chair but ‘styled’ an existing design. “Don’t think too much of style.” said William Morris over 200 years ago. I agree, best to design the most comfortable chair we can, one without pointless decoration or detail. One that I can sit on for the 20 minutes I might be eating my tea without having to think about the act of sitting. As long as it fits in with the other clutter in my home I would be happy. Mine’s an Americano please. Splash of milk.

Living with Complexity by Don Norman is published by MIT Press and can be found at the MIT Press website. Another designer type who has written great words on the relationship between simplicity and complexity is John Maeda, and his book The Laws of Simplicity, (also published by MIT press) can also be found at the MIT Press website. Please take a look at the work of Jeremy Huchisons at his website. You can check out the amazing Balancing Siphon Coffee Maker at the Royal Coffee Makers website.

For those of you interested I am trying out http://www.feedly.com/ for my RSS feeds.