Analyze goals and strategy for corporate portals and web sites. Conduct user research, stakeholder interviews, search log analysis and content audit. Design high-level information architecture, including but not limited to: Structure, Organization, Navigation, Search, Sitemaps, Metadata, Controlled Vocabularies, Indexes, Taxonomies and Thesauri.

What does this mean?

The goal of information architecture is to make it easy for users to find information on your web site. Organizations must realize that users may represent multiple audiences, and that each audience may perceive their content in a different way. The steps/tools listed above help identify how content on your site should be labeled, organized, navigated and searched.

An information architect is not responsible for the graphic design of your web site; an IA develops the information design. A common analogy applies: You wouldn't consider building a house without a set of architectural plans, so you shouldn't develop a web site without information architecture.

Workflow Analysis and Documentation:

Develop and document workflows for a variety of web-based processes and applications. This can apply to new systems being developed, or reviewing and improving existing processes. Workflow documentation can also include personas and narratives to assist development teams.

What does this mean?

Workflows apply to any process a user may encounter on your web site, for example: account creation, insurance quote application, contact forms, e-commerce systems, etc.

For existing workflows, are you analyzing how many users start the process then abandon? Why do they abandon the process? By reviewing and improving the process you may increase your applications/registrations/sales, etc.

How Much?
Budgeting for Information Architecture and Usability

Budgeting for information architecture and usability services can prove to be a challenge. Ten to fifteen percent (10-15%) of the total project budget is a good estimate.

Those not familiar with the importance of information architecture and usability will dismiss the idea quickly. But would you rather spend an extra ten-fifteen percent now or another 100% in a year because you need to overhaul a poorly planned site the confuses users and employees?