What is a SharePoint Information Architecture, and why should you care about it? Learn how to create a top-notch IA that boosts productivity across your organization.
In the world of SharePoint management, Information Architecture, or IA, is the way content is organized and presented to the people within your organization.
A logical Information Architecture lays the foundation for end-user productivity, and ensures that everyone has access to what they need, when they need it.
Creating a solid IA starts with understanding the content, and how people will interact with it. From there, you can start to consider how SharePoint will meet those requirements making sure to account for change management.
The information you glean while developing your IA can also serve to inform your SharePoint governance plan.
A good IA is the difference between a usable system that is widely adopted by users, and one that struggles to get off the ground. In this post, we will look at what it takes to build a good IA in SharePoint.
Planting the seeds for a good Information Architecture
From a technical point of view, SharePoint is able to store and display almost any type of content:
- Lists of data
- Social content
The above elements can easily be added to a SharePoint environment using out-of-the-box functionality. How these elements are organized, laid out, and thus accessed by users, however, is very much up to those who are implementing the system.
As a first step, it is important to realize that technology alone is not the answer. It must not be allowed to drive the solution. The key to this is to abstract yourself away from the technology, and focus on the types of content you want to store in your SharePoint environment. You should focus on understanding the content in isolation.
It’s also important to engage with the key content owners and managers early on, to understand how people will interact with the collateral. Useful questions to ask these people include:
- What types of documents do you want to store?
- What information about those documents (e.g. published date, author) should be stored?
- Are there workflows for the content?
- Who will be accessing the different types of content?
- Which department or project does the content belong to?
Armed with a solid understanding of the content, and how people will interact with it, you can start to consider how SharePoint will meet those requirements and integrate that in your governance plan.
The building blocks of SharePoint content management
When it comes to organizing and managing content, and designing a solid Information Architecture, SharePoint offers the following building blocks:
- Site Collections: Logical containers with a unique name used to store a collection of sub sites.
- Hub sites: Allow you to group together similar topics, tasks, and content.
- Libraries: Located within sites, libraries store items that are ‘files’. Examples include Site Pages, Images, Videos, Documents. These are all stored in libraries.
- Lists: Similar to libraries, except instead of storing files they store ‘items’. An item, in many ways, is akin to a line of structured information from a table or database.
- Folders: Located in libraries and lists, folders are sub containers with names.
- Metadata: The properties that are applied to items inside libraries or lists.
- Managed metadata: A centralized version of metadata that can be managed in an enterprise way.
- Navigation structure: Informs how users find their way through your Intranet and land on desired sites and content.
- Content Types: A definition created for a type of item being added to the system. It can be used to define how the item is treated i.e. what metadata is needed for a type of document, or what retention schedule should be applied. You can learn all about content types here.
Creating an Information Architecture
Now that we understand the nature of our content, and the building blocks available to us, we can start to create elements of the Information Architecture. Let us take an example of an Intranet with an HR section. This needs to store HR forms, policies, key contacts, and news. The following is an example of a simple model that could be created within SharePoint:
One of the challenges of building a good IA is that there are a number of different ways of representing any given set of content.
In the above example, we have used a combination of Site Collections, Pages, Lists, and Libraries to best represent the content. However, there are a number of other directions you could take, depending on the needs of your organization.
Tips and tricks for managing SharePoint content with a strong Information Architecture
To help you get off to a good start with your Information Architecture, we present a number of tips and tricks.
Have some useful tips of your own? Drop a comment at the end of this post.
1. Make your Information Architecture logical
Build a structure that users would consider logical, one they would recognize. A simple example is that all supermarkets tend to have a similar layout, which means, even if you have never been to that particular store before, you have a good idea how to find something. Ensure users are able to store or find things without having to ask or be taught.
2. Make your Information Architecture extensible
It is impossible to determine, upfront, every possible type of content your solution will need to hold. Your IA should be extensible so that it is able to grow and incorporate new types of content as they become apparent.
3. Keep it as simple as possible
It is important to create appropriate site collections (as well as libraries, metadata, content types, etc) for the content you are working with. But there is a balance. Asking a user for too much metadata, or making them navigate twenty subsites, will just frustrate them.
4. Limit how many options you present to a user
Users don’t want to fill out twenty metadata fields, nor select from twenty different content types. To reduce frustration, or risk of user error, limit users’ choices to between four and seven at a time. It is believed that this is the optimal number of items a user can manage easily in their short-term memory.
5. Limit the use of folders
There are many reasons for this but, put simply, folders create usability issues by hiding away content in a nested structure. Leverage metadata, libraries, views and web parts appropriately instead.
Benjamin’s article on logical architecture of his governance planning series could be a great addition to this read if you want to learn more on the subject.