Implications for Multimedia Authoring

"Information Architecture for the World Wide Web" by P. Morville & L. Rosenfeld

Chapter 1: Defining Information Architecture

The authors define Information Architecture (IA) as a complex disciple with multiple definitions. They liken it to the structural design of shared information environments. They describe it as the process of organizing and labeling information to make it searchable and findable. it is the process of making data useful by placing it in a framework that facilitates access.

The authors address the challenges surrounding language and representation that impact IA, describing the relationships between words and meaning as being largely subjective to the individual. I've often struggled with how to label categories of a website and now understand why that is. Is the label appropriate and understandable for the intended audience? Does it truly describe the content encompassed in that area? Organizing information for other users poses challenges that often are not understood by users - especially in the case of well-designed websites. The time and effort that goes into IA are invisible and unnoticed as they occur behind the scenes.

I especially like the section on "Why Information Architecture Matters." Having worked in a corporate setting, there is a constant rush to complete IT projects as quickly as possible. The least amount of effort, in my opinion, is devoted to analysis and design. As long as the functionality is there and the information is somehow accessible (albeit inefficiently), project managers feel they've achieved their goals. If only they knew the future costs that users and the organization would incur because of the poor planning of a site's information design. These costs include:

• The cost of finding information
• The cost of not finding information
• The value of education
• The cost of construction
• The cost of maintenance
• The cost of training
• The value of brand

As an Instructional Designer/Trainer I have been asked to teach classes on how to search for information on company Intranets. Our director is now concered that we will need to teach classes on how to use a Shopping Cart program where parents register their daughters for camp and other Girl Scout events. I can't help but feel that training in the context of web sites should not be necessary if the Information Architecture is well thought-out. This leads to Chapter 2, which describes information architecture as a blend of context, content and users. Without considering all three factors and representing them in a site's design, chances are your site will incur some of the aforementioned costs in the future.

Chapter 2: Practicing Information Architecture

The practice of Information Architecture involves the relationships between users, content and context.

Context refers to the organization for which the site is being built. Each organization has a mission, goals, strategy and culture that the site's design should reflect. The design must also reflect the limitations of the organization as set by the physical and technological infrastructure, budget and policies and procedures.

Content is defined as the "stuff" that makes up a site. Important considerations surrounding content include ownership, format, structure, metadata, volume and dynamism.

Users refer to the people who will use your site. It is critical to take into account their goals and preferences. If you do not target your audience properly, your site will remain untapped.