Industry cries out for a new approach of user experience design

September 19th, 2007 | Under announcements, method, opinion, usability |

Thoreau Interface Design is now one year old. It’s time for a quick look behind the shoulder.

It has been a very good year, and a very instructive one too. Here are several things I realized, and some crucial points that I need to focus on for the coming years:

The industry really cries out for a new approach in usability.

The way usability specialists are commonly involved in projects proves not to be adequate in some cases.

  • Usability has too often an intellectual and hermetic approach to problems that would require creative and emotional involvement instead to be solved.
  • Usability jargon is not understood by the clients, and is often seen as a way to hide a blatant incapicity to bring real solutions.
  • Usability sometimes justifies itself by imposing irrelevant set of rules to designers and coders who see it as an obscure, intrusive and dictatorial thing. As a result they also tend to ignore the usability recomandations.

… but the needs are HUGE, and the architectural approach to interface design can really fullfill them. Here is how interface architecture should find its way accross the development process of a web service, a software or a device:

TID positioning

Notice that user testing and focus groups come during the production process to validate and re-align the concept in a more constructive way.

Notice also that wireframes are also part of the production process and they are associated with general documentation and design guides.

My recent contracts more than validated the term “Interface Architecture” applied to the discipline. The role of an Interface architect is to build and describe a complete User Experience that users and makers alike are excited to embrace.

When I started all this, Frank Gehry, the great architect, was my main inspiration; his disruptive approach of architecture brought something fresh and incredibly powerful to city landscapes. He achieved this by taming technology to his unique vision with no respect for the rules and what others do.

I really think systems and machines can be seen as work of art with strong personality and specificity. They are “places” or “spaces” or even “moments”. They convey specific messages to their users, they tell stories of their own. Some of them can be much more than commodities.

That’s the reason why I’m going to keep my distance from the academic rules of usability, and focus entirely on creativity.

From there, I really intend to widen the gap between the classic usability approach and the architectural approach. Industry needs creativity, specificity and soul. That’s all architecture is about: elegance, commodity and humanity by a smart and inspired use of the same basic building blocks.

Now is the time, as technology tends to flood us with wasted power and features, to add this layer of interface Architecture in the development process.

Best vs. Special

This year was also a year of immersion into endless and sterile arguments about Facebook vs. Myspace, Second life vs. real life, Mac vs. PC, etc. etc. The blogosphere is full of this rhetoric and I too fell into this trap.

It’s easy to be a follower and spend one’s time to influence the other followers. Social Media have this weird twist that they entice many to enter the battle for opinion leadership, thus, instead of setting new rules, just making new kings with very questionable legitimacy.

While everyone is guessing, with a weird fascination, who’s is going to rule the web, it clearly appears that the mass of users actually don’t give a damn; and they can easily deal with a diversity of experiences. People can appreciate many different places, forms and stories. There are actually no rules, no best practices, only good propositions. It’s an ecosystem out there, not (only) a battle field.

So I won’t try to be the best usability specialist in town, but I will increase my difference, polish my method and make my customers proud of what they get. I’ll put all my energy in being creative for people who need something special for their products.

Tool

Speaking of Frank Gehry, this guy developed his own CAD tools to build the crazy shapes and volumes he has in mind.
There’s obviously a need for such a tool in interface architecture to fill the gap between designers and coders. This tool should free the creative process by taking care of the building aspect of things.

It’s a crucial challenge, it’ll take time, and I’ll need the help of people interested in breaking some rules.

… and, THANK YOU.

5 comments

1

Congrats Guillaume and happy birthday to Thoreau ID!

2

Hey thanks Marc :)
Hope everything works great at StandOutJobs.com

3

hi guillaume
i like this post, it’s very refreshing and i encourage you to go into this path. Montréal need more people like you in interface design and architecture.

if you can, you should post about what you are doing and what is the vision behind it. people would understand more about what is your specifity.

i am sure the best is still ahead. so i am wishing you all the best :-)

4

Hey Guillaume, congrats for your first year “on your own”!

J’ai apprécié travailler avec toi cette année et ton approche créative et ouverte sur les rôle d’architecte d’interface en est qui va faire ta marque cette année, c’est une prédiction facile à faire!

The hard part will be documenting and commicating that, my guess is that you will need to expand a bit and find others with similar mindshare…

5

Thanks Sylvain & Heri.
My “specificity” resides mainly in the method and, as Sylvain noticed, the method is far from being perfect :( … Anyway I did some improvements in the way to communicate by doing interactive prototype clients can “play” with and get a better feeling of what they get.

That’s the kind of tool i’d like to develop: a kind of map allowing to circulate within the information architecture, zoom to screen level, add notes and documents to screens so that architects can design the UX and experience it live with the client.

Why this ? Because of documentation: documenting a user experience in a linear and hierarchical way (chapter, section, sub-section, etc + wireframes for each use case) is a waste of time and money. It’s to hard to read, too long to write, too inaccurate. It’s like representing a globe on a flat paper: you lose a lot of data. A web service is a much more complex and multidimensional “volume” than a globe, hence the necessity to have a tool to describe it.

I heard that UML now proposes dedicated tools to describe UI. Do you know more about that ?

Leave a comment