Information Architecture

What?

Because I-TV is a relatively new medium people are unsure how to navigate or find information on an I-TV service. The mode of interaction is very different to that of the Internet and conventional TV. Each person who uses I-TV for the first time is essentially on a very steep learning curve. The navigation and information structure of an I-TV service should reflect the way users want to find information or buy products

Information architecture involves scientifically structuring the information on an I-TV service logically for its' end users. Information architecture designed and tested by Usability specialists with input from real users is much more likely to be usable upon launch. Development costs and timelines can be considerably reduced by getting a thorough understanding of Usability implications before building of the service commences.

The Usability specialist creates wireframes (page mock-ups of individual screens) of the interface after a careful consideration of the service's intended content, intended audience, scenarios of use and technical constraints. These prototypes are created using tools such as Visio and Freehand. Each element in the wireframes is verified by employing specialised techniques such as card sorting to elicit user feedback on the developing information architecture. The wireframe is constantly revised based on this feedback and any necessary design modifications are made. Throughout this process the technical feasibility of the proposed solution is constantly monitored.

Information Architecture has 3 key deliverables:

Interaction Schema - wireframes providing a page-by-page storyboard and descriptions of screen elements and features. It details what each screen should contain, and how the user can interact with it. It illustrates screen layouts, navigation rules and information flow. It is essentially a blueprint for design.

Service map - a graphical overview of the proposed service structure in the form of a hierarchical diagram. It depicts all of the screens within the service and the relationships between them.

Style guides - used to guide designers/site builders in developing the entire service. The style guide will offer rules for the use of navigation, design elements, controls, labelling, and error messages.