Why Document Management Solutions Fail
My customers trust Associated Asset Management (AAM) with the creation, management, disposition and seamless access to their documents and official records. We take this role of the custodian of their documents very seriously as mismanaging them can lead to legal exposure for our clients. When it came time for AAM to replace our document management system, I became very interested in what makes Document Management implementations fail and what can be done to prevent it. Having successfully navigated our implementation, I wanted to share some of my findings.
“We take this role of the custodian of their documents very seriously as mismanaging them can lead to legal exposure for our clients"
The Reason Document Management Solutions Fail
This isn’t a groundbreaking discovery but the reason that so many Document Management Solutions fail is because the user circumvents the protocols in favor of familiar or easier solutions. The inconsistency that these tactics create leads to document incompleteness that becomes a tremendous liability to the organization both in term of lost productivity and legal exposure. Exploring the reasons why users typically bypass Document Management protocols can be informative, and how you respond to mitigate or eliminate such behavior will determine if you end up with a successful project.
Typically, organizations attempt to solve this challenge by enforcing strict policies around the use of the system. Approaches like this, however, are much more effective when dealing with an ERP or accounting packages, as failures such as service non-delivery and/or customer non-billing become immediately apparent. Often organizations may not realize that they are missing documents until months or years later, when a contract dispute requires a document to be produced that is not in the document management system. At this point, organizations are left hoping they can find the document somewhere in their email archives as an attachment. Even when organizations are reaching near 100 percent compliance by policing, the policing process itself tends to be effort intensive and fraught with negative interactions between IT and the users it is serving.
At AAM, we took a different approach when we developed our Document Management System. Our goal was to identify the functionality that users liked about other systems that could lead to them to circumvent our process and then include it in our design. Some responses that we received included:
• “I love Dropbox, I can access my documents anywhere”.
• “I like the Shared Drive because it is so fast and I’m used to it”
• “I’m used to my records management solution”
• “I have a custom macro that parses documents”
• “I like My Documents because it makes sense to me and I can find things fast”
We also took a lot of time to understand how, when, and where users consumed documents in our current solution and where they would like to.
From this analysis, we realized that if we wanted to have the adoption we desired, we needed to choose a solution that was web based, mobile friendly, could directly integrate with capture devices (copiers, scanners, etc), and gave us the flexibility to control the end user interface. The flexibility to control, tailor, and design the end user experience ended up paramount in the success of the system.
While taking this approach and investing so much time and effort into the end user interface delayed our projected timeline and pushed us over budget, it resulted in an incredible adoption and satisfaction rate with the end users.
While a high adoption rate was one of our main goals, we also wanted to concentrate on the backend processes. We built in robust reporting to track current and expected usage and now the system issues positive messages about our compliance rather than negative violation notices.
In order to implement this strategy, we needed to choose an appropriate solution and set of tools. The core of the solution is the Microsoft SharePoint 2013 platform. Global content types and meticulous mapping and standardize metadata allowed us to deploy an extremely robust search feature that delivered an end user experience that exceeded expectations. The search interface development was an iterative process where we learned what and how people were searching for and adjusted the interface and search refiners accordingly. The size of our content databases required the use of over half a dozen content libraries so we choose to age documents through these libraries according to their age and retention policies. This strategy accomplished the goal of having a manageable database size to restore the most recent documents in case of a recovery event.
To secure the solution, we leveraged Citrix NetScalers. They serve as a reverse proxy and authentication gateway to the public Internet and have Global Load Balancing functionality that allows to easily and securely scale as needed.
The extra money and time it took to deliver a consumer friendly solution was well spent. The solution ultimately helped flip a paradigm from one that required heavy training, messaging and enforcement of use to ensure use of the system to one where users actively and aggressively embrace the solution.