What I found most valuable, though, were the nuggets of advice throughout the piece on the main causes for the failure of an ECM project. Alan Pelz-Sharpe, a principal at CMSWatch, offers sharp observations on the importance of the up-front work prior to selecting an ECM solution:
"In most cases, little or no thought is given to content governance issues, and in larger deployments failure can often be traced back to that."
Another observation from Pelz-Sharpe on the risks of not fully understanding the internal business processes before trying to overlay an ECM solution:
"Very little time is given to understanding, mapping, and optimizing business processes in advance of a technology project -- I would say this is the number one reason for failure. Analyzing business processes is a highly skilled task, and few firms have those skills in-house and are reluctant to spend money on outside help -- with resulting consequences."
Many organizations would do well to take the advice in the article to heart, and it's worth a read for anyone involved in the process of standing up an ECM solution.