Information Architecture Overload redux

Jen Vetterli asks the right question:

How many of these books really have something new to offer, and just how many re-articulate, remetaphorize, re-tool, etc., the same message?

One of the comments on her site asks why I have “Flash usability” in the same sentence as IA? Very simple, look around how seperate in most organizations are the interaction design, information design, usability and information architecture groups. In my experience, not very! We are talking about the same problems, Flash, HTML, xhtml, dhtml, thick client, thin client, web-based, embedded systems, handhelds, etc. All of these are devices or technologies, information is the medium, users encounter similar problems due to design designs or poor information architecture on each platform.

Jesse James Garrett comes closest to explaining the relationships of the different specializations in the creation of user experiences. (Peter Morville’s Iceberg of IA is also a great description of a model of the relationship between Information Architecture and other disciplines/techniques). Information architecture and usability are closely related. Do Flash applications not have an information architecture? Just because the amount of information displayed on my handheld is less than my desktop, does this mean that the information architecture problems are easier? Or are they made more complex by the role of the usage context plays with the device? Information Architecture isn’t something that is limited to library science, or to the Web. Information architecture is a part of the bigger picture:

How do we build systems that help people accomplish their goals in an efficient manner?

This is a very broad description of the user experience. But it encompasses visual design, interaction design, information design, emotions, play, information architecture, user needs, methodologies, documentation, strategy, etc. The idea is that we as a community need to encourage specialization but we need to see the big picture. How many in our industry can’t see the forest because the trees get in the way?

This entry was posted on Friday, November 8th, 2002 at 9:24 am and is filed under Articles. You can follow any comments to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

  • WebGirlie

    <p>David,<br />
    <br />
    While I certainly see your point, I think what perplexes me the most is that you are calling out Flash so specifically. <br />
    <br />
    Information Architecture is only a small piece in the map of &quot;how do we build systems that help people accomplish their goals in an efficient manner&quot;. Then what is the difference between an Information Architect as opposed to a Technical Writer or an Interaction Designer or a Usability Designer or even someone as basic as a programmer? </p>

  • http://lifeafterb0rg.blogspot.com WebGirlie

    David,

    While I certainly see your point, I think what perplexes me the most is that you are calling out Flash so specifically.

    Information Architecture is only a small piece in the map of “how do we build systems that help people accomplish their goals in an efficient manner”. Then what is the difference between an Information Architect as opposed to a Technical Writer or an Interaction Designer or a Usability Designer or even someone as basic as a programmer?

  • David Crow

    <p>Flash is just a tool. I call out Flash because it is used frequently to develop applications on the web. And because designers and developers have been known to create <a href="http://www.useit.com/alertbox/20001029.html&quot; target="_blank">un-usable designs</a> with Flash. No other reason.<br />
    <br />
    Specialization is a great thing, but often we focus on our specific tasks. Many of the projects I have worked on have failed because of teams not collaborating, or the project manager not understanding the big picture. <a href="http://library.thinkquest.org/3376/Smith.htm&quot; target="_blank">Adam Smith</a> argued in <a href="http://www.amazon.com/exec/obidos/ASIN/0879757051/davidcrow-20/&quot; target="_blank">The Wealth of Nations</a> that specialization occurs because it allows products to be created more efficiently. This specialization and the resulting division of labour, requires that it is possible to separate the labour of different professions. I argue that most businesses are unable to separate the roles of information architecture and usability until we, as information architects and designers, can prove our impact on the bottom line. I will write a summary of our financial impact in my next posting.</p>

  • http://davidcrow.ca/ David Crow

    Flash is just a tool. I call out Flash because it is used frequently to develop applications on the web. And because designers and developers have been known to create un-usable designs with Flash. No other reason.

    Specialization is a great thing, but often we focus on our specific tasks. Many of the projects I have worked on have failed because of teams not collaborating, or the project manager not understanding the big picture. Adam Smith argued in The Wealth of Nations that specialization occurs because it allows products to be created more efficiently. This specialization and the resulting division of labour, requires that it is possible to separate the labour of different professions. I argue that most businesses are unable to separate the roles of information architecture and usability until we, as information architects and designers, can prove our impact on the bottom line. I will write a summary of our financial impact in my next posting.