Information architecture involves creating the organizational structures that allows users to efficiently navigate through a site's content. At the highest level, information architecture is a process that defines categorization schemes that correspond directly to established site objectives, user needs, and the type of content that will be available on the site. Typically, a complete content inventory will have been completed and documented in the functional specification prior to the design of the information architecture.

The approach taken to define the information architecture can range from a hierarchical structure to more organic forms. Nodes within the structure are arranged by a set of organizing principles that correspond directly at the highest level to the site objectives and user needs. Different areas of the information architecture will also have different organizing principles.

Language consistencies are also an essential part of the information architecture design. A system of nomenclature is necessary to create vocabulary consistencies throughout the site. Once this is determined a complete navigation design can be designed with a focus on providing the users with the most efficient path to the information.

To define the information architecture and navigation design:

• Review and organize site objectives. User experience designers should always be reminded of the "why" involved in any project as defined in the site objectives and strategy. This information allows us to compare these objectives against the user's perception.
• List the content requirements. The specifics of the content available to users should outlined in a content requirements document. These specifications are created by comparing the available content with the user needs outlined during task analysis. If a content management systems (CMS) is to be used, the implementation guidelines should be reviewed and noted.
• Determine appropriate categorization scheme. By reviewing the site objectives, available content and user needs, it is possible to determine if the categorization process should be defined from a top-down or bottom-up approach. Either approach, combined with various organizing principles, will lead to the definition of appropriate categories and sub-categories used to organize the content.
• Design organizational and navigational approach. With the categorization process complete, we can begin to define the structural approach and it's effect on the navigation. Again, depending on the site objectives and user needs, we may choose a hierarchical, matrix, organic or linear approach to this organization problem.
• Create standard site nomenclature. A good information structure is incomplete without a consistent site nomenclature. All the site labels and descriptions should reflect the language used by the users of the product. This nomenclature can be derived from the earlier user interviews and tested during user testing sessions.
• Diagram completed information architecture. At the end of this process, a complete information architecture diagram can be created, displaying the essential categorization, and organizational schemes.
• Create navigation specifications and schematic layouts. With the structure defined, a complete navigation specification can be created that identifies the types of navigation defining all global, local and contextual navigation elements. At this point, schematic layouts, sometimes referred to as wireframe mockups, can be created to show the placement of the navigation elements in relation to the content of the site. This is the first step in the process of defining the information design or layout of the individual site pages.