|
Located: research
topics > site planning
The role of information architecture in web
site planning (section 2)
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 some
of the key components of information architecture and in particular
principles of different types of organisational schemes.
Contents:
Section
1 - Role of information architecture. Section
2 - Key issues in site planning. Section
3 - the site planning process.
Chapter 3 - organising information
Systems of classifications for the very
foundation of our understanding (p22). Challenges inherent in organising
info are not new - but are now forced on more people each day through
the internet. Issues and difficulties include: ambiguity (classifications
based on language), heterogeneity (collection of objects composed
of unrelated or unlike parts), differences in perspective (personal
systems or views), internal politics (managing their impact).
Organisation schemes - defines the shared
characteristics of content items and influcences the logical grouping
of those items (p26). There are different types:
Exact organisation schemes: (eg alphabetical
phone book) Divide info into well defined and mutually exclusive
sections. Pros: good for 'known-item' searching, where you know
what you're looking for. Cons: bad if you don't know the specific
name of the resource. Include alphabetical (book indexes,
phone books, libraries), chronological (press releases, history
books, diaries and television guides) and geographic (travel,
news and weather, political, social and economic issues).
Ambiguous organisation schemes: (eg
library 'subject' category, as opposed to 'title' or 'author' category
) Divide information into categories that defy exact definition.
Pros: more useful and more commonly used (backed by extensive library
research) - particularly when we don't know exactly what we're looking
for. Supports a more associative learning process. Cons: Difficult
to design and maintain, difficult to use. Include topical
(yellow pages, newspapers, academic courses), task oriented
(desktop software applications, directed web sites), audience
specific (some education sites, intranets - can be open or closed),
metaphor driven (desktop computer interface, virtual office/library/space),
hybrid scheme (most web pages).
In designing a topical organistional scheme,
remember that you are defining the universe of content (both present
and future) that users will expect to find within that web site.
Task oriented when its possible to anticipate a limited number of
high-priority user tasks. Audience specific when a need to break
sites into smaller subsets. Metaphor driven to help users understand
new by relating it to the familiar - and helps with intuition.
Hybrids
go against the power of a pure organisational scheme - to suggest
a simple mental model for users to quick understanding. Where multiple
schemes must be presented on one page, each should be presented
separately to maintain its integrity. (p36) This
suggests that one of the principle powers of an organisational scheme
is in its ability to be recognised by a user, and that combining
schemes dilutes their power as an information device. It could also
be assumed that various schemes would be better presented in differing
ways - an example may be an audience specific-scheme which may be
verb-driven, as opposed to a topic scheme which may be more noun-driven.
Organisation structures: (eg ) Most organisation
structure that apply to web sites and intranet architectures include
hierarchy, database-oriented and hypertext. In many cases, it makes
sense to use all three.
Hierarchy: a foundation - simple and familiar
way to organise information. Categories should be mutually exclusive,
and there should be balance between breadth and depth. Breadth -
seven plus or minus two rule (more than 10 options can overwhelm
users) and depth - more conservative (4 to 5 levels maximum). Finally,
don't let hierarchy constrain development.
Hypertext: provides greater flexibility,
but can created disorientation. Without context, users can become
quickly frustrated and overwhelmed. Additionally, hypertext links
are often personal in nature. It is often more sensible to design
the information hierarchy first and then identify way in which hypertext
can complement the hierarchy.
Relational database: Allow the use of searches,
better content management and personalised content using records
and fields. Often better to use databases as subsets of structured,
homogeneous information within a broader website.
Chapter 4 - designing navigation systems
A complementary navigation system provides
context and to allow for greater flexibility of movement within
the hierarchy of a site. (p47)
The use
of standards in navigation can greatly influence usability, and
the success users have within a site. Many site designs sacrifice
usability for aesthetics and belie a lack of consideration for the
user and the environment. (p49) Web browsers are an integral part
of browsing and their navigation systems are integral to the user's
navigation experience. This view
concurs with many of those voiced by Fleming, Nielsen and Tognazzini
that navigation and site usability is enhanced measurably if popular
conventions are used.
Typically, navigation should strike a balance
between allowing lateral and vertical navigation of a site, and
holding the integrity of a hierarchy. (p52) Different navigation
systems include:
Hierarchical navigation: typically the primary
navigation system of a site.
Global navigation: navigation that spans
the site
Local navigation: typically used for subsites.
Should complement, not replace, global navigation systems.
Ad Hoc navigation: more editorial than architectural.
Generally placed throughout content.
Nielsen talks about different types
of links (embedded, structural and associative. He suggests that
of these, associative are the most effective in lifting site use
- presumably because they offer the ability to view more content
aligned to their current topic of interest. (more
about this concept...)
This forms the basis of the link
between defining user goals (Fleming), effective navigation (Nielsen)
and the concept of structure planning highlighted here. It adds
weight to the proposition that users will arrive at a site location
seeking information, then may browse as their interest is piqued
by like topics, then seek to return and resume their information
search. This scenario relies heavily on a functional navigation
system. (The concept is discussed further in the essay 'Satisfying
site design'...)
Frames can cause problems by violating the
page model of browsing - thereby disabling many browser functions
such as bookmarking and using the back button. (p62) They will also
slow display speeds and can create many design challenges.
Remote navigation systems can include tables
of contents, index, site map, guided tour,
Chapter 5 - labeling systems
Labeling should make sense to the general
public and be descriptive. (p74). Successful labeling mirrors the
language and thinking of site users, not owners. Particularly iconic
labeling, where there are only a handful of consistently agreed-upon
symbols. Few sites use icons without accompanying text because of
this issue. (p85).
Chapter 6 - searching
The different types of searching: (p102)
Known-item searching: clearly defined and
a single correct answer
Existence searching: having an abstract
idea or concept, and trying to find if the matching information
exists.
Exploratory searching: knowing how to phrase
the question, but not being exactly sure what you're hoping to find.
Comprehensive searching: attempting to locate
everything available on a particular topic.
Searching and browsing are often
interlinked. And both are by nature iterative - users will make
a first attempt, learn something, refine and try again. (p104).
This is typically called associative learning. The challenge is
to design site architecture to support the most common searching
and browsing approaches in a smooth and integrated way.
 
|