World's fastest modeling job, or information architecture: What is it? The multidisciplinary adventures of two Ph.D. students
Bulletin of the American Society for Information Science, Jun/Jul 2000 by Denn, Sheila O, Maglaughlin, Kelly L
The last thing that Ph.D. students want to hear is that we need to take more courses. Yet the ASIS Summit 2000 on Defining Information Architecture left us with what seems a lifetime agenda. Philosophy, literature, anthropology, landscape architecture and ecology were just a few of the suggestions mentioned as desirable preparation for information architects - all in addition, of course, to our current full program at the School of Information and Library Science at the University of North Carolina - Chapel Hill (UNC-CH). One of the major themes that emerged from the summit is that information architecture truly is a multidisciplinary area. The people in the profession do indeed come from a wide range of academic and career backgrounds. Becoming an information architect is very much an art and not a science. There is no set path to get there.
Which is not to say that our program at UNCCH is not excellent basic preparation. Practicing information architects really do use the skills we work on in our classes on systems analysis, user interface design, database design, information retrieval and communications. As an even more exciting prospect, the demand for information architects is growing, ensuring that there will be jobs available in this field when we graduate.
One of the goals of the summit was to bring together academic information scientists and practicing information architects to discover common ground and to make an attempt to formulate a definition of information architecture. First we will discuss some of the major themes that emerged from the sessions. Then we discuss the process we undertook, along with the summit organizers and other volunteers, to synthesize a model of information architecture, the feedback we received about the model and the implications of the model-building exercise for the field.
The summit was kicked off by Louis Rosenfeld, president of Argus Associates, who presented a model of information architecture that served as a jumping-off point (Figure 1).
This model is meant to represent information architecture as the intersection of the content and applications included in the architecture, the users who will be using the architecture and the context (including business goals, politics, culture, etc.) in which the architecture exists. Subsequent speakers were invited to use this model to frame their talks or to propose different models that more closely mirrored their own experiences.
Another theme that came up repeatedly during the summit was the distinction between the client for whom one is developing an information architecture and the end users of that architecture. This arose, in part, as a result of the demographics of the summit. Unlike gatherings like the ASIS Annual Meeting, there were a large number of people from outside the academic world working on information architecture as part of consulting firms. In this light, the concern for differentiating the client from the end user makes good sense and was reflected in the model that was developed and proposed at the summit.
Another theme that emerged was the close interrelationship between information architecture and user interface design. A number of speakers stressed the importance of involving interface design staff early in the process of designing the underlying architecture of the system, because the underlying structure will necessarily influence what can be done at the user interface level.
One of the most interesting aspects of the summit was examining the variety of fields that are contributing to work in information architecture. These include information retrieval and librarianship, visual design, HCI and usability engineering, technical communications, interface and interaction design, markup and data modeling, anthropology and ethnography, and computer science, just to name a few. Information architecture is drawing practitioners from such a diverse array of fields that there is an increased need to define information architecture itself as a field. As we continue to move into ever more multimodal information spaces, including multimedia elements and new visualization technologies for data beyond simple text, the field will increasingly be called upon to provide more complex solutions to more complex challenges. All of the fields described above have much to offer to information architecture, but any one approach is incomplete for designing a complex information system.
The notion of purpose seemed to be an important one. Alison Head, principal of Alison J. Head & Associates, felt so strongly that purpose was an important (and often overlooked) element of information architecture that she spoke to a "purpose crisis" in organizations engaging in information architecture. Purpose can be a difficult issue, because often there are competing purposes - sometimes even within the client organization that has requested a site. In addition, the organization completing the architecture needs to be mindful not only of the client's purpose for the site, but also the purposes that users will have in visiting the site. This problem is compounded because, as Mark Hurst, founder and president of Creative Good, mentioned in his talk, we as information architects are not our users, nor are we like our users. So it is not possible to divine what kinds of purposes the users of an information architecture will have without examining the users carefully.
Most Recent Reference Articles
- Not Part of the Public: Non-indigenous policies and the health of indigenous South Australians 1836-1973
- Homophobia: An Australian History
- Social inclusion and sport: culturally diverse women's perspectives
- Who to serve? The ethical dilemma of employment consultants in nonprofit disability employment network organisations
- Vocational education, self-employment and burnout among Australian workers

