Replaced by Developing and managing an information architecture - Whole of Victorian Government ICT Guideline issued 29 November 2010.
Supporting: Information Architecture/Classification Standard (WEB/STD/08)
Version: 2.0
Release Date: 30 November 2007
This resource supports the Information Architecture /Classification Standard WEB/STD/08. A significant aspect in developing an effective information architecture is the analysis of audience and user characteristics and the actions they wish to undertake. This is done to ensure that users are able to effectively complete the tasks they initiate on the website.
This paper provides advice for gathering and recording website audience or user interaction information. Specific information architecture issues will be addressed in this paper including:
User-centred design, ease of navigation and efficient discoverability are fundamental to providing a better web experience and service to clients. They result in users having a positive experience on the website and increased return visit rates.
Website interaction design is a component of the user-centred design process. It leverages:
Defining and tracking the way users interact with the website helps to determine the most user-centred and streamlined way to deliver information and services. This has an impact on:
Audience profiling and task analyses are classic methods for figuring out who the audience is and what they want to accomplish. A range of website interaction techniques can be used to translate the needs of website audiences into efficient and intuitive task completion exercises.
Website interaction analysis creates plans about how users will or do interact with the website and often involves:
The plans can take the form of:
Audience profiling and task analyses are classic methods for establishing who the audience is and what they want to accomplish. Audience profiles characterise the information requirements of the web site users. A user may be a member of more than one audience and therefore may approach a website with a range of motivations or needs, and motivations can change from one visit to another.
Audience analysis and the resultant profiling generally aim to
The extent and frequency of research and audience analysis is dependent on:
However, like usability testing, informal and formal methods can be used.
Each audience profile provides an overview of the types of information required by that audience, the way in which one audience's needs are different from another, and the types of web functions and services that are required to meet the audience requirements on the actual site.
The outcomes of audience analysis and research involves the identification of:
The examples below were developed as part of an audience profiling exercise for Consumer Affairs Victoria as part of their website re-development initiative.

Example of a user profile record (1)

Example of an individual user profile (2)
There are a number of research methods used to gather information about audiences and their interaction needs and preferences. The investment required to implement these research activities will be dependent on time, resources, costs, scope, size and the risk profile of the website. Each of these methods can use formal and informal approaches. However it is vital that some investigation is done into who might use a website and what they might want to do there.
The table below was prepared by the Australian Government Information Management Office as part of a user-profiling toolkit (3). It lists user research methods and provides details of their strengths, weakness and resource requirements.
| Method | Strengths | Weakness | Quality of Results | Resources Required |
|---|---|---|---|---|
| Usability test metrics, qualitative feedback |
|
|
|
|
| Questionnaires and Surveys |
|
|
|
|
| Interviews and Focus Groups |
|
|
|
|
| User Website Feedback |
|
|
|
|
The design of audience research activities often involves researching general users, businesses and industry representatives and internal organisational staff. Research instruments include but are not limited to:
Audience/user research generates a list of information and service needs associated with website audiences. Within this list there are some significant ‘must-have’ requirements that are required by all website users:
Particular interaction needs that relate to certain groups or only had low level mention across several audience groups are also likely to be included in a listing of audience needs.
Tasks can then be classified according to audience, profile, sector description, interaction types, special needs and priority. This can be represented in a matrix.
| Audience | User profile- Choose from Primary, Secondary, Occasional user |
Sector - Major audience sectors eg., Consumer, Business, other or Youth, Seniors, etc. | Description - Short description of the characteristics of the audience | Interaction types - list typical interactions eg., online registration | Special Needs- Consider language, disability, location, etc. | Priority Rating - High, Medium, Low |
Audience data is used to plan the location, functionality, presentation and investment in the interactions delivered on a website. This will ensure that the most important interaction types are provided to the widest number of users .
The list of individual interactions gathered in a profiling exercise can be grouped into a number of interaction categories and the type of functionality or service that could be offered. This helps to match the functionality with the activities that users require.
| Interaction Categories | Sample Website Interactions Types |
|---|---|
Identify based – I know who I am, or which group I belong to |
Audience classification options e.g. Youth, Seniors, Industry, Consumers |
Task based – I know what I want to do |
Transactional services e.g. online bill payment |
Item based – I know what specific product or service I want |
Fast track options to products or services through Search or Homepage access |
Location based – I want to know where something is |
Interactive map showing location of offices, resources etc. |
Interest based – I know my general field of interest |
Subject taxonomy providing access to categorised information and services |
Organisation based – I know which agency or department, or role of the person I want to talk to |
Directories, organisational diagrams |
Time based – I want to know when something is happening or what’s on now |
Latest news, events, alert services |
Random based – I am looking around to see if something interests me. |
Search and browse |
Mapping, designing and testing the effectiveness of the interactions can be presented in a number of ways. Some presentation methods such as site maps can be used to provide a high level view of the range of interactions and the ‘number of clicks’ required for the interaction. Others like flow diagrams map individual processes closely. Use Case diagrams provide a way of communicating the functional requirements of a particular interaction. Wireframes and storyboards can be used to visualise and test interactions and evaluate website navigation systems.
The diagrams below are examples of the different ways that interactions can be presented.
Sitemaps are high level diagrams showing the hierarchy of a system. They can be used to provide a visual picture of progress through a website for the completion of an enquiry or task.

Reference: To see and enhanced image go to http://www.orarian.com/documents/Sample_Sitemap.pdf (This document requires the use of Adobe Acrobat Reader). .
Process flow diagrams show the end-to-end process such as locate information or complete a specific task.

Reference: To see and enhanced image go to http://www.leacock.com/deliverables/flow_ex1.pdf (This document requires the use of Adobe Acrobat Reader). .
Flow diagrams can be presented in a number of ways.

Reference: To see an enhanced view of this image go to http://www.leacock.com/deliverables/block_diagram_ex1.pdf (This document requires the use of Adobe Acrobat Reader). .
Wireframes display page level navigation, content types and functional elements and can be used to provide an indication of the user visual and navigation experience.

Reference: To see and enhanced image with associated instructional text go to: http://iainstitute.org/tools/download/LombardiWireframe.pdf (This document requires the use of Adobe Acrobat Reader). .
A use case describes a way in which a real world actor - a person, organization, or external system - interacts with an organization such as a website. It captures the sequence of events of an actor (human or system) using the system to complete a process. Typically use cases represent business processes and assist in communicating requirements and testing the value or relevance of a process.

Scenario templates capture the interaction process in a formal descriptive manner. Reference: Further description of Use Case templates is available at http://www.scenarioplus.org.uk/

Interactive prototypes create a real web simulation and clearly define the navigation and process experience. The major issues with prototypes are the cost and time involved in their preparation.
Sequence diagrams track the interaction between a user and the messages sent to the system and the message/information that the system returns.
Storyboards can show a sequence of interactions and options throughout an activity. They can use either sketch diagrams of the sequence of activity or use wireframes for a site to test and plot navigation.
This type of interaction model groups users into major audience groups and identifies required information and service requirements was prepared by iFocus for Consumer Affairs Victoria.

Australian Government Information Management Office User-Profiling and Testing Toolkit
Goodwin Kim, Perfecting Your Personas
Jacob Nielsen's usability site
Sample Block Diagram available at http://www.leacock.com/deliverables/block_diagram_ex1.pdf (This document requires the use of Adobe Acrobat Reader). .
Sample Flow diagram available at http://www.leacock.com/deliverables/flow_ex1.pdf (This document requires the use of Adobe Acrobat Reader). .
Sample Sitemap available at http://www.orarian.com/documents/Sample_Sitemap.pdf (This document requires the use of Adobe Acrobat Reader). .
Scenario Plus Templates, Tools, Training & Consultancy for Scenario-Based Requirements Engineering
The Information Architect – Tools
Website Management Framework
Government Services Group
Department of Treasury and Finance
Phone: 61 3 9651 5656
Email: administration@egov.vic.gov.au
Footnotes
(1) iFocus (2004) Consumer Affairs Victoria Website User Research Report
(2) iFocus (2004) Consumer Affairs Victoria Website User Research Report
(3) Australian Government Information Management Office - User-Profiling and Testing Toolkit
Enter your email address to subscribe or unsubscribe from the eGov What's New mailing list.
Please enter email address of the person you wish to send this page to.