Colligo Blog: Ryan Duguid

In this final blog entry, I’ll wrap up with what Microsoft sees as the key drivers of SharePoint and Office 2010 as well as provide answers the two of the questions that I was asked during the webinar and was able to answer live.

In summary, the three key drivers of the new SharePoint and Office 2010 release are (1) ease of use, (2) flexible compliance, and (3) cost effectiveness. These help to drive enterprise content management across the organization and into the hands of all of your users.

My answers to the following two questions asked during the webinar can be heard on the audio file below.

Continuing the series based on the recent webinar that I participated with Colligo on email management in SharePoint 2010, in this fourth blog entry I’ll outline the new features designed to extend the Records Management capability of SharePoint 2010.

In Place Records Management

Historically, most records management systems operate around what’s called a file plan or a business classification schema, which is essentially a hierarchical folder structure for classifying and storing content (including emails). Within the file plan hierarchy, you define your metadata capture and your retention policies. In SharePoint 2010, we have created a new way of managing records called In Place Records Management. The idea here is that records can exist anywhere within the SharePoint platform. You may chose to take that record and move it to a separate records archive but a lot of people in the collaborative world want to the ability to declare a content item as a record, and to leave that content where it is, in the context it was created.

In my second blog entry, I discussed how SharePoint is bringing together the traditional world of content management and the world of social networking and collaboration. In this third entry, I’ll look more closely at Project and Case Management in terms of the new features and functionality that Microsoft launched in SharePoint 2010 that will help in email management.

The Content Organizer

The Content Organizer is an underpinning piece of the SharePoint 2010 platform. The Content Organizer is a way to automatically classify and route information based on specific properties of that information. This capability makes it easy for users to take large volumes of emails and move them into the SharePoint environment for better project and case management.

In my first blog entry, I looked at the 4 key scenarios for email management in an organization and identified the key outcomes and supporting platforms and software for each scenario. In this next section, I would like to talk about content management from a Microsoft perspective, our notion of ECM for the masses, and how we think of delivering it from Microsoft.

When we look at the ECM space, we see two worlds, the world of traditional content management and the world of social networking and collaboration. From a Microsoft perspective and with SharePoint, we are looking at bringing these two worlds together and saying that this is all just content, no matter how it is created, no matter how it is rendered to the end user, or on what device it’s consumed over. It’s all simply content that needs to be supported with security, metadata, workflow processes, and with policy in place to make sure we keep the content we should be keeping and we dispose of content once it is no longer useful to the organization and in line with corporate guidelines, industry or government regulations.

As Barry mentioned, I’m going to do a series of posts over the new few weeks based on the information that I presented at the webinar on Email Management in SharePoint 2010. These posts and the associated audio files and presentation slides break down the webinar into smaller sections and enable people to download the audio and slides and listen/view at their convenience.

In this first section, I’ll discuss how Microsoft is thinking about ECM and in particular email management in terms of how an organization can get it under control. Their are 4 key scenarios that we consider when we think about how to manage emails in an organization. These 4 key scenarios I like to call the continuum, starting on the left hand side with Personal Email Management, then moving right to Project and Case Management, then to Email Archiving and finally to Records Management.