Can an In-House E-Discovery Solution Be Built in a Day?
Monday, March 8th, 2010
After more than ten years of IT experience and over a year of experience as an attorney working exclusively with e-discovery, I am delighted to join the E-Discovery 2.0 team. I am a member of the South Carolina Bar Association and the American Bar Association. In this and future posts, I will try to bring a practical perspective or view from the trenches to this blog – a look at how to deal with some of the day-to-day problems facing e-discovery practitioners today. I will begin with a discussion about how to approach the decision to move e-discovery in-house, and although the desire to build a solution “in a day” is tempting (and sometimes precipitated by necessity), a solution that will stand the test of time and provide the greatest ROI requires a bit more planning and care.
E-Discovery can sometimes be thought of as an ailment that requires a quick remedy in the form of software or services. We continue to be reminded, however, that e-discovery is much more than a fleeting malady; it is an ongoing business problem that must be treated with the same diligence and meticulous execution as regulatory compliance or data security.
So where should the prudent practitioner begin?
Every good IT project manager I have ever worked with always had the same mantra when it came to solving a problem with technology – make sure the business problem has been well defined and establish detailed requirements before venturing into the marketplace. So, why are so many companies sending out form RFPs containing canned text expecting to find a miracle “end-to-end” e-discovery solution in a relatively short period of time? The answer, I believe, lies both in the abundance and availability of generic information about e-discovery and the fact that most companies looking to bring e-discovery in-house are already feeling the pain of rising costs and demands on existing staff. They are, in short, trying to conquer their e-discovery problem in a day. To truly conquer the problem, it should be attacked from the areas causing the greatest pain and expense first, and those areas should be thoroughly examined using proven project management techniques.
If e-discovery is indeed a significant business process, then companies must address that problem using the same proven methods that they have been using for years to solve other business problems. For example, every company today, believe it or not, has an e-discovery solution in place. If the company was sued tomorrow, and there was a significant e-discovery component to the matter, the company would likely react in a certain way based on a number of factors – hire outside consultants, work with a litigation support provider, rely on their outside counsel to coordinate e-discovery, etc. So why not predict that reaction, analyze it, and determine where the greatest expense and pain lies in that process? From that data, the company can decide which portions of the e-discovery workflow, if any, should be brought in-house, and it can seek out best-of-breed solutions rather than settling on the first end-to-end vendor that comes knocking. The next step is to rely on those time-honored project management edicts – define the business problem and establish concrete requirements. Then the company will be armed with the most powerful weapon in the marketplace – the power to distinguish.
The burning question, then, is how does the company decide which portions of the e-discovery workflow to bring in-house? The answer is relatively simple: you follow the money (right out of the front door in many cases). Where is the company spending most of its e-discovery budget, and are those portions of the workflow good candidates to bring in-house? Typically, processing data and review are the most expensive phases of any e-discovery project. The logic here is simple: if you send 100GB of ESI to outside counsel to review, it will be more expensive and time-consuming than sending only 20GB. Thus, processing, analysis, and first-pass review are great candidates to be brought in-house from an ROI perspective, and bringing these phases in-house could facilitate a form of early case assessment given the right solution.
Now, suppose a company decides to bring processing, analysis, and first-pass review in-house, also leveraging their chosen technology solution for early case assessment. Now what? The process can simply be repeated. Given the solution implemented, what happens if we get sued tomorrow? What other portions of the e-discovery workflow will need to be outsourced and how will we do that? What will that cost? Is there a better way? The company can continue this process until it determines that either all portions of its e-discovery workflow have been successfully brought in house or the ROI of bringing additional portions of the workflow in house does not justify additional projects at that time. This analysis should then be repeated on a regular basis to ensure the current solution is still meeting the needs of the organization and that market or industry shifts have not created additional opportunities for cost savings.
Although an effective and defensible in-house e-discovery solution likely cannot be built in a day, a carefully crafted plan of attack and a thorough understanding of the organization’s particular needs can strategically position it for long term success.
As a long-time reader of
Judge Shira Scheindlin is famous for a number of things in her
Yesterday, I explained what I think
On February 21,
Next week, as most of you know, is the Superbowl of legal technology events. And, so if this is a newsflash, you’ve probably found this blog by searching for the
There are many barriers preventing the creation of a new product category, especially in the legal industry. The biggest is inertia, since most people prefer to leverage the tools they have, both on grounds of cost (why spend money on something new?) and familiarity (who wants to spend time learning a new workflow?). A second barrier is risk-aversion, since the consequences of errors in the legal world can be severe for all concerned. A third is insensitivity to cost, since service providers simply pass on expenses to their corporate clients. When safety and risk mitigation rank above efficiency on the hierarchy of needs, there’s not much incentive to try new technology.
Part IV of this series on
Cheesy