eDiscovery Tool evaluation – Case Study

After familiarising myself with the existing documentation, I reached out to key stakeholders in the following teams: –
• Records Management
• Infrastructure Architecture
• Data
• Technical Operations
• Networks
• Information governance
• Legal
• Testing and Assurance
• Proof of Concept Vendors 

Based on these face to face meetings and discussions, I put together a High-Level Design Document. This was presented and approved by the Digital Approval Board. The key actions from there were to build two proof of concept servers, one for each tool.  This needed some planned and scheduled time with the Tech Ops team. 

Following this, I scheduled some remote knowledge sessions with the two vendors and ensured any mutual non-disclosure agreements were in place with them. This was done by reviewing the agreements with in-house Legal and Information Governance team. Once all this was in place, a strategy was developed with Technical Operations , to identify appropriate network locations that would adequately test both tools. This would ensure true value of the Proof of Concept and the result could be matched against the documented requirements.
After further conversations with Records Management and Technical  Operations, it was agreed that the scope of test data would focus on the following: –
• Light Index of one department Share
• Two  targeted and current Data Subject Access Requests

Once the proof of concept was completed , I prepared product summaries and a conclusion. The conclusion was reached measuring both tool’s ability to perform each of the following  tasks :-