| |
 Phase
3: Design
It's difficult to
arrange information into categories, hierarchies, and sequences that make
sense to users. But it is the single-most important part of developing
electronic documents. As information architects, it’s our specialty.
We transform information chaos into structures that help people find and
use the information they need.
What
is Info.Design's design process?
We focus on problem
solving. We seek to find ways to use words and pictures to guide users
to the tasks they hope to accomplish and to the content they are seeking.
Based on our vision
in the Scope Definition Document and the results of initial user-testing
(analysis), we use the design phase to evaluate content, chunk
it, test it, and revise it.
- Evaluating
content. When we evaluate content, we ask such questions as:
Does the document support users' needs? Does the document support the
organization's mission? How current do documents have to be? Is this
document current? Is this document accessible?
- Chunking
content. When
we chunk (group) content, we ask such questions as: Are there identifiable
groupings? Can I break these groupings into underlying structures of
information such as location, alphanumeric, time, categories, or hierarchies?
Can we emphasize related similarities? Are there special audience-related
groupings of information? Is content connected in a way that "chains"
tasks or actions?
- Testing
content. When we test content before a site is constructed,
we provide paper mockups that we use to test users' reactions to labels.
We examine the user's ability to find information that could be "buried"
under labels.
- Revising
content. Working with content offers discoveries. And working
with users always offers results different than what "experts" may predict.
So it is likely the design phase will include several opportunities
for revision.
How
do we "show" our design results?
The information architecture
of a website, Intranet, or CD-ROM will not become reality unless managers,
developers, designers, and programmers "see" the structure in forms they
can understand and use. It is the responsibility of the information architect
to provide other team members with the directions.
At Info.Design, we
use these kinds of blueprints to display structure visually:
- Site Structure
Maps—show site structure to people who don’t need all the
details.
- Site Structure
Tables—show the deep structure of the site and can also show content-management
details.
- Page/Screen mockups—show
how elements will be arranged on specific kinds of pages.
- Clickstream storyboards
and flowcharts—show how users might move through the website, Intranet,
or CD-ROM to accomplish specific goals.
- Implementation
and maintenance plans.
Action
For more information
on how Info.Design helps you design an effective information display,
direct a question to thom@thomhaller.com.
|
