Information Architecture is about getting the right information to the right user role at the right time. Equally, it’s about providing the appropriate control mechanisms for that user role so they can carry out their tasks efficiently. In other words, it’s not just about consuming information, it’s also about producing desired results. Anything that requires user inputs is a productive task – from ordering tickets on-line to managing content.

The identification of roles is a critical first step to working out an appropriate Information Architecture strategy. We strongly recommend carrying out a User Requirements Analysis phase before getting into the design of the Information Architecture.

The requirements analysis phase will also identify business requirements. These, too, are an essential component when beginning an Information Architecture design phase. This is how we conduct an Information Architecture Design process:

Examine all Existing and Planned Content

For existing applications or web sites, we will take stock of all the existing content and critical data. We will review with you the intent behind this content and identify known issues regarding the current organization scheme.

For new applications or web sites we will identify the overall characteristics of the planned content that will serve to support your business goals.

Examine all Existing and Planned Functionality

Because we place strong emphasis on overall task completion, we will identify the key functional components that need to be in place for each task set. If key functional components are missing we will discuss with you the viability of getting them in place as part of the feature set. In certain cases, it may be preferable to simply earmark them for long term strategic development.

Design and Testing

When we have identified the content and functional components that will incorporated into the project we will begin the design process.

We will conduct a series of iterative design and test steps to zero-in on effective content structures and control systems that satisfy the requirements of specific user roles. The iterative approach support an agile and flexible process that can be tailored to suit your timelines and budget. Further control of scope can achieved through selecting the range of user roles that need to be supported.

Outcome: IA Design Document

Our Information Architecture Design Documents will outline the overall design paradigm describing the content structures and control systems. These design elements will be related to the business goals and along with their rationale for increasing application effectiveness and user productivity.

The document will include screen layout diagrams, interaction strategy and listing of essential functional components. Detailed design mockups showing graphic design elements can optionally be incorporated or provided in external documents.