When you are working on getting the details right for your SharePoint projects, you need to produce, share and get feedback on a number of key artefacts. Things like wireframes, navigation maps, and content taxonomies.

As we go through the series you’ll see how we can easily apply Records Management policies to any type of content within SharePoint 2010 which is extremely powerful!

However we will be specifically concentrating on new functionality in SharePoint 2010 and defining our Content Types with Records Management in mind.

Following on the theme of common sense, I’d like to provide some additional guidance and best practices around jumpstarting your SharePoint governance.

One of the most powerful means of filtering, sorting and searching information that has emerged as part of social computing is the use of “tags” to classify content of all types.

We’ve been doing a lot of work with SharePoint lately so I thought I’d put together a quick post on some approaches to implementing taxonomies in the new version

Mind mapping works so well for creating high level and detailed designs of your SharePoint Information Architecture or taxonomy

SharePoint is making inroads as an ECM or Records Management system, primarily because of its document library features, price, and integration with Office. But, for SharePoint to move beyond that and become the system to do document-centric transactional processing, you’ll need to customize and plan your SharePoint installation more carefully.

SharePoint Saturday: The Challenge of Unstructured Content, Concepts and Terminologies, Taxonomy and ECM Adoption Techniques, Why should Taxonomy matter to me