Monday, May 02, 2011

ECM Maturity Model and SharePoint

If you don’t know the ECM Maturity Model – definitely take a look at – they are currently at version 2.0. The ECM Maturity Model provides a framework for creating a roadmap in the context of an overall ECM strategy. It categorizes an organization across 13 maturity dimensions into one of the 5 levels of ECM maturity:

  • Unmanaged
  • Incipient
  • Formative
  • Operational
  • Pro-active

I’m wondering if anyone has already applied this model to a typical SharePoint implementation. Please leave a comment if you have.


Anonymous said...,-Version-2-0.aspx

Thomas Vochten said...

Haven't applied this one in particular, but its derivative SharePoint Maturity Model by Sadie Van Buren. A nice way to talk about where your organisation stands with SharePoint and where you want to go.

Rene said...

If I remember correctly, Sadie's "SharePoint Maturity Model" took the ECM Maturty Model (among other things) as an inspiration.
Check the following page:,-Version-2-0.aspx

Shaun O'Callaghan said...

It's one of the first things I attempt to do on new engagements for two reasons.

Firstly, it drives the vocabulary you can use as a consultant when engaging in requirements and design. Sometimes it's absolutely fine to use terms like "records management" and "metadata", other times that would absolutely not be appropriate.

Secondly, it informs the kind of solution I would suggest and how the delivery phases would be split up. I worked with a customer this year who, before I got there, was working from network file shares. Some of the far-reaching business aims were to automate the disposition of certain types of documents after a period of time. The leap from network file shares to automatic disposition using Information Management Policies, in my opinion, is *way* too great to do. This, along with quite intricate integration of LoB systems into Managed Metadata Store, were pushed out to a later phase in the project possibly 6 - 12 months in the future.

The ECM maturity model should actually be termed the 'Information Management maturity' model because it doesn't just relate to ECM. As mentioned, it underpins the vocabulary we can use and absolutely should inform the solution we deliver.

Shaun O'Callaghan