Steps Toward a SharePoint Reference Information Architecture

Many organizations do not spend the time and make the effort to understand user requirements in detail.   And even when they do, they are often unable to translate requirements into effective content organizing principles, critical to successful SharePoint deployments.

Organizations, committed to making SharePoint a success, need to take a comprehensive approach that addresses user information needs in the context of their work processes.   The central artifact of this approach is a reference information architecture.  An information architecture determines how content will be organized and managed. 

This blog post discusses the initial part of the process that translates more abstract pains and problems into a conceptual framework for content.  In a follow-on post, we’ll discuss how this conceptual framework can be translated into design elements and information architecture details. 

Developing an information architecture is not a trivial activity.  It requires a methodical process.

The following table articulates steps that lead to development of initial organizing principles (click table to enlarge):

There is still a great deal of work to be done to translate organizing concepts into SharePoint design elements.

The last step is where we begin to create the conceptual framework for taxonomy and information architecture development.  There are a number of tasks that need to be executed to further translate this into content models, site structures and navigational elements.   

A methodology for building an information architecture responsive to user needs should address five phases of activity:

1. Strategy and Vision
2. Research and Discovery
3. Design and Development
4. Testing and Validation
5. Maintenance and Enhancement

A well-planned information architecture examines user processes first and foremost.  There are many aspects to understanding this context.  Ultimately developing a successful SharePoint deployment means building internal capabilities and competencies in each of the areas described with governance processes acting as the “glue” that holds all of the other pieces together.   Long term success, and the resulting benefits, requires a disciplined approach to information management.

For a discussion of Earley & Associate’s information architecture methodology, check out my recorded discussion on SharePoint Information Architecture.