Summary

During information architecture, we create schemes for organizing, labeling, and navigating the content of a site. Storyboard and site flow are reflective of the taxonomies produced during this process. For systems with significant UI, information architecture provides a much needed reality check for users, stakeholders, and implementers of the system at the very outset. It is used for flushing out the detailed requirements of workflows and processes, the implications of which are immediately reflected in the detailed use case description of the system. The consensus on detailed use case descriptions among stakeholders, users, information architects, and the technical team ensures that the vision set forth by the extended team addresses both the business needs and technical feasibility of the system within the specified time and budget.