Long before anyone was looking for “godfathers” of information architecture, our fellow species were wrestling with some of the same problems we face today. The real godfathers of information architecture, as it turns out, emerged a very long time ago with the earliest origins of life on this planet.
Jesse James Garrett’s “The Elements of User Experience” diagram has become rightly famous as a clear and simple model for the sorts of things that user experience professionals do. But as a model of user experience it presents an incomplete picture with some serious omissions—omissions I’ll try address with a more holistic model.
Somewhere in the process of evangelizing user-centered design, user experience professionals seem to have forgotten the value of vision-driven design, which can be equally important in making sites and software relevant and desirable. We need to integrate both approaches.
As users and builders demand more and more richness from the Web, we need to re-evaluate the technology that 99% of it is built on. It seems no matter how sophisticated our back ends get, the front ends remain stagnant. What other options are there? What are the requirements that we as user experience designers face that newer technologies miss the boat on?
What happens when web designers really “get” designing for the web? Sarah Horton, co-author of the Web Style Guide, ponders the meaning of beauty and quality in the context of being a good web designer.
At this point in experience design’s evolution, satisfaction ought to be the norm, and delight ought to be the goal. As design professionals, how do we create opportunities for customer delight?
With all the bickering over the “right” tools, we lose sight in these discussions of the fact that we already have the perfect tool: our brains. The knowledge, expertise and skills to solve problems are right between our ears.
Part of me feels for Jakob Nielsen for the grief he’s taken over deciding to work with Macromedia after declaring “Flash 99 percent bad.” After all, the pressures and temptations to provide simple answers to complex issues are ones we all face in our professional practices.
As computers and digital devices increasingly insert themselves into our lives, they do so on an ever increasing social level. Designers need to understand the context of use and include the whole of a user’s experience into the solution when creating a computer interface.
Not so long ago, on my personal site I posted a little entry on design. And a comment was made: “IA is not design.” This sentence has sat vibrating in my head for months. It speaks of bravado in the face of fear. But why should Information Architects fear design?