Why ECM Implementations Fail

According to the AIIM Blog, the latest AIIM State Of The Industry Survey is available... One of the questions was what were the top 3 obstacles encountered during your Enterprise Content Management (ECM) implementation? The results are below:

  • 44%=Underestimated process and organizational issues
  • 32%=Lack of knowledge or training among our internal staff
  • 30%=Project derailed by internal politics
  • 29%=Uneven usage due to poor procedures and lack of enforcement
  • 21%=Underestimated the effort to distill and migrate content
  • 20%=Excessive "scope creep"
  • 19%=Failed to address taxonomy and metadata concerns
  • 18%=Low user acceptance due to poor design or clumsy implementation
  • 16%=Failed to think or benefits/issues beyond our business unit.
  • 16%=Poorly defined business case
  • 13%=Lack of knowledge or training among our external staff/suppliers
  • 13%=Budget was overrun
  • 12%=Failed to prioritize "high-value" content
    • What I found interesting, was that very few of these issues can be tied to failures in the technology... its seems to be a failure of the organization. Lack of training/resources/knowledge could possibly point to an overly complex product... "scope creep" could be due to inflexible technology, or inflexible project managers... but bad taxonomy was blamed more often than the "clumsy implementation."

      This kind of reinforces what I always believed about ECM... its not really about the technology, its not even about the content; its about people. I always hated those snake oil salesmen selling coblaberation instead of collaboration. A hunk of technology isn't going to make all your process problems go away. If you have good processes, technology will make your life simpler. If you have bad processes, technology will amplify your problems.

Comments

obstacles

You said it exactly right -- and better than me -- it's all about people and processes -- especially as the technology itself moves to the infrastructure.

jmancini
www.aiim.typepad.com

And also of interest...

Interesting to see that most of the problems are failures of management, rather than the technology developers.

How can you get the non-technical people in charge to wake up to the fact that the ultimate 'success' of these projects lies with them, and have them support rather than restrict the developer needs?

This is typically relevant to larger organisations, rather than the smaller companies.

Stewie!

Post new comment

The content of this field is kept private and will not be shown publicly.
CAPTCHA
This form prevents comments spam...