Information Architecture for the World Wide Web, Second Edition

Chapter 15. Building an Information Architecture Team

Since even the title of this chapter may incite quiet fury among our colleagues, we’d like to begin with a few qualifications. First, our focus on staffing an information architecture team in no way suggests a desire to build walls between roles and disciplines. To the contrary, we are firm believers in the value of closely knit, multidisciplinary teams. Second, we fully recognize that our description of an information architecture dream team is provocative and ambitious. The complete vision will be realized only in the largest of projects and organizations.

Our intent is to push the envelope, and to explore scenarios for the small but influential community of professional information architects. How will the world’s most massive sites be designed and managed? Who will do the work? Will it be outsourced or done internally? Will staff be centralized or distributed?

These questions loom large in the minds of many. Should I become an in-house information architect, or is it better to stay in a consulting firm? Innie or outie? Which is safest? Where can we expect the most growth?

Intranet and web managers are asking the same questions. How do I get this information architecture designed? Do I need a permanent staff, or can I get by with a consultant? Either way, who do I hire? What mix of skills is required?

These are hard questions. They drive debates about the role and discipline of information architecture. They force us to imagine ...