Located: research topics > site planning

The role of information architecture in web site planning (section 1)

Authors: Moreville, P. & Rosenfeld, S. 1998

Abstract: This research is taken from the book Information Architecture for the World Wide Web. This section looks at information architecture and the part it plays in web site planning - particularly in addressing usability issues.

Contents: Section 1 - Role of information architecture. Section 2 - Key issues in site planning. Section 3 - the site planning process.

The web is too new for anyone to feel secure in claiming that there is a right way to do things (xiv)

Chapter 1 - what makes a site work

Brainstorm these questions & put on whiteboard: (p3) 1. what do you hate about the web and 2. What do you like about the web. Typically break down answers into three groups - technical (interactivity/bandwidth), look and feel (design/funcitonality) and other (navigation/finding info). The 'other' category is generally related to information architecture.

Typical 'hates' are (p4): can't find info - inconsistency/ poor labels/ poor navigation, poor graphic design and layout, gratuitous use of technology, inappropriate tone for audience, designer centredness, under construction, lack of attention to detail.

Typical 'likes' are (p4): good aesthetics, big ideas - mind challenging, utility and usefulness, finability - good navigation, and personalisation - aiming for a wide audience.

Like anything else - we take success for granted. Poor design frustrates us. Quality is often quiet, passive and transparent (p7). This is particularly relevant in the site design process. Because information architecture and navigation planning is so intangible, if it works it is taken for granted - therefore affecting its importance in the process. A challenge for site planners is ensuring that the information architecture process takes as much relevance as planning for the design and technical process.

Chapter 2 - role of the Information Architect

Main job of information architect is (p11):
· Clarify mission and vision for the site - balance needs of owners with that of audience
· Determine content and functionality
· Specify how users will find info by defining its organisation, navigaiton, labeling and search systems
· Map out how the site will accommodate change and growth.

It could be argued that planning in these four areas are equally as relevant to site graphic design and site technical design. If so, would a collaborative approach in determining these areas make more sense.

Each site needs a definition of what it will be and how it will work (p11). This can include various target audiences, site goals, content and functionality required, and the big picture.

Many thorny issues including: which goals are more important? should the site be informational, entertaining or educational? Should there be one main page for all audiences, or one for each? Should the architecture organise information by topic, by function or some other way? Who should own and maintain the info? What kind of navigation makes most sense? If these issues are not resolved before the site is built, they are ultimately placed as a burden on site users. (p14)

Information architecture is about what's not obvious. Users don't notice information architecture of a site unless it isn't working. Poor information architecture makes busy users confused, frustrated and angry. (p12)

There are multiple models of finding info - including known item searching, casual browsing. (p12)