Chapter 2 - Basic Principles of Information Architecture
Chapter 2 - Basic Principles of Information Architecture
BASIC PRINCIPLES
OF INFORMATION
ARCHITECTURE
2
Introduction
Information Architecture is not just for websites and intranets,
and is relevant to;
3
Menus
■ Many applications, both on and off the web, use menus to
provide access to functions and tools. Menus are a perfect
example of IA – each grouping together similar functions.
4
Data-heavy applications
■ The data fields of internal business applications are grouped
in sensible ways so people know what each set of fields is
about and what to do with them.
5
Classifying
■ Many applications are about classifying data so people can
find and use it. For example, a document management
system usually needs you to classify each document
according to a number of criteria.
6
Mobile
■ If you are designing a mobile app, you’ll need to do some IA
work. A lot of mobile apps work as a hierarchy, with menus
providing access to different parts of the application.
7
A principle to guide to design
information architecture
■ The information architect’s primary focus is the structure
itself and secondarily the user interface representing the
structure on screen (I make site maps and flow charts)
■ The information architect has a good understanding of how
people want to relate to the content and functionality
contained in the structure (I’ve done my research)
■ The information architect has a good understanding of the
range of content and functionality to be supported by the
structure (I’ve inventoried the content)
8
8 Principles of Information
Architecture
■ The principle of objects
– Treat content as a living, breathing thing, with a lifecycle,
behaviors and attributes.
■ The principle of choices
– Create pages that offer meaningful choices to users,
keeping the range of choices available focused on a
particular task.
■ The principle of disclosure
– Show only enough information to help people
understand what kinds of information they’ll find as they
dig deeper.
9
(cont.) 8 Principles of
Information Architecture
■ The principle of exemplars
– Describe the contents of categories by showing
examples of the contents.
■ The principle of front doors
– Assume at least half of the website’s visitors will come
through some page other than the home page.
■ The principle of multiple classification
– Offer users several different classification schemes to
browse the site’s content.
10
(cont.) 8 Principles of
Information Architecture
■ The principle of focused navigation
– Don’t mix apples and oranges in your navigation
scheme.
■ The principle of growth
– Assume the content you have today is a small fraction of
the content you will have tomorrow.
11
Why is it important to be
able to visualize information
architecture?
■ Many people don't believe that things exist until they can
see them.
■ The field is abstract, and many who might conceptually
understand the basic premise of information architecture
won't really "get it" until they see it and experience it.
■ A well-designed information architecture is invisible to
users (which, paradoxically, is quite an unfair reward for IA
success).
12
Look at these websites:
■ https://gustavus.edu/
■ https://uitm.edu.my/index.php/en/
13
Can you find these elements
in those websites?
■ site's visual design
– site's colors
– typeface choices
– Images
– the number of columnsand their widths changes
throughout the page
■ site's interaction design
– Mouseovers
– pull-down menus for "Go Quickly To" and search
options.
14
Approaches to visualize
information architecture
■ Top-down Information Architecture
■ Bottom-up Information Architecture
15
Top-down Information Architecture
17
Top-down Information Architecture
18
Bottom-up Information Architecture
■ Content itself can have information architecture embedded within it.
■ By looking closely to the content, it is possible to see information
architecture even when it’s embedded in the core of the content.
■ And by supporting searching and browsing, the structure inherent in
content enables the answers to users’ questions to “rise” to the
surface.
■ Content structure, sequencing, and tagging help users answer
questions like:
– Where am I?
– What’s here?
– Where can I go from here?”
19
Bottom-up Information Architecture
20
Information Architecture
Components
■ Organization systems
– How we categorize information
■ Labelling systems
– How we represent information
■ Navigation systems
– How we browse or move through information
■ Searching systems
– How we search information
21
Organizing System
22
Organizing System
1. organization schemes
✓ An organization scheme defines the shared characteristics of
content items and influences the logical grouping of those items
1.1 Exact organization scheme
✓ alphabetical
✓ chronological
✓ geographical
43
Call things by their correct name
■ One of the hardest issues you’ll come across in labelling is whether to use
‘correct’ terms or those your audience understands. Sometimes these two
things align with each other naturally.
Yoga journal shows the Sanskrit and English name side by side (yogajournal.com)
Consistent
■ When it comes to terminology, consistency is very important. You need to be
absolutely consistent within your own set of content.
■ If there’s a term everyone in your industry uses, and your audience is likely to
know it, just use it. Let people use the knowledge they’ve learned outside your
site to make life easier on your site. You can’t go wrong with simple things like
Contact us, About us and Our services.
Use terms that your audience
uses
■ You should make sure your labels are accurate for the content
they’re describing, you’ll often have plenty of room to work
within this, and many ways to describe something. When
making this decision, think about the terms your audience
knows and understands, and use these.
■ Be careful with jargon as well
46
Clear as possible
■ Clear labels are obviously better than unclear labels. Here are a few
easy ways to make sure your labels are clear. Use as long a term as you
need to describe the content or idea.
■ Use words that are as concrete as possible. For example, don’t use
Small, Medium and Large if you can better describe what these labels
actually mean.
Where to get ideas for labels
■ You can get ideas for your labels from a number of places:
– Content: look at the words used in your content and the labels they
suggest.
– User research: your research will contain hundreds of words that
describe how your audience phrase ideas and concepts. Make
sure you look at your search logs – you’ll see exactly what people
are looking for.
– Card sorting: in a card sort, the last step is often for people to
provide a label describing what the group of cards is about. I often
find these labels a bit long or informal to use, but they can give you
some ideas.
– What everyone else does: look around at competitors or other
content like yours and see what other people do. If there’s a
consistent approach, you can do your users a favour and
use that.
Expect Changes
■ Finally, expect labels to change over time. As you add more content to
a site, or move things around, labels will need to change as well.
Language is subtle and slight changes in words may be needed over
time.
■ For intranet work, as organizations change the labels in common use
also change. Older employees remember and use the old labels, but
new employees will have no idea what to use. Keep on top of the
terms being used and adapt over time.
■ Keep an eye on how people are using your site – in particular, watch
search terms and see if there’s any change in the terms people are
using over time.