How to NOT do ECM
It’s not an uncommon story. Management at the highest levels of the company identifies a need to have a centralized document repository to facilitate disaster recovery and document sharing. The IT department, swamped with other work, buys a product that looks like it might work and begins implementing it. When they start showing the new system to the business people (the people who will have to put documents into the system) they are confronted with resistance.
“We had hoped for automated workflow” and “It’s not fast enough in our remote offices” are common responses to their introduction to the new document management system. However, the most common response is “It will cost my department money. You can’t implement here”.
IT bought a solution that works with their preferred database, is easy for them to build integration with line of business applications and runs on the right operating system. What IT didn’t do is look at what is needed within their company beyond the bare basics of DR and document sharing. They didn’t evaluate what a document management system can do to empower front line business staff to do their job better and more efficiently.
While an objective of DM doesn’t have to be reducing labor related costs, this benefit shouldn’t be ignored. Changes in processes and additional staff to facilitate document scanning and indexing will cost money. If the DMS doesn’t provide any tools to allow managers to reduce costs elsewhere, the project to implement a new system is bound to receive an unfriendly reception.
This very scenario took place at a client of mine some time ago. In a financial services organization with a global foot print, the IT department at this client had purchased a DMS two weeks before they signed a contract with me to manage their DMS project. The product they purchased is a solid departmental product, but it provides no provision for managing content in the global environment the company maintains. The product fit into their technical environment, but it didn’t provide the ability to manage documents globally or any way to automate workflow. Both of these were seen to be key features of every business unit I met with early on in the project. However, IT didn’t consider any features of the product beyond their wish list.
How can your IT department avoid this sort of expensive mistake? It’s really very easy. Involve staff and management from across your company throughout your DMS project. Take the wish list and the concerns of business units seriously. Conversly, make sure that IT isn’t left out of the discussion. Their needs are important factors in the success of the project as well, but they aren’t the only factors.
Regardless of whether you are business or technology oriented keep your mind open to the needs of the other side. If you are bringing document management into your company, it’s vital that both business and technology concerns are addressed.