A while back, your Portable Consultant was intrigued to read a BBC story about “Websites ‘keeping deleted photos'” for a couple of reasons. Firstly, it showed a surprising degree of technical knowledge that used to be absent from Internet stories. The method that the researchers used to retrieve photos from social network sites after they had supposedly been deleted is trivial, but used to be beyond the abilities of news organizations to understand. There’s obviously a new generation of reporters and researchers who understand this beat.
Secondly, the heart of the issue as clearly stated by Joseph Bonneau “It’s imperative to view privacy as a design constraint, not a legal add-on”, should be framed and hung on the walls of web designers and managers, not only at social networking sites but also those in the public service, in the private sector, and even corporate intranets.
In the northern latitudes of North America February is considered quite a dismal month. With cold, grey skies overhead and worthless, shadow seeking groundhogs below there is not much to be encouraged about except the slowly lengthening hours of daylight.
The Portable Consultant is feeling understandably low, therefore, when against this bleak backdrop he is exposed to an ECM project that seems to model much that can go wrong with an ECM initiative.
While the following is not intended as a comprehensive list, these are some of the Do’s and Don’ts that the principal consultants on the project failed to be aware of. In no particular order they were:
Do have a Project Charter… an SOW is nowhere near good enough for the implementation of a critical enterprise infrastructure such as an ECM.
Don’t undertake ECM as an IT Department driven technology project… ECM is more dependent on business requirements and business processes than, say, a new firewall. These days the IT guys should be tightly integrated with the business; e.g., the head of IT should be a CIO who ensures C-level priorities, not technology, drives IT.
Do establish an ECM Steering Committee that is representative of the whole enterprise and leverage them to provide guidance, impetus, and a high-level sign-off for company-wide issues such as the corporate taxonomy, key metadata, and security models as well as critical SLA and Disaster Recovery (DR) requirements. Specifically…
Don’t confuse backup/restore requirements with DR. DR is about business continuance after the entire office and/or data centre has ceased to function while backup/restore is about a broken server, corrupted database, or some such.
Don’t just sit down some afternoon and enter new metadata fields into the production system on the fly without first gathering, documenting, and having affected parties sign-off on the relevent requirements.
Do not rely on business units to gather and present their own requirements without extensive guidance from knowledgeable ECM consultants who can speak to the business in their language, the language of business processes not software configuration.
Do not expect one of the Big 4 consultancies to necessarily know all this and manage the project according to ECM Best Practices… sometimes just one experienced independent consultant can be enough to help even a large global enterprise to navigate the treacherous waters of ECM deployment… without all that excess overhead. <grin>
Sigh. Time to crawl back into my burrow, I suppose. Wake me up in another six weeks.
Yes, The Portable Consultant now has a new look. I’ve tweaked the theme a bit and will probably continue to update the look & feel as the days go by.
It’s amazing how similar most WP themes are. This one was a Little different (pun intended) and the only one I liked that had solid borders around postings and other page elements.
more later…
-pmh
ECM infrastructure architecture… and unrelated matters.
