Let’s face it. We live in a complicated world. Every day people are bombarded with technology and information. Much of it adding value and meaning to our lives. Much of it making our lives easier. Some of it bringing real joy into our world. But it can be overwhelming and, well, complicated. And that’s just assuming we’re talking about those complex things we enjoy. Too much of that complicated information and technology is valueless, over-complex and a daily drain on our sanity.
We need more simplicity—more understanding and ease of use—while at the same time maintaining the value (and delight) that can be found in a complex world. It’s a difficult balance to strike and one I think about almost every day.
The Value in Complexity
Some of my very favorite things in life are complicated. My favorite books, music, games, toys, people—most of them are complicated. Complicated things can bring with them a lot of joy. Complexity, when properly balanced, can really delight.
To a certain degree value (and meaning) come hand-in-hand with complexity. That’s not to say that I don’t find value in uncomplicated things, no, only that many of the things I value are complicated and to remove that complication would also remove that value.
At the same time, too much complexity (even complexity full of value) can be overwhelming. I find that as my life and work become more complicated, the harder it is for me to enjoy those other complicated things I consider good. I have only the energy to deal with so much complexity in my life! As well complexity that doesn’t add meaning, or value…well, that’s complexity that nobody needs.
In a way there are two different kinds of complexity. The good complexity that comes with meaning and value and the bad complexity that just makes everything harder. Along the same lines there is also good simplicity, which makes things easier and bad simplicity that removes or obscures meaning and renders something dull and useless.
I’ve been on a personal mission of sorts to eliminate “bad” complexity from
everything I do so that I can better enjoy that “good” complexity and hopefully help others in the process. By making my work easier for me to do, while at the same time not removing the value of that work, I’ve got more time and energy to do other things.
For example, the less time and energy I spend using the technology I use every day, the more time I can spend reading, playing games, spending time with my overly-complicated friends or enjoying Rome or Lost.
The Value of Simplicity
There is no doubt in my mind that making something easier to understand without removing value or meaning is a good thing. I don’t think that can be argued. So, in general, simplicity is something I’m always striving for. I try to make things as simple and easy as possible, again, while not removing value or meaning from them.
(This goes for design, business, process, etc. Pretty much anything, and it’s much easier said than done!)
On one side you’ve got complication, value and meaning and on the other you’ve got simplicity and understanding. Those things that bring true delight have all of this in good balance. The now classic technology example is the iPod. It’s a very complicated device with lots of value that, largely because of it simple design and ease of use, brings delight to millions.
This is our goal when thinking about usable, peoplecentric technology; making things as easy to understand and use as possible, while at the same time maintaining (or better yet, adding to) their value and meaning.
Often times by removing unneeded complexity we’re actually revealing the value or meaning of a thing.
I’ve been saying it for years now; technology should work for people, not the other way around. Sometimes all it takes is a bit of simplicity to help someone understand, or see the meaning in a system, message, interface, etc.
But complexity isn’t only a design and technology concern for me. The same goes for the business of consulting—we’ve tried to structure Blue Flavor so that we’re as easy to work with as possible. We do our very best to make our process as simple and straightforward as possible and are always looking for ways to eliminate unneeded complication from it. Hopefully to the delight of our clients!
The work we do is by its very nature complicated and will likely have to remain so. (It has value and meaning!) However, the processes around our work can almost always be improved. Think about how you work and how much of what you do in your day has meaning and value. Now think about those things that don’t have meaning yet take your focus away from those things that do. My guess is you might begin to see where somethings you’re doing can be simplified.
Obviously “meaning” and “value” can be somewhat subjective but the point I’m trying to make is that when it comes to work, life, business, technology, design, etc. it pays to take a long look at what you’re doing on a regular basis and see where you can remove “bad” complexity.
In today’s world where technology, information and complexity (both good and bad) play an ever increasing (and often unwanted) role in our lives, there is a serious need for balance and simplicity. We have to begin to eliminate meaningless and valueless complexity wherever it can be found to ensure we can get the most value, meaning (and delight) out of our lives.
Complexity of systems is a real challenge, how to make them simple to use. The successful solutions are those that focus on the user and that are not constrained by what is seen as technically challenging or impossible.
As a developer I’ve often found myself limiting the way something works simply because of a technical reason, and have been challenged by my work colleague as to why it works that way.
It takes further effort and perseverance to make sure that an application works well from a users perspective rather than what is easier to code! It helps to have non-coders involved in the development process as they have less technical restrictions on their view towards a project.
Rick - I totally agree. Often times when you’re designing for use it turns out that what is easy to a user can be much more complicated for a designer or developer. And that’s assuming you know what is easier for a user.
Complexity and Simplicity aren’t always at odds; sometimes you’ve got to do something complex to make something simple.
Rick - I agree that keeping users at the forefront of your mind when you’re developing is crucial.
When I’m designing or coding and run into an issue I’m not quite sure about I like to do some “guerilla” usability testing. Which basically means I go around to a few people in the office and see if they get what I’m trying to do. It works great for really small tasks. I usually ask questions like, “Do you get what that icon means?” or “When you click there what do you expect to happen?” They probably take an extra 10 minutes at the most but can really help keep you on track.
I like to think something which cannot be simplified more (without losing any value) as being simple. Anything else is either simplistic, or “complex” (in most cases, it is more a matter of incorrectness, than real complexity), and should be avoided or improved (except for specific uses -for specific users-, which might justify it -at least temporarily-, of course).
As such, this is not at all, a matter of balance between complexity and simplicity. It is only a matter of striving for simplicity, which seems a goal far more simple to achieve ;)
Generally, it is mostly about avoiding prejudices (which are numerous, and might not all be easy to “unlearn” -for example, seeing progress as adding new random things, rather than as thinking more correctly, including simplifying things, which, today, is mostly about removing a lot of things, and improving the general experience), and possessing the appropriate knowledge (which is not always directly available, as the current system push people to try to complexify simple things, adding more and more incorrectness to the subject).
This often relates to having enough time to learn and do things correctly (and to wanting to take the time to do it, as a lot of people simply don’t care -again, because of the current system, either because of pseudo egocentrism, because of prejudices, or because they are not doing the job they’d like to do).
In all cases, the current situation can’t go on forever, and we are indeed seeing quite a few people talking about simplicity (or at least, about major problems in the current computer world -well, it is however a global problem of today society), in the recent months (or maybe I’m just noticing it more…), and I like this.
I’m still 21; I hope to be able to greatly contribute to this change (being otherwise rather lazy ^_^ -doing anything more than what I would do in an idealistic society, is not easy for me, though I decided to be more active).
While I may be splitting hairs (hey, why not) I mark a difference between Complexity and Complicatedness.
To me, <a href=”http://usabilityworks.org/2006/12/13/simplicity-complexity-and-complicatedness/” rel=”nofollow” >these are not interchangeable words</a>.
Something that is complex doesn’t imply it isn’t easy to use. Something complicated does imply not easy to use. Or I infer they do. :)
I agree with your premise though. Often I get odd looks in meetings when I respond with Why? to statements like, “We need to keep it simple.”
I’m the usability guy; I should think that <strong>everything</strong> should be simple, right? Not so much…
Matthew - I think it is spitting hairs a bit and I suppose you could debate the semantics of complicated vs. complex all day long (to me they are pretty much interchangable) but I get your underlying point.
Something (a system, interface, etc.) can be complex and still be uncomplicated as far as use goes. Very true.
I was also going to make a comment about complex / complicated as I tend to agree that there is a difference in their usage, at least in how people interpret them. But I think overall in your article the point you’re getting across is made.
re: complex vs. complicated. Not to belabor this, but I’m pretty sure that technically they mean the same thing, and regardless it’s all semantics and I don’t want to get into a semantical debate.
However, in order to remove confusion I want to explain my thinking and my choice of words here. I think it depends on what you’re talking about. For example, when talking about a person, or relationship, I’d say “complicated” not “complex” regardless of it that relationship was good or bad. For a system or say a Web application, I’d probably go with “complex” when talking about the underpinnings and maybe “complicated” when talking about the interface.
I guess the problem with splitting those hairs is that you then apply a negative connotation to the word “complicated” and a positive connotation to “complex” which, IMHO, doesn’t always make sense. Not that I don’t get Matthew’s point, just that I don’t think of it that way myself.
ANYway - what’s really important to note here is simplicity should be about adding or revealing value — the key to all this is value and/or meaning.
I guess knowing when to use either word is a complex / complicated issue? ;)
Very thought provoking entry, simply stated.