simple The more I work with interaction design the more I home in on the same mantra – simplify. This works on everything, from the most complex situation down to really basic UIs. Actually it’s a lot harder for the basic situation as they are already simplified. But it always pays off in the usage.

In the current project we have a very complex structure that, currently, are presented to the user. Developing for it, we find ourselves discussing it over and over again and to me this is a big warning sign. When we, that really should understand every detail, misunderstand the concept again and again, how hard will it not be for the user, and this really shout simplify! We should never be allowed to expose this internal complexity our we will end up with a usage nightmare. In the same way you really don’t need to understand every sprocket and spring in an old watch to tell time.

And here I am, working real hard to wrap my head around the end result and the goal  the user want to experience. I focus all my effort to visualize this result in the simplest possible way. I remove redundant and excessive information. For every piece of data, every column, button and link, I ask myself: is this needed to complete the task? If not – I hide and maybe, but just maybe allow the user to reveal on demand. When I think I’m done I go through it again…

But it’s the same thing with everything around us. If you read my post on simplified licenses it’s obvious that this applies to other areas. And it may seem obvious, but how come run into the same overcomplicated situations? Why is the GPL 3 license using 5700 words? Obviously, it cannot hurt to be reminded - make simplify YOUR mantra…

// Håkan Reis