Learning Objectives:
1. Design a user test.        3. Evaluate a user test.
2. Conduct a user test.     4. Document results.

Task: 1 of 2

Weight: 60%

Due Date:  Week 6

Information architecture (often abbreviated "I.A.") is the practice of structuring information (knowledge or data) for a purpose. These are often structured according to their context in user interactions or larger databases. The term is most commonly applied to Web development, but also applies to disciplines outside of a strict Web context, such as programming and technical writing.

In the context of web design (or design for related media) information architecture is defined by the Information Architecture Institute as

1. The structural design of shared information environments.
2. The art and science of organizing and labeling web sites, intranets, online communities and software to support usability and findability.
3. An emerging community of practice focused on bringing principles of design and architecture to the digital landscape.

An alternate definition of information architecture exists within the context of information system design, in which information architecture refers to data modeling and the analysis and design of the information in the system, concentrating on entities and their interdependencies. Data modeling depends on abstraction; the relationships between the pieces of data is of more interest than the particulars of individual records, though cataloging possible values is a common technique. The usability of human-facing systems, and standards compliance of internal ones, are paramount.

The term information architecture describes a specialized skill set which relates to the management of information and employment of informational tools. It has a significant degree of association with the library sciences. Many library schools now teach information architecture.

- WIkipedia

 

Organizing functionality and content into a structure that people are able to navigate intuitively doesn't happen by chance. Organizations must recognize the importance of information architecture or else they run the risk of creating great content and functionality that no one can ever find.  The problem: finding is the new doing Computer systems used to be frustrating because they did very little quite badly. People using systems became frustrated because they simply weren't capable of doing what they were required to do.
But technology has progressed and now technology can do practically whatever people want it to do. So why doesn't everyone using a computer have a large smile on their face?
The shear wealth of functionality and information has become the new problem. The challenge facing organizations is how to guide people through the vast amount of information on offer, so they can successfully find the information they want and thus find value in the system?
Intuitive navigation doesn't happen by chanceWhy  Information architecture is importantBad information architecture is not only extremely frustrating for users, but it has serious repercussions for organizations.

• For intranet's it means low adoption rates and staff reverting to unsupported off-line resources.
• For web sites with online shopping facilities it has a significant impact on revenue. Research suggests that a significant number of shopping attempts fail not because the user has evaluated the products on offer and decided against a purchase, but because the navigation system has failed and user can't find the product they are interested in.

Information architecture is the term used to describe the structure of a system, i.e. the way information is grouped, the navigation methods and terminology used within the system.
An effective information architecture enables people to step logically through a system confident they are getting closer to the information they require.
Most people only notice information architecture when it is poor and stops them from finding the information they require.
Information architecture is most commonly associated with web sites and intranet's, but it can be used in the context of any information structures or computer systems.
In Information Architecture for the World Wide Web: Designing Large-Scale Web Sites they define information architecture as:

• The combination of organization, labeling, and navigation schemes within an information system.
• The structural design of an information space to facilitate task completion and intuitive access to content.
• The art and science of structuring and classifying web sites and intranet's to help people find and manage information.
• An emerging discipline and community of practice focused on bringing principles of design and architecture to the digital landscape.

Common problems The most common problem with information architectures is that they simply mimic a company's organizational structure.
Although this can often appear logical and an easy solution for those involved in defining the architecture, people using systems (even intranet's) often don't know or think in terms of organizational structure when trying to find information.
Effective IA must reflect the way people thinkStyles of information architecture There are two main approaches to defining an information architecture. These are:

• Top-down information architecture

This involves developing a broad understanding of the business strategies and user needs, before defining the high level structure of site, and finally the detailed relationships between content.

• Bottom-up information architecture

This involves understanding the detailed relationships between content, creating walkthroughs (or storyboards) to show how the system could support specific user requirements and then considering the higher level structure that will be required to support these requirements.
Both of these techniques are important in a project. A project that ignores top-down approaches may result in well-organised, findable content that does not meet the needs of users or the business. A project that ignores bottom-up approaches may result in a site that allows people to find information but does not allow them the opportunity to explore related content.
Take a structured approach to creating an effective IACreating an effective information architecture in 9 steps The following steps define a process for creating an effective information architectures.

• Understand the business/contextual requirements and the proposed content for the system. Read all existing documentation, interview stakeholders and conduct a content inventory.
• Conduct cards sorting exercises with a number of representative users.
• Evaluate the output of the card sorting exercises. Look for trends in grouping and labeling.
• Develop a draft information architecture (i.e. information groupings and hierarchy).
• Evaluate the draft information architecture using the card-based classification evaluation technique.
• Don't expect to get the information architecture right first time. Capturing the right terminology and hierarchy may take several iterations.
• Document the information architecture in a site map. This is not the final site map, the site map will only be finalised after page layouts have been defined.
• Define a number of common user tasks, such as finding out about how to request holiday leave. On paper sketch page layouts to define how the user will step through the site. This technique is known as storyboarding.
• Walk other members of the project team through the storyboards and leave them in shared workspaces for comments.
• If possible within the constraints of the project, it is good to conduct task-based usability tests on paper prototypes as it provides valuable feedback without going to the expense of creating higher quality designs.
• Create detailed page layouts to support key user tasks. Page layouts should be annotated with guidance for visual designers and developers.

Developing an information architecture in this way enables you to design and build a system confident that it will be successful. Information architecture and usability Some people find the relationship and distinction between information architecture and usability unclear.
Information architecture is not the same as usability, but the two are closely related., usability encompasses two related concepts:

• Usability is an attribute of the quality of a system: "we need to create a usable intranet"
• Usability is a process or set of techniques used during a design and development project:

"we need to include usability activities in this project"
In both cases usability is a broader concept, whereas information architecture is far more specific.
Information architecture as an attribute of the quality of a system
An effective information architecture is one of a number of attributes of a usable system. Other factors involving the usability of a system include:

• visual design
• interaction design
• functionality
• content writing.

Information architecture as a process
The process for creating an effective information architecture is a sub-set of the usability activities involved in a project.
Although weighted to the beginning of the project, usability activities should continue throughout a project and evaluate issues beyond simply the information architecture.

• ascertain those needs (i.e., must gather information about the needs),
• organize the needs into a coherent pattern that clarifies their nature and interactions, and
• design a building that will--by means of its rooms, fixtures, machines, and layout, i.e., flow of people and materials--meet the occupants' needs.

Content  Analysis

Module No	Module Name:	outcome		page	Notes
3756G	Apply principles of visual design & comm.	1.  Receive and interpret the brief.		Visualdesignbrief.htm	Content to be developed
	This unit describes the skills and knowledge required to incorporate the principles of visual design and communication into the development of multimedia products for use within the cultural industries.	2.  Generate and assess ideas.		Visualdesign.htm	Page too long
		3.  Conduct research.		Visualdesign.htm	Too long, needs reorganisation
		4.  Select Media/Materials for use in visual design and communication.		Composites.htm	Further content to be developed Rename to visualcomposites.htm
		5.  Apply visual design and communication techniques.		Composites.htm Strongvisualidentity.htm	Further content to be developed Rename to visualcomposites.htm
		6.  Evaluate visual and communication design techniques.		Strongvisualidentity.htm	Headings need to clearly identify content. Needs content development specifically in relation to evaluation
3756B	Develop web site information architecture	Intro		Info2.htm	Does not match outcome specifically but is necessary as an introduction (first half of Info2.htm)
		1.  Identify content needs.		Info2.htm	Second half
	This unit defines the competency required to develop an information architecture for a complex web site that meets current and future business requirements.	2.  Plan content structure.		Info3.htm
		3.  Develop navigation system.
		4.  Test and sign off.
3755R	Ensure site usability This unit defines the competency required to determine that clients can use sites once a connection has been established.		Intro	Usability.htm	Content for this section should be developed further and reorganised
			1.  Design a user test.	Usability.htm
			2.  Conduct user test.	Usabilitytask2.htm
			3.  Evaluate user test.	Usability.htm
			4.  Document results.	Usability.htm
3755M	Validate basic web site performance		Intro		Content to be developed
			1.  Define performance criteria.		Content to be developed
	This unit defines the competency required to design and implement procedures that measure the performance of the web site and compare them to the initial design specifications.		2.  Validate performance.		Content to be developed
			3.  Sign off performance.		Content to be developed
3755K	Prepare web site content		1.  Ensure content meets required standards.		Content to be developed
	This unit defines the competency required to prepare a mix of content for a web site.		2.  Ensure the technology supports content.		Content to be developed
			3.  Test content.		Content to be developed
3755D	Confirm accessibility of web site design		1. Identify accessibility standards.		Should be renamed to AccessabilityGuidelines.htm
			2. Test accessibility.	Accessability.htm
			3. Test pages.	Accessability.htm
3755B	Maintain web site performance		1.  Benchmark performance.
	Completion of this module should enable the learner to ensure that a web site performance remains effective.		2.  Track site performance.		Content to be developed
			3.  Tune performance.		Content to be developed
			4.  Initiate performance improvement.		Content to be developed
	Resources
			Provide links to resources on student sites		Page to be developed
			Student links	Links.htm
			E Commerce		Should be renamed as eCommerce
			Dreamweaver	Dreamweaver.htm
			Human computer interaction	Hci.htm	To be broken into several smaller pages
			Book review	Howweuseweb.htm	Renamed book review
			Writing for the web	Writingfortheweb.htm

Pages to be deleted: index.html and links.html

 

Creating an effective information architecture in 9 steps

---

The following steps define a process for creating an effective information architectures.

1. Understand the business/contextual requirements and the proposed content for the system. Read all existing documentation, interview stakeholders and conduct a content inventory.
2. Conduct cards sorting exercises with a number of representative users.
3. Evaluate the output of the card sorting exercises. Look for trends in grouping and labelling.
4. Develop a draft information architecture (i.e. information groupings and hierarchy).
5. Evaluate the draft information architecture using the card-based classification evaluation technique.
6. Don't expect to get the information architecture right first time. Capturing the right terminology and hierarchy may take several iterations.
7. Document the information architecture in a site map. This is not the final site map, the site map will only be finalised after page layouts have been defined.
8. Define a number of common user tasks, such as finding out about how to request holiday leave. On paper sketch page layouts to define how the user will step through the site. This technique is known as storyboarding.
9. Walk other members of the project team through the storyboards and leave them in shared workspaces for comments.
10. If possible within the constraints of the project, it is good to conduct task-based usability tests on paper prototypes as it provides valuable feedback without going to the expense of creating higher quality designs.
11. Create detailed page layouts to support key user tasks. Page layouts should be annotated with guidance for visual designers and developers.

Developing an information architecture in this way enables you to design and build a system confident that it will be successful.

 

Fundamental questions of Navigation

• Where am I?
• Where have I been?
• Where am I going?

The most important question is “Where am I?”
Because users will never stand a chance of understanding the site’s structure if they don’t know where they are.

The user’s current location needs to be shown at two different levels;

• Relative to the Web as a whole
• Relative to the site’s structure

 

f people cannot navigate through your site, they will quickly leave. Thus, designing effective navigation on your Web site is crucial. But there are some basic things you need to do before you can start worrying about rollovers or links, images or flash.

Before you can even start to plan your navigation, you need to define your site's information architecture. Information architecture is the taxonomy or structure of your Web site.

Some common taxonomy elements on a corporate or business Web page are:

• Products - the products or services the company sells
• About - information about the company
• Investor Relations - information specific to investors
• Support - help for customers

Some common taxonomy elements on a personal Web page are:

• About Me - information about the page author
• Favorite Links - links that the author likes
• Friends and Family - information about the author's friends and family

Organization

Once you've determined your site architecture, you need to decide how to organize it.

Site structure:

No matter what navigation design is used there is one common theme to all navigation, all it does is visualise the user’s current location and alternative movements relative to the structure of the underlying information space. If the structure is a mess, then no navigation design can rescue it. Poor information architecture will always lead to poor usability.

have it all live in one directory, and just link to the major pages from your front page. Or you might have all the sub-pages separated into directories.

When thinking about your organization, you should think about how your customers might wander through it. Flow charts and storyboards can help you map out exactly how you would like to encourage your readers to use the site. You might want to map out exactly how you would like to encourage your readers to use the site. You might want to map out several paths for your readers to use.

Navigation Design

Once you have an idea of the architecture and organization, you're ready to think about the design of the navigation. There are several things you should consider in deciding on your navigation design:

1. Accessible
   The navigation of your site is possibly the most important part of any given page. So it should be as accessible as you can make it. This means avoiding special effects like Flash, Java, or JavaScript as your only navigation method.
2. Meaningful
   Keep your navigation meaningful. Make the links clear - don't try to get cute or use terms that are internal to your organization. Someone who has never been to your site before should know immediately where the link will take them.
3. Understandable
   If you want to use images for your navigation, make sure that there is some text associated with them. " Mystery Meat Navigation" is the use of non-descriptive images as navigation, and it's much more common than you might think.
4. Prevalent
   Your navigation should appear on every page of your site. While you don't need to have identical navigation, the basic structure should be the same throughout the site, with changes used only to indicate location within the hierarchy.

Once you've designed your navigation, then you can begin to use it. Keep in mind that it is really tempting to change your navigation structure while you're in the middle of implementing it. But if you decide to do this, be sure that you're making the change globally and that it fits with the original goals of your taxonomy and information architecture. My recommendation is to implement the original design and wait a week or two. If at that point you still want to change it, and the change will work, then go for it. You might just find that your planning and preparation were ultimately correct and not change it at all.

 

Below we will look at a structure which we believe has an effective design, and one which will address the fundamentals listed above.

Global Links: Site Wide Links:
 The following pages should be linked to each other;

Home
Accessibility
Usability
Visual Design
Information Architecture
Website Performance
Links
Resources

Each of these pages should be accessible from each individual page, these are Global Links.

Local Links:

Local links would be links to pages dealing with the same sections, ie:
Accessibility 1. htm.
Accessibility 2.htm
Accessibility 3.htm
These pages would link to each other but only the Introduction Page of the topic would have the Global, Site wide link, the sub pages of a topic should have ‘back to top’ links embedded throughout the page, especially on long pages.

Body Links:

Body links should be used so all relevant content can be cross-linked within a site.
Overall we feel that the above structure is hierarchical and would allow the user to intuitively navigate throughout the site with relative ease.

 

Products from the information architecture process

---

Various methods are used to capture and define an information architecture. Some of the most common methods are:

• Site maps
• Annotated page layouts
• Content matrices
• Page templates

There are also a number other possible by-products from the process. Such as:

• Personas
• Prototypes
• Storyboards

Each of these methods and by-products is explained in detail below.

Site maps - Site maps are perhaps the most widely known and understood deliverable from the process of defining an information architecture. A site map is a high level diagram showing the hierarchy of a system. Site maps reflect the information structure, but are not necessarily indicative of the navigation structure.

Annotated page layouts - Page layouts define page level navigation, content types and functional elements. Annotations are used to provide guidance for the visual designers and developers who will use the page layouts to build the site. Page layouts are alternatively known as wireframes, blue prints or screen details.

Content matrix - A content matrix lists each page in the system and identifies the content that will appear on that page.

Page templates - Page templates may be required when defining large-scale websites and intranets. Page templates define the layout of common page elements, such as global navigation, content and local navigation. Page templates are commonly used when developing content management systems.

Personas - Personas are a technique for defining archetypical users of the system. Personas are a cheap technique for evaluating the information architecture without conducting user research.

 

Conclusion

---

It simply isn't good enough for organisations to build functionality or write content, put it on their computer systems and expect people to be able to find it.

Developing an effective information architecture is an essential step in the development of all computer systems.

Effective information architectures enable people to quickly, easily and intuitively find content. This avoids frustration and increases the chance that the user will return to the system the next time they require similar information.

Remember: people can only appreciate what they can actually find.