For a Web site or other digital information product, information architecture (IA) constitutes a primary aspect of conceptual modeling. Information architecture begins with content analysis. Through discussions with your project manager and content developers and by analyzing a representative sample of your existing content, Team Spirit develops an understanding of the scope of your Web site or other digital information product, the types of content it presents, and the hierarchical or associative relationships that exist between your content objects.

If your Web site or digital information product already exists, during conceptual modeling, Team Spirit evaluates its current information architecture, your existing content, and the lexicon, or controlled vocabulary, that is already in use.

Once we have become thoroughly familiar with any existing information architecture or lexicon, and your existing and planned content, Team Spirit produces a detailed Information Architecture Strategy and Specification for your Web site or other digital information product by

• categorizing content types
• identifying document types
• developing a lexicon, or controlled vocabulary, for your content domain
• labeling categories of content, using terms from your product lexicon
• defining high-level organizational models for your Web site or digital information product
• developing a taxonomy that establishes the hierarchical relationships between content objects
• specifying associative relationships between Web pages or screens containing various types of content
• defining the metadata that describes the attributes of your content objects

Our Information Architecture Strategy and Specification defines the structure of your Web site or other digital information product and includes

• a high-level content map—for a new Web site or digital information product—that shows the general scope and organization of your planned content, including various categories of content
• one or more detailed site diagrams that show the scope and organization of your product’s content and define the hierarchical and associative relationships that typically exist between different types of content objects
• labeling schemes for your product’s content objects
• metadata that describes the attributes of your content objects

Once our Information Architecture Strategy and Specification undergoes one or more cycles of review and revision, we present our information architecture to your entire product team.

Content Modeling and Mapping Strategy

Once your content developers have created an inventory of your existing and planned content for your Web site or other digital information product, Team Spirit works collaboratively with them to

• determine the proper granularity for different types of content—that is, how to divide your content into information chunks
• map information chunks onto pages or screens

With the help of your product team, Team Spirit also develops an understanding of the existing or planned technology infrastructure for your Web site or other digital information product. Team Spirit works collaboratively with your product team to ensure that we take into account your process for implementing and maintaining your information architecture and managing your content.

Finally, Team Spirit develops a Content Modeling and Mapping Strategy for your Web site or other digital information product. Once our Content Modeling and Mapping Strategy undergoes one or more cycles of review and revision, we present our strategy to your entire content development team.