My Impromptu Video Interview at NY LegalTech on Predictive Coding and Some Hopeful Thoughts for the Future

February 28, 2012

This is my off-the-cuff interview at LegalTech 2012 by the well-known Gregory P. Bufithis, the founder and CEO of Project Counsel. Most of the video is of me talking about my current favorite subject, predictive coding, but I am also asked about where to get reliable information on e-discovery. I point out that one of the greatest resources out there for in-depth information is The Sedona Conference, where, like this blog, everything is free. If you watch the whole video, you will see me hassle the fun-loving Greg at the end with my Star Wars Storm Trooper duck. Thanks to the good people at Daegis for that little LegalTech souvenir, and my condolences to Maura who got stuck with the Princess Leia duck.

Greg Bufithis and his posse of reporters are at nearly every e-discovery event in the world. For an example of their detailed coverage, take a look at Greg’s excellent report on this year’s LegalTech. You might also want to check out a new application that Greg recommends, The Mashup App. He says he used this new app at LegalTech with much success. As you can see from his report, Greg moves around a lot and really needed this app. I have not tried it out yet (been real busy lately doing what I love, as my careful readers have deduced), but hope to do mashup soon.

As a brief narrative sequel to the video, I suggest that all of my readers try to learn as much as you can about predictive coding as fast as you can. While you are at it, ask all your favorite vendors with predictive coding offerings, either now or coming soon, to bring the prices down! We need to use the best technology in every case, not just the blockbusters.

It is a great time to be in e-discovery and will get a lot better soon. We are all at the beginning of a new ground swell. The Law is learning to surf the tidal wave of new technologies, new information, and new writings. For my dear readers who understand and practice the Hacker Way, the sky is the limit to your future success. Don’t be timid. Do what you love. Love what you do.

Your work is going to fill a large part of your life, and the only way to be truly satisfied is to do what you believe is great work. And the only way to do great work is to love what you do. If you haven’t found it yet, keep looking.

Steve Jobs

Stop acting as if life is a rehearsal. Live this day as if it were your last. The past is over and gone. The future is not guaranteed.

Wayne Dyer

The future is literally in our hands to mold as we like. But we cannot wait until tomorrow. Tomorrow is now. 

Eleanor Roosevelt


Evidentiary Objections to Email are Key to BP Oil Spill Case

February 19, 2012

The Deepwater Horizon oil spill case is scheduled for non-jury trial in New Orleans on February 27, 2012. In re: Oil Spill by the Oil Rig “Deepwater Horizon” in the Gulf of Mexico, on April 20, 2010, (E.D.La., MDL No. 2179). This mammoth case is a consolidation of 300 law suits involving 120,000 people and businesses. Click here to see the full docket on Justia. The biggest case in the country proves, once again, that email is powerful evidence. You may recall news concerning email and the world’s largest oil spill back in 2010 when Congress publicized an email from a BP drilling engineer, Brian Morel. It warned that the Deepwater Horizon oil rig was a “nightmare well” that had caused the company problems in the past. Of course, there were more emails like this, but they did not all get into evidence as this blog will explain.

Here is how the presiding Judge Carl Barbier describes the In re: Oil Spill by the Oil Rig “Deepwater Horizon” case in a recent Order:

This Multi-district Litigation (“MDL”) arises from the April 20, 2010 explosion and fire on the DEEPWATER HORIZON mobile offshore drilling unit (“MODU”), and the subsequent discharge of millions of gallons of oil into the Gulf of Mexico. The consolidated cases include claims for the death of eleven individuals, numerous claims for personal injury, and various claims for environmental and economic damages.

Order dated January 26, 2010, Granting in Part and Denying in Part Transocean’s and BP’s Cross-Motions for Partial Summary Judgment Regarding Contractual Indemnity

The purpose of the upcoming trail is to assign and apportion blame among the many defendants sued in these cases. The main corporate defendants include BP, rig owner Transocean, and Halliburton, which provided cementing services. As a side note, BP recently accused Halliburton of spoliation by intentional destruction of computer records and has, of course, moved for sanctions. Anadarko Petroleum, one of BP’s partners in the well, is also involved in the upcoming trial. Plaintiffs include individuals and businesses, represented by a plaintiffs’ steering committee, as well as many states and the U.S. government.

Smoking Gun Emails

Emails will certainly be part of the 7±2 documents that the trial lawyers of all parties will build their arguments around. See: Secrets of Search, Part III.  In addition to the “nightmare well” email that will be the centerpiece of every attorney’s opening statement, except for BP, many other emails were found that will be featured as evidence. Three smoking gun type emails were subject to a motion in limine to try to have them excluded.

One of the emails subject to the motion to exclude was a pre-accident 2009 email where an Anadarko employee expressed disappointment about BP. He complained that BP had not disclosed some information related to tropical storm damage caused to a different Transocean rig. Another Anadarko employee responded with an email saying: “Bummer. I’m amazed that they did not tell us about this.” Bummer and amazing make great touch stones for attorney arguments about cover-up and fault. This is just the kind of email you need to build a persuasive pitch to pass all blame to BP. Mix in the nightmare well, and you have a real bummer for BP’s attempt to share the blame with other defendants.

But wait, there’s more. They also found a June 2010 email from a Halliburton employee, Ryan Haire, which questioned the company’s reported findings regarding some tests on the well.

But wait, there’s still more. They also found an February 2010 email from a BP geologist to a friend referring to the Deepwater Horizon rig and saying: “thanks for the shitty cement job.” Oh, this is a particularly good one for lawyers because of the colorful language.

These emails could be used to argue cover-up and negligence, despite what the witnesses later say under oath. Trial lawyers could now say it was a shitty nightmare well that BP knew was an amazing bummer. Powerful stuff, especially with a jury who might later hear damage claims. BP knew that it had to try to keep out these three emails, so they made an all-out effort with a motion in limine (one of dozens).

Just because you discover email, and it’s hot, and would be part of anyone’s 7±2, does not mean that the email will actually be considered. Never forget that the whole purpose of e-discovery is not just to find evidence, it is to get it admitted at trial. If it does not get into the record, it cannot be part of the 7±2 based argument. All three of the emails quoted above have been excluded from evidence by a February 8, 2012, Order of U.S. Magistrate Judge Sally Shushan.

Judge Shushan excluded the first two emails on the basis of hearsay. The author of one of the emails, Ryan Hair, testified that he really had no first hand knowledge of the test findings that his email criticized. It was just what someone else had told him. Hearsay objection sustained.

As to “thanks for the shitty cement job” email, it was excluded on even more interesting grounds. According to news reports, Halliburton argued that the email was no more than a casual, tasteless joke made by one friend to another. Judge Shushan agreed. She concluded that there was no showing that the email was a “business record” of the cement work that could be used as a basis to introduce the email into evidence. Judge Shusan explained:

It must be demonstrated that the e-mail at issue was not sent or received casually, nor was its creation a mere isolated incident.

Hmm. You have to prove that the email was not casual? I guess this shows the “just kidding” objection sometimes works and can be used in a last-ditch attempt to exclude email. Usually that kind of “didn’t really mean it” argument does not work. The email will be allowed into evidence, but you can provide other testimony that it was just a joke, and let the trier of fact determine the truth. The problem is, most juries lack a sense of humor, especially when people are killed and the lives and business of thousands of people are ruined. So I can see why BP did not want to go that route.

Defense counsel here must have made a very compelling argument, probably concerning unfair prejudice. I suspect their argument also relied upon contextual email and other emails between these friends showing that is how these boys actually talked to each other. Real jokers, and tasteless ones at that, as BP smartly admitted.

Yes, it is amazing what people say in electronic communications like email, not to mention text messages, private Facebook posts, and the like. Email remains king, as the Deepwater case shows, but so to do evidentiary objections. Also see LTN article on Google’s recent attempts to exclude emails on the basis of privilege in its billion dollar patent suit against Oracle. Here is the Sixth Circuit Court of Appeals Order denying Google’s Petition for Writ of Mandamus.

Lorraine v. Markel

Everybody should know Judge Paul Grimm’s Lorraine opinion, and should study it again before they go to trial. Lorraine v. Markel American Insurance Company, 241 F.R.D. 534 (D.Md. 2007). It is the best treatise on rules of evidence governing ESI. Who knows, you just might be able to devise an argument to keep an email out of evidence that would otherwise sink your ship.

Consider Judge’s Grimm’s summary at page nine of the one-hundred-and-one page decision in Lorraine of the kind of evidentiary issues that you should consider:

Whenever ESI is offered as evidence, either at trial or in summary judgment, the following evidence rules must be considered: (1) is the ESI relevant as determined by Rule 401 (does it have any tendency to make some fact that is of consequence to the litigation more or less probable than it otherwise would be); (2) if relevant under 401, is it authentic as required by Rule 901(a) (can the proponent show that the ESI is what it purports to be); (3) if the ESI is offered for its substantive truth, is it hearsay as defined by Rule 801, and if so, is it covered by an applicable exception (Rules 803, 804 and 807); (4) is the form of the ESI that is being offered as evidence an original or duplicate under the original writing rule, of if not, is there admissible secondary evidence to prove the content of the ESI (Rules 1001-1008); and (5) is the probative value of the ESI substantially outweighed by the danger of unfair prejudice or one of the other factors identified by Rule 403, such that it should be excluded despite its relevance.

Conclusion

Email and other electronic evidence, including video, are powerful forces in court rooms today. But just because you discovered relevant ESI, does not mean you will be able to use it or show it to the jury. It might, for instance, not be authentic, as some claim about this genuinely hilarious video.

The ninth step in the EDRM model, Presentation, is the home of complex, sometimes arcane evidence rules and unexpected rulings. The recent order by Judge Shushan in the largest case in the country shows that these evidentiary considerations and arguments are an essential part of e-discovery practice.

Objections to admissibility can come at you from many directions. For instance, in another order in the Deepwater case, Judge Shushan denied an objection to other email based on spousal privilege. She held that the email was not covered by this privilege because a husband had no reasonable expectation of privacy in emails sent to his wife from his work computer. See EvidenceProf Blog.

You neglect evidentiary analysis at your peril. Be prepared and do not be surprised when you hear some new outbursts at trial when you move to admit email into evidence, such as:

Defense Counsel: Objection your honor. Counsel has not proven that this e-mail was not sent or received casually, nor that its creation was just a mere isolated incident.

Plaintiff’s Counsel: But your honor, the witness testified that he was wearing a tuxedo when he sent this email. That proves it was not sent casually. Further, it could not have been isolated because our deduplication software found five copies of this email.

Get ready for some interesting appeals too.



Bottom Line Driven Proportional Review

January 15, 2012

I have been working on the problem of out-of-control e-discovery costs since 2006. At that time I phased out my general trial practice, went full-time e-discovery, and started this blog. (By the way, did you notice the new ® in the blog title? It means the U.S. Patent and Trademark Office granted me the trademark to e-Discovery Team.) I focused on the expense side because it was obvious that crazy high e-discovery cost was a core problem of civil litigation. It still is. Indeed, the high price of e-discovery, and the uncertainty of  these costs, are the main reasons most attorneys still avoid e-discovery like the plague. For more reasons see Tell Me Why?

The primary expense of e-discovery comes from the document search and review process; most estimate that it constitutes from 60% to 80% of the total. The core expense of the review process comes from the final manual quality control checks of each document to be produced to verify relevancy and to protect confidentiality by redaction and privilege logging. Confidentiality protection is an enormous problem in litigation. See Anonymous, An Open Letter to the Judiciary – Can We Talk? Parts One and Two.

Further, you cannot just dispense with final manual review. As I explained in my series Secrets of Search, Parts One, Two and Three, we are not going to turn that over to the Borg anytime soon. I’ve asked around and no law firms do that now. No experts advocate that approach either, even the most extreme advocates for automation (of which I’m one). The only exception I have heard of is in non-litigation circumstances, such as second reviews with production to the government. Automated review is nowhere near good enough to go it alone. You use predictive coding to speed up the final manual review to be sure, but only a fool (or con artist trying to get at a producing parties secrets) trusts coding software today without human verification.

My thinking and experiments since 2006 have focused on how to control the final review costs. By early 2008 I came up with one possible method that looked promising. I have been testing and refining this invention ever since with several e-discovery teams. I have also talked about it with many other attorneys, friend and foe, and used this new method in many law suits, big and small. I am now ready to write publicly about my proposed fix for the first time. I call it Bottom Line Driven Proportional Review and Production. A more technical description for it, the one I used in a legal methods patent application, is: System and Method for Establishing, Managing, and Controlling the Time, Cost, and Quality of  Information Retrieval and Production in Electronic Discovery. But I usually just call it Bottom Line Driven Review, and who knows, if it catches on – and I think it should because it really works – I may trademark that phrase too.

In the meantime, try it out. The more attorneys that use this method, the more accepted it will be by judges. Right now they are hearing it from my teams for the first time, and, like anything new, it takes some explaining and getting used to. But, once understood, it appears obvious, and I expect all thinking clients will demand that their attorneys use this approach. It saves money.

Bottom Line Driven Review

The bottom line in e-discovery production is what it costs. Believe me, clients care about that …. a lot! In Bottom Line Driven Proportional Review and Production everything starts with the bottom line. What is the production going to cost? Despite what some lawyers and vendors may tell you, that is not an impossible question to answer. It takes an experienced lawyer’s skill to answer, but after a while, you can get quite good at such estimation. It is basically a matter of man-hours estimation. With my method it becomes a reliable art that you can count on.

Price estimation is second nature to me, and an obvious thing to do before you begin work on any big project. That is primarily because I worked as a construction estimator out of college to save up money for law school back in the seventies. Believe me, estimating review costs is basically the same thing, projecting materials and labor costs. In construction you come up with prices per square foot. In e-discovery you estimate prices per file, as I will explain in detail later.

My new strategy and methodology is based on the bottom line. It is based on projected review costs, defensible culling, and best-practices of review. Under this method the producing party determines the number of documents to be subjected to costly final review by calculating backwards from the bottom line of what they are willing, or required, to pay for the production.

The process begins by the producing party calculating the maximum amount of money appropriate to spend on ESI production. A budget. This requires not only an understanding of the ESI production requests, but also a careful evaluation of the merits of the case. The amount selected for the budget should be proportional to the monies and issues in the case. Any more than that is unduly burdensome and prohibited under Rule 26(b)(2)(C), Federal Rules of Civil Procedure and other rules that underlie what is now known generally known as the Proportionality Principle. See Rule 1, Rule 26(b)(2)(C), Rule 26(b)(2)(B), and Rule 26(g) Federal Rules of Civil ProcedureCommentary on Proportionality in Electronic Discovery, 11 SEDONA CONF. J. 289 (2010); Oot, Kershaw & Roitblat, Mandating Reasonableness in a Reasonable Inquiry, Denver University Law Review, 87:2, 522-559 (2010); Also see Rule 403 of the Federal Evidence Code (inadmissibility of cumulative evidence).

The budget becomes the bottom line that drives the review and keeps the costs proportional. The producing party seeks to keep the total costs within that budget. The budget should either be by agreement of the parties, or at least without objection, or by court order. The failure to estimate and project future costs, and to decide in advance to conduct the review so as to stay within the budget, is the primary reason that e-discovery costs are so high.

After analysis of the case merits and determination of the maximum expense for production proportional to a case, the responding party makes a good faith estimate of the likely maximum number of documents that can be reviewed within that budget. The document count represents the number of documents that you estimate can be reviewed for final decisions of relevance, confidentiality, privilege and other issues, and still remain within your budget. The review costs you estimate must be based on best practices and be accurate (no puffing).

The producing party then uses smart search techniques and quality controls to find the documents most likely to be responsive within the number of documents that the budget allows. This is usually based on relevancy ranking, and thus the need for hybrid multimodal best practices in the search and review. Predictive coding is inherently rank based and so it makes bottom line driven review especially easy to do. That is one reason I am especially pleased to see the price of predictive coding software finally coming down. It can be done without predictive coding ranking to be sure, but it is harder to be accurate, especially with recall. Using best methods allows you to get the most bang for your buck, the core truth, and thus persuades the requesting party or court to go along with your budgetary limits. More on the new gold standards in a minute.

Example

An example may help clarify how it works. If you set a proportional cost for a case of $100,000, and estimate that it will cost you $5.00 per file for the final manual review before production of the ESI at issue, then you can  review no more that 20,000 documents and stay within budget. It is basically that simple. No higher math is required.

The only difficult part is the legal analysis to determine a budget proportional to the real merits of the case. But that is nothing new. What is the golden mean in litigation expense?  How to balance just, with speedy and inexpensive? The essence of the ideal proportionality question has preoccupied lawyers for decades. It has also preoccupied scientists, mathematicians, and artists for centuries. They claim to have found an answer that they call the golden mean or golden ratio:

In law this is the perennial Goldilocks question. How much is too much? Too little? Just right? How much is an appropriate spend to produce documents? The issue is old. I have been dealing with this problem for over thirty years. What’s new is applying that legal analysis to a modern-day high-volume-ESI search and review plan. Unfortunately, unlike art and math, there is no accepted golden ratio in the law, so it has to be recalculated and reargued for each case. (Side Note: If the golden ratio were accepted in law as an ideal proportionality, the number is 1.61803399, aka Phi. That would mean 38% is the perfect proportion. I have argued that when applied to litigation that means the total cost of litigation should never exceed 38% of the amount at issue. In turn, the total cost of discovery should not exceed 38% the total litigation cost, and the cost of document production should not exceed 38% of the total costs of discovery.  (It’s like Russian dolls that get proportionally smaller.) Thus for a $1 Million case you should not spend more than $54,872 for document productions (1,000,000 – 380,000 – 144,400 – 54,872). See Losey, R., Beware of the ESI-discovery-tail wagging the poor old merits-of-the-dispute dog. But I digress too far.)

Estimation for bottom line driven review is essentially a method for marshaling evidence to support an undue burden argument under Rule 26(b)(2)(C). It is basically the same thing we have been doing to support motions for protective orders in the paper production world for over sixty years. The only difference is that now the facts are technological, the numbers and variety of documents are enormous, sometimes astronomical, and the methods of review are very complex and not yet standardized.

The calculation of projected cost per file to review can be quite complicated, and is frequently misunderstood, or is not based on best practices. Still, in essence this cost projection is also fairly simple. You basically project how long it will take to do the review and the total cost of the time. Thus, for example, and this is a gross over simplification, in a review project of 20,000 documents (after computer assisted culling – it probably started as 100,000 or 200,000), if the average review and coding rate is 50 files per hour, it will take 400 hours to complete. If the projected total cost for the reviewer time, including supervision and other costs, is $250 per hour, the projected total cost for the review is $100,000 ($5.00 per file).

This may seem high when you consider the cost of contract lawyers is $50 or less for their time, but you have to also include expensive partner and senior associate management time, direct supervision, quality control reviews, and privilege logging, etc. Do not be fooled by promises of $1.00 per file charges by contract review companies (or even less than that). That does not include the law firm of record time and expenses to supervise, etc., and often is based on a pre-culling rate for file count. In this business one of the hardest aspects for good estimation is getting true apples-to-apples comparisons from vendors.

Also, quality control is important and best practices can be expensive, even though with bottom line driven review the total cost is still dramatically less than old-school. As I said before, when you talk about capping the number of documents you review, you also have to talk about finding the most likely relevant documents for this capped review. You have to provide the most bang for your buck, the most truth. That, along with transparency to earn trust, is a key to the success of this method, a key to persuading the other side or court to accept this new approach to reasonable discovery.

Estimate of Projected Costs

Another key to persuade the requesting party or court is to be sure your estimate is realistic. You cannot just dream up estimates, or puff the likely expense. The estimate must be based on knowledge of the types of documents that you will be reviewing in your particular case. It must be based on the times that you find it takes for manual review of the documents. Some document collections are faster and easier to review than others. The speed is measured in files per hour. (I like the sound of that, plus pages per hour is just a relic of the paper world. Computer files don’t have pages, only paper print-outs do.)

The typical speeds we see today in final manual review are anywhere from 25 files per hour, for collections with a lot of dense long documents and crappy review software, to 100 or even 200 files per hour for collections with easier to skim documents and the best software. Putting aside the question of the wide divergence in the quality of review software, we tend to see faster files per hour rates in email-heavy cases with few attachments, than we do in cases with a high percentage of complex documents and spreadsheets. You have to know your case, know your ESI, to make a proper estimate.

The projected costs must also be based on best practices for economical review and not be inflated. You can’t justify $500 per hour partners to do all of the review (although they may be needed as subject matter experts to do the seed set review in predictive coding). Of course, old-fashioned full manual review is out of the question. It has to be hybrid with computers doing most of the first-pass document culling. Even if you use technology assisted review, you still must also use best practices for methods. You cannot justify old-fashioned stupid review methods, such as batch out to reviewers solely based on first in, chronological, or just random. It has to be a best practice based multimodal type of review, where, for instance, you batch out documents for manual review based on issues, clusters, language, or other smart review methods. Best practice also means quality control and a random button as discussed at length in the Secrets of Search series. If you do not use the nine best practices to get the most bang for your buck, the core truth, the requesting party or court may not agree to limit the number of documents to be reviewed.

The processes behind the estimate should also be transparent. This means you should be willing to disclose it to the requesting party. That is how you can convince them that the estimate is reasonable and that you are not still stuck in the old paradigm of hide-the-ball discovery games. I cannot overstate how important it is to develop trust between counsel on discovery and often the only way to do that is through transparency. You do not have to disclose all of your trade secrets, but you have to keep the requesting party pretty well informed and involved in the process. That is what cooperation looks like.

In general, I have found that in 2011, $5.00 per document was a good place to start in projecting costs for review of a typical email collection (an email is one file, and each attachment is another). This price includes the expensive redaction and privilege logging processes. Review with a simple relevant or irrelevant coding is the easiest and cheapest to do, and is also fairly rare. There are usually multiple additional factors to consider.

The five dollars per file is a starting point of estimation, a rule of thumb that is often correct, but sometimes way off. It is comparable to the rule of thumb in construction estimation where you start with the typical costs to build on a square footage basis. But in some cases, especially ones involving cross-border issues, the costs could go much higher, as high as $15 per file. In others, where the review is simple, it could go as low as $2.00 per file. It is just like construction where various buildings in different locations have different costs.

The $5.00 per file price is based on my recent experiences in 2011. In 2009 the average cost was more like $6.50 per file, and I expect average costs will keep going down a little in 2012 and then level off.

It is important to note that you can justify starting with a much higher number based on legal precedent alone. For instance, the Department of Justice spent $9.09 per document (or file, same thing) for review in the Fannie Mae case, even though it used contract lawyers for the review work. In re Fannie Mae Securities Litig., 552 F.3d 814, 817 (D.C. Cir. 2009) ($6,000,000/660,000 emails). There were no comments by the court that this price was excessive when the government later came back and sought cost shifting. My current $5.00 per file general rule is also lower than the $6.09 per document that Verizon paid for a massive second review project that enjoyed large economies of scale and, again, utilized contract review lawyers.  Roitblat, Kershaw, and Oot, Document categorization in legal electronic discovery: computer classification vs. manual review. Journal of the American Society for Information Science and Technology, 61(1):70–80, 2010 ($14,000,000 to review 2.3 million documents in four months).

So, if your experience suggests a starting review rate higher than $5.00 per file, there is legal justification to use a higher number. Just be prepared to go to the next steps and back it up.

The price per file is just a starting point, a way to get a quick picture, a quick estimate, without doing all of the detail work. A more accurate picture starts to emerge with sample reviews and more detailed analysis of the tasks required in the review and the actual data to be reviewed. You have to, as I like to say, get your hands dirty in the digital mud. You have to know your ESI collection. Even in just one type of ESI, the one most common in e-discovery today, email and attachments, the variances in email collections can be tremendous.

Once you get your hands on the data you need to start to breakdown and analyze the time involved in the various tasks required in the review project. Here, as in construction estimation, the spreadsheet is your friend. This move to actual examination of the ESI at issue, and study of the specific review tasks that need to be performed in your case, is equivalent to the move in construction estimation from rough estimates based on average per square foot prices, to a careful study of the buildings plans and specifications, and a site visit with inspection and measurements of all relevant conditions. No builder would bid on a project without first doing the detailed real world estimation work.

Even in the same organization, and just dealing with email, the variances between custodians can be tremendous. Some for instance may have large amounts of privileged communications. This kind of email takes the most time to review, and if relevant, to log. High percentages of confidential documents, especially partially confidential, can also significantly drive up the costs of review. All of the many unique characteristics of ESI collections can effect the speed of review and total costs of review. That is why you have to look at your data and test sample the emails in your collection to make accurate predictions. Estimation in the blind is never adequate. It would be like bidding on a building without first studying the plans and specs.

Even when you have dealt with a particular client’s email collection before, a repeat customer so to speak, the estimates can still vary widely depending on the type of law suit, the issues, and on the amount of money in controversy or general importance of the case.

Although this may seem counter-intuitive, the truth is, the complex, big-ticket cases are the easiest to do e-discovery, especially if your goal is to do so in a proportional manner. If there is a billion dollars at issue, a reasonable budget for ESI review is pretty big. On the other hand, proportional e-discovery in small cases is a real challenge, no matter how simple they supposedly are. Many cases that are small in monetary value are still very complex. And complex or not, all cases today have a lot of ESI.

The medium size to small cases are where my bottom line driven proportional review has the highest application for cost control and the greatest promise to bring e-discovery to the masses.

The Quest for Gold

In Secrets of Search Parts One, Two and Three, I outlined the five key characteristics of search today, using the rubric of secrets. To support my outline I used the latest scientific research on legal search, and focused on the work of William Webber. Re-examining the Effectiveness of Manual Review. In Part Three I summarized my ideas on search and review using the symbol of the Pythagoreans, the five-sided polygon, or pentagon:

With this blog on Bottom Line Driven Proportional Review I add a sixth idea, where the process gets real and takes money into consideration. Here I have shared my method to use estimation, projections, budget, cooperation, transparency, and the legal doctrine of proportionality to control the costs of search and review. With this final piece my proposal for a new gold standard of search and review is complete.

Bottom Line Driven Review is a method to try to control the key problem in electronic discovery law today, the run away costs of review. The number of documents we have to review seems to double every two to three years, so this new legal method is imperative. New and better software, especially predictive coding type, is also important. As shown, the ranking of relevancy and other categories built into the latest algorithms is, under my bottom line driven analysis, an especially helpful new capability.  You rank the documents within your budget limit that the computer predicts, based on your training, will be the most relevant to your case. But new technology alone is not enough. We must also have new legal methods. Technology and law have to work together, grounded in science, to create a new gold standard.

In Secrets of Search Part II, I proposed a new gold standard, one that would replace the now disgraced old-gold brute-force manual review unassisted by technology. I drew upon the findings in the latest scientific research, legal literature, and my over thirty years of experience with discovery to create a first draft list of the nine criteria of the new gold. The first criteria listed was Bottom Line Driven Proportional Review, which I promised to explain later and have now done so. Here is how I put it in Part II:

The old gold standard of average human reviewers, working in dungeons <smile>, unassisted by smart technology, and not properly managed, has been exposed as a fraud. What else do you call a 28% overlap rate? We must now develop a new gold standard, a new best practice for big data review. And we must do so with the help and guidance of science and testing. The exact contours of the new gold are now under development in dozens of law firms, private companies, and universities around the world. Although we do not know all of the details, we know it will involve:

  1. Bottom Line Driven Proportional Review where the projected costs of review are estimated at the beginning of a project (more on this in a future blog);
  2. High quality tech assisted review, with predictive coding type software, and multiple expert review of key seed-set training documents using both subject matter experts (attorneys) and AI experts (technologists);
  3. Direct supervision and feedback by the responsible lawyer(s) (merits counsel) signing under 26(g);
  4. Extensive quality control methods, including training and more training, sampling, positive feedback loops, clever batching, and sometimes, quick reassignment or firing of reviewers who are not working well on the project;
  5. Experienced, well motivated human reviewers who know and like the AI agents (software tools) they work with;
  6. New tools and psychological techniques (e.g. game theory, story telling) to facilitate prolonged concentration (beyond just coffee, $, and fear) to keep attorney reviewers engaged and motivated to perform the complex legal judgment tasks required to correctly review thousands of usually boring documents for days on end (voyeurism will only take you so far);
  7. Highly skilled project managers who know and understand their team, both human and computer, and the new tools and techniques under development to help coach the team;
  8. Strategic cooperation between opposing counsel with adequate disclosures to build trust and mutually acceptable relevancy standards; and,
  9. Final, last-chance review of a production set before going out the door by spot checking, judgmental sampling (i.e. search for those attorney domains one more time), and random sampling.

I have probably missed a few key factors. This is a group effort and I cannot talk to everyone, nor read all of the literature. If you think I have missed something key here, please let me know. Of course we also need understanding clients who demand competence, and judges willing to get involved when needed to rein in intransigent non-cooperators and to enforce fair proportionality. Also, you should always go for confidentiality and clawback agreements and orders.

I repeated this nine-point list of the new gold in Part III of Secrets of Search, and again repeated my invitation for input with a comment on standards that bears repetition:

I have probably missed a few key factors. This is a group effort and I cannot talk to everyone, nor read all of the literature. If you think I have missed something key here, please let me know. I will be at Legal Tech New York for three days with four presentations. Seek me out and let’s talk. You can reach me at ralph.losey@gmail.com.

You may note that I am herewith joining the call of other leaders in the field to develop best practice standards, notably including Jason Baron, and have overcome my initial reluctance to go there for a variety of reasons. See Jason R. Baron, Law in the Age of Exabytes: Some Further Thoughts on ‘Information Inflation’ and Current Issues in E-Discovery Search, XVII RICH. J.L. & TECH. 9, at 29-33. My concerns on arbitrary standards and unfounded malpractice claims remain, but I think we have no choice but to develop some basic industry standards. The nine characteristics of good document review outlined above constitute a first modest step in that direction.

I will be at LegalTech NY on January 30th, 31st and February 1st. My invitation for dialogue and input from readers continues. Seek me out and let’s talk, but spare me the sales pitches, please. (I am, however, open to writing pitches.) My main focus right now is the quest for a new gold standard of search and review. I know that many of you share this quest, so let’s use the power of groups, or team work, to make it happen. What do you think of my nine-point first draft list? Any suggestions to add new criteria, consolidate, or add to what any of these nine mean?

Two of my readers have already responded to my outreach for input, Bill Hamilton and Larry Chapin. They provided some more concrete details to the criteria number six in the list, new tools and psychological techniques. They submitted an essay on one such new technique, which is actually of ancient origin, and well-known to the best trial lawyers, namely the use of story and storytelling to improve legal review. Storytelling: The Shared Quest For Excellence in Document Review. If you have ideas for an article, please send me an email with outline or first draft and I will consider it for possible publication.  As coaches everywhere love to say, there is no “i” in team, even if there is in e-Discovery Team ® <grin>.

Conclusion

I have a dream, like all humans do. It is one of the key attributes that separates us from machines. My dream is not as noble or stirring as the public dreams of Martin Luther King or John Lennon. Those were grand dreams indeed. But my dream is important to me, and you can probably relate to it. I dream of a day where man and computer work together to bring truth and justice for all, not just the elite few who can afford it now. I dream of a day where e-discovery is affordable and used in all size cases. This dream of truth and justice for all is deeply rooted in my psyche. I suspect it is in yours too. We all grew up understanding the importance of Superman’s never-ending battle for truth, justice, and the American way. Join me in this battle. Join the e-discovery team fight for truth, justice, and the American way. (For my many readers outside of the U.S., my American way reference is not meant to be nationalistic or exclusionary, but rather to refer to the highest ideals of a great country.) All professionals in the field are invited. So too are computers, especially the latest generation of super smart ones. Yeah, their programmers too. All behind the scenes coders, techs, and scientists are an important part of the e-Discovery Team.

High tech lawyers working with computers and their handlers are key to my version of the archetypical American dream of truth and justice. Techs and computers helped bring about the nightmare we must now overcome – the explosion of ESI that hides the truth and makes justice too expensive. They helped get us into this mess, they can help get us out. We cannot turn back.

Jason Baron’s depressing prophesy of information dystopia, where we all drown in a flood of information, is no prophetic dream. It is a realistic assessment of the current state of the law and the discovery of electronic evidence. The reality today is that the vast majority of lawyers avoid the discovery of information in computers, even though that is where the truth lies. They have a prejudice against it. They believe in the inherent superiority of paper. We all know that most of the truth left paper filing cabinets over a decade ago (with the sole exception, perhaps, of the federal government), yet most lawyers still look there, and only there, for justice. Jason’s dream of extreme information overload is a projection of the current reality getting worse. He speaks the truth, but only if we don’t do something about it, if we don’t continue in the never-ending battle. Truth and justice can triumph. They must.

The motivation is clear. So is the solution. Imagine a world where the fool’s errand, the paper chase, comes to an end. Imagine a world where these old ways, based as they are on ignorance and delusion, are replaced by an affordable and effective process of e-discovery. Imagine a world where all the people, the litigants in all size cases, can all afford to do e-discovery. Imagine all the people living life in justice. It isn’t hard to do. As John Lennon said: You may say I’m a dreamer, but I’m not the only one. I hope some day you’ll join us. And the world will be as one.

I have a dream of a new method of technology assisted discovery, where Man and Machine work together to find the core truth. This day will come, in fact it is already here. As William Gibson said: “The future is already here – it’s just not evenly distributed yet.” The key facts you need to try a case and to do justice can be found in any size case, big and small, at an affordable price. But you have to open your mind. You have to embrace change and adopt new legal and technical methodologies. The Bottom Line Driven Review method is, I suggest, an important part of that answer. It is working for me today, it can work for you too. Our dreams can come true. The nightmare scenarios of justice for only the super-rich can be avoided. The battle for truth and justice must continue.

I  see a way out, where we can overcome, where truth and justice can be attained for all the people. I see a day where the truth in our computers can be found and brought to the court room for justice to prevail.

Although I also have a dream of a new generation of tech-smart lawyers, who understand and apply the new methods, the new gold, to keep e-discovery available for all. We do not need to wait for this slow gradual change. We can win the battle now, even without the young geek Supermen. The time for change is now – in this generation, not the next. As King said in his I Have Dream speech, this is not time to take the tranquilizing drug of gradualism.

Join me in the dream of e-truth and justice today. As a team we can get there, we can and shall overcome, we shall be free of the paper-prejudices of the pre-computer world. And when that day comes, let the bells of truth and justice ring throughout the world. To quote the end of King’s famous speech:

And when this happens, when we allow freedom to ring … [we] will be able to join hands and sing in the words of the old Negro spiritual, “Free at last! free at last! thank God Almighty, we are free at last!”


Storytelling: The Shared Quest For Excellence in Document Review

January 8, 2012

Guest Blog by William F. Hamilton and Lawrence C. Chapin.

Bill Hamilton is an attorney with nearly thirty years of experience in business litigation who is a partner at Quarles & Brady. Bill also serves as the Dean of the E-Discovery Department of Bryan University, which includes an online educational program in e-discovery project management. Bill is also an Adjunct Law Professor teaching Electronic Discovery and Digital Evidence at the University of Florida, and has frequently contributed to this blog. See Eg. The E-Discovery Crisis: An Immediate Challenge to Our Nation’s Law Schools, and The E-Discovery Sanctions Cube.

Larry Chapin is an attorney with 30+ years experience, including corporate Wall Street law, who now works as a contract review lawyer in New York City. Larry has taught at the New School for Social Research in NYC and currently serves on the Board of Directors for an asset management company in Stockholm Sweden. Larry is the first graduate of our e-Discovery Team Training program. He contributed a must-read blog here earlier this year entitled Contract Coders: e-Discovery’s “Wasting Asset”?

_____________

EDITOR’S NOTE: Over the last several blogs on the Secrets of Search we have examined the latest scientific research on manual and automated reviews. The research shows that although brute-force manual linear review is as dead as a doornail, or should be, there is still an important place for skilled human reviewers and review, even in the latest predictive coding models. But the emphasis is on skilled human reviewers and skilled methods. Simply asking some lawyers to look at documents all day on a computer screen for weeks on end and decide relevance or not is unacceptable. If that is how you conduct manual reviews, and just bid things out to the lowest paid reviewers, then you are inviting error. You probably would be better off turning it over to the Borg, and just skipping final quality control reviews altogether. But if you care about quality, if you are diligent in the protection of client confidentiality – and as a lawyer you have a clear ethical duty to do so – then you must improve and innovate on manual review. This guest blog by professional reviewer, Larry Chapin, and an expert in e-discovery and project management, Bill Hamilton, help show the way.

In Part III of Secrets of Search I listed a nine-point checklist for quality reviews. Point number six was: “New tools and psychological techniques (e.g. game theory, story telling) to facilitate prolonged concentration … ” This guest blog will flesh out a new approach that Chapin and Hamilton have developed to use storytelling to improve the quality of contract reviews. I think this is a great idea. Lawsuits are essentially a battle of competing stories. They can become high drama as the Casey Anthony trial that took place across from my office in Orlando showed in 2011. Good trial lawyers already know the importance of story to a case. They should quickly understand this idea and appreciate how this new review technique could help their cause. All attorneys, and especially companies that do contract review work, should look into including this new technique into their projects. Feel free to email Bill Hamilton or Larry Chapin to see how they may be able to assist.

_____________

By putting its faith in logic, control and optimization, command-and-control management has lost sight of the crucial role that passion plays in human action.

Stephen Denning, The Leader’s Guide to Storytelling

_________

Storytelling: The Shared Quest  For Excellence in Document Review

by William F. Hamilton and Lawrence C. Chapin

What is the future of large-scale human document reviews? With the startling advances of search technology, is human document review about to be consigned to the dustbin of history? Some believe so. Yet, others think that the death of human review has been grossly exaggerated. There is no doubt that computer assisted reviews will be increasingly important for large and even moderate scale reviews. However, the contest between human and computer, between manual and automated review is far from over. In this blog, Ralph Losey recently discussed some of the implications of the fascinating work of information scientist William Webber. It seems that in the proper setting, the best human reviewers can still out-perform the automated review.

Watson may be the Jeopardy winner, and IBM’s Deep Blue the chess champion, but the identification and evaluation of documents in the litigation context stretches the utility of computer algorithms. In document review setting, well-trained, well-led and properly motivated women and men are, in fact, able to excel. How can we build reviews to maximize human review performance? What can be done about the powerful disincentives of long hours of dreadfully monotonous work at rates of pay already low and still in decline? Put more constructively, what can be done to tap the intelligence, marshal the talents, and harness the energies of the contract lawyers who fill the ranks in the typical review? How do we rid ourselves of the upstairs-downstairs mentality that isolates and confines our reviewers, turns them into servants and cripples their reviews?

We believe that the answer may be found in an approach to document review that harkens back to a simpler time, before litigators faced the enormous volumes of documents common in our digital age. That is to say, answers are to be found in building reviews around the art of storytelling. Shakespeare was right: the entire world’s a stage, and all the men and women players. Certainly, litigation is drama. It is the drama of competing and clashing human passions. It is the stuff of stories. Document reviews must be understood as a central player in the litigation storytelling process.

A fundamental shift in the way that lawyers think, speak, and conduct document reviews is required. We propose a new paradigm. We propose building  “story-centric” reviews. First, though, let’s face it. Storytelling usually gets a hard knock. It’s for children. It’s the stuff of fairy tales. Storytelling is said to have no place in the hard-edged, logic driven, command-and- control culture to which the legal and business communities have grown accustomed. Euphemisms – like “business narrative” – have been invented so that stories might have a place of some kind in the working world.

Yet, storytelling has long been a part of lawyering. Good trial lawyers have always known that cases are won on the strength of their story. Even crazy ones can be convincing. Empirical studies also show that appellate briefs, too, are more persuasive if they tell stories rather than rely on logic alone.  A case can’t resonate with a judge or jury – emotionally, intellectually, or intuitively – unless it’s tied to a compelling story. The litigation team itself can’t know what evidence most belongs before the court unless it knows the story to which the evidence belongs. The discovery process serves to yield the elements and the contours of the story, and shed light on the connections between the cause and effect that are at its heart. It is the job of the entire team – including document reviewers – to construct the most persuasive story possible, and to diminish and discredit the tale told by the other side.

Our experience, unfortunately, is that too many lawyers separate document review from that creative process. They fail to see document reviewers for what they are: investigators sharing fully in the common tasks of discerning, shaping, and telling the client’s story. This kind of engagement requires that the review structure and evaluation adopt the elements and language of the story. It’s an orientation that triggers active reviewer participation and has real potential to address the problems now plaguing review. We believe that the failure to engage the review team in this way results in a process that is less true and just than it might be.

Suggestions to Add Story to Document Reviews

Accordingly, we offer a series of suggestions for the use of storytelling in the discovery process, toward building a story-centric review.

First, at the outset, use the client’s story and its themes to define the goal of the review project. Articulate clearly the central purpose of every reviewer’s contribution: to enable the story to be told. The story needs to remain the constant center of their focus. We might liken reviewers to crew members who sailed in search of new lands during the great age of exploration. Not every day was filled with adventure. During more days than we realize, their ships were becalmed on windless seas. What got them through those days was their purpose for being there, the vision of things that had launched their journey. So they kept their focus, mindful always of the possibility of a sighting and the promise of discovery. In that way, let the story of the case be what drives and sustains the review team. Remember that the critical document, like new land, may be just a moment away. Everyone needs to stay alert.

Project metrics should be designed to reflect this orientation. Story-centric metrics should measure: linkage, the degree to which documents pull the story together tightly to help tell the tale; gravity, the degree to which the document collection gives weight, heft and power to the tale; and resonance, the degree to which documents provide compound richness to the story.

“Linkage Docs” provide the basic story line. They establish the necessary cause and effect that transforms otherwise isolated facts into a real story. They reflect the fact that every story is composed of details that unfold at a time, place, during a temporal extension, and that involve human motivations and conflicts. They are the sinews, the connecting tissues without which a story does not exist. For example, in a case involving a business breach of contract for failure to maintain premises, a document that shows the defendant’s  financial distress shortly before the breach establishes linkage. Linkage allows the story to begin to congeal.

Links are related to gravity, but different. “Gravity Docs” are those documents that move the story events out of stasis towards resolution. They function as a pivotal column or anchor that marks a transition, direction or resolution within the story. We ultimately want links that tie to these pivotal columns. The documents with gravity are the turning point documents.

Finally, “Resonance Docs” are those documents that strike a chord in us. They evoke sympathies in ways that align us with the actors in the story. They establish decisive commonalities between persons hearing the story and those person within it. In helping the story ring true, they persuade us. The lead us safely past any temptation to turn to unpersuasive  clichés, triteness, and banality in telling the story. A document that provides resonance will  tie story links (sub-plots) and pivotal gravity markers (the main plot) together.

The story can have links  and pivoting documents, and still be unpersuasive. Resonating documents provide  understanding, the “now I get it feeling,” and are often documents that directly speak to human motivation and intention ( or give rise to strong presumptions of actual motivation).  The irony of the traditional review is that a  review team shackled by  traditional coding blinders can row past a proverbial “smoking gun” document and not recognize its value to the story. Reviewers should not resemble the galley rowers portrayed in Ben-Hur who are driven to exhaustion as the pace of the review escalates to ramming speed.

The review team must be able to recognize documents with story-centric values, not merely label documents  as responsive or non-responsive according to abstract coding rules. A good review team requires graphics. The review team’s identification of Linkage Docs, Gravity Docs and Resonance Docs compose the story as the review progresses. The review team needs to literally see the story mapped as it develops. The story-centric review replaces the  traditional white board with a large story board that simultaneously shapes and is shaped by the review.

Linkage, gravity, and resonance can be seen as three overlapping circles. In practice, depending upon the story, the circles may vary in size and shape (e.g. oblong),  but in the overlapping section we are likely to find the 7±2 documents that the trial team needs to tell the winning story.

So invest your own time in a solid understanding of the client’s story. Invest more time still in discussing it with the review team, so that together you reach a shared grasp of its themes and important facts. This initial investment may turn out to be substantial, but the rewards will be enormous. Don’t make the mistake of taking more time to talk about the software the team will be using than on the story they will be helping to tell.

On one project of which we are aware, the trial and discovery teams developed a highly detailed, rule-based review book. It was more than one hundred and fifty pages long, but devoted fewer than one hundred words in not even ten lines of text to actually telling the client’s story. Don’t do that. Don’t let a narrow focus on the chains of logic obscure the compelling threads of the underlying narrative.

Second, use storytelling with the review team to create a sense of quest. Remember again our metaphor of voyage. The reviewers are, of course, engaged in a real pursuit – weaving a tight, compelling story worthy of being told. Beyond that, quests intimate a feeling of authentic commitment – even a passion – among members of the review team. The power of the story transforms the document review experience. Stories have a unique ability to bind members of the team to a broader purpose, and to each other. As we work together, we are reminded of the human drama that has already unfolded for our client. We remember, too, that our own stories are still unfolding in our work together. On several levels, then, we feel connected. The present has new and important depth.

The organization of the review teams is critical to a sense of quest. The reviewers must identify with the quest to face its hardships and celebrate its victories. The review itself should be seen as a story that has drama, disappointments, dead ends, clues, and ultimately triumph. Banish forever the factory concept of document review as a mass production based on the principles of Taylorism and Fordism.

Third, use of a lawsuit’s stories serves to continually define and redefine the team’s analytical tasks, and to sharpen their focus as the review progresses. Use graphics and models to demonstrate the elements and cohesion of the story as the review is taking place. If the reviewers can’t understand and relate to your story, no judge or jury ever will. Emphasize that the story being told to them is provisional, and that their investigation may, in fact, bring about a retelling of the story. Reiterate key themes as you talk to the members of the team. Challenge them to discern both its strengths and its weaknesses. Provide opportunities for them to share their impressions and their hunches, their discoveries and concerns. This might be as simple and productive as it was on one recent project in which every day or so, one of the law firm’s associates on the case went among the reviewers and asked them, “What are you finding? What do you think?”

It is hard to exaggerate the importance of these interactions. They’re not drive-by questions that are all too easily answered with a yes or no. They are chances for leaders to demonstrate deep listening. They are open-ended invitations to contribute to the group’s learning. They are small streams of one-on-one talk that contribute to what Denning has called the river of conversation that keeps the project moving forward. They are also brief opportunities for members of the team to be acknowledged and affirmed in their work. The goal is to create short but meaningful exercises in team building and flushing out the law suit’s story.

Fourth, share “discoveries” among the team. After all, many of the decisions made by reviewers are close calls, and need to be shared and socialized for consistency and accuracy. In part, this question of sharing is a matter for science.  There are, no doubt, a wide variety of wiki-like technologies that might be brought to bear for purposes of shared learning. But there are several things to be remembered in that regard. First, the technologies seem to be variations on the same theme. That is, they provide ways in which reviewers can articulate their rule-based questions, which are then migrated upwards for consideration by someone on the trial team. The review team is then given access to a database containing all the questions and their answers.  There are many other technologies available for broader, more open learning, but sadly they are rarely employed. It is ironic that in this digital era that has spawned massive reviews, few of the readily available social networking and communications tools have been applied to “humanize” the review process. Then again, the reason is clear: non-story-centric reviews seem to have little use for creativity and collaboration.

The reviewers should be organized into “review teams.” Review teams should ideally be small teams (10-15 reviewers) located in physical proximity. The identification of Linkage Docs, Gravity Docs, and Resonance Doc should be quickly shared and celebrated. Review team members should encourage one another. Review metrics should not exclusively focus on number of documents reviewed per hour. All genuine work and creativity has valleys and plateaus. A review should not be a forced march. The football team regroups in the huddle before each play as it creatively marches down the field. A good, productive review will have its own rhythm. To facilitate this rhythm the successes of one review team should be shared with other teams. Success encourages success and friendly goal oriented competition. Reporting, feedback, and encouragement should be emphasized.

Why have we ignored the lessons of sports competition in our document reviews? Sports motivation coaches are paid millions to inspire athletes and teams. Yet in million dollar reviews, and where even more is at stake in the litigation, we tolerate performance that would be banished elsewhere. What is needed are the genuine “review coaches.”

Fifth, collaboration thrives on human face-to-face contact. The 2009 Text Retrieval Conference (TREC) validated this important point. The TREC team sponsored by the School of Information Sciences of the University of Pittsburgh was provided with shared digital space that allowed them to communicate with each other and to store and organize results. Early on, communication between the searchers consisted mostly of texting, with very little actual, verbal communication. Later on, as tasks became more difficult and the need to collaborate became greater, real talk between the searchers virtually replaced texting, as trust and familiarity developed.

The Pittsburgh team results suggest that while wiki-like technologies are useful in knowledge sharing, trust-based communication such as that involved in document review will gravitate towards ordinary face-to-face communication. It also reminds us that, especially in knowledge sharing exercises, “talk is work” as Stephen Denning has said. This may be another surprise for readers. Absolute silence may not simply mean a focused project. It may be signal a failure to share critical information.

It is precisely in such spontaneous conversations that members of the team draw from the pool of cognitive diversity. A good team will comprise individuals with different strengths, training and backgrounds. When left to themselves high functioning teams learn to take full advantage of their diversity. Good leaders will make sure that team members know their neighbors. Sadly, that rarely happens. On one project related to the life sciences, one reviewer had nearly a decade of law firm experience in that field. But the rest of the team never found out, because the supervisors never thought or wanted to ask. In another project involving the global capital markets, one of the reviewers had two decades of high-level experience trading financial instruments. He decided not to reveal that to anyone. Somehow, the message had gotten across to him that the smart approach to “surviving” document review was to “keep your head down.” It’s a saying you hear a lot on the project floor. What a terrible reflection upon the kind of “supervision“ and “management” to which document reviewers are commonly subjected!

Sixth, use storytelling to generate the connections that will make document review a meaningful experience. The most profound concerns about document review have always revolved around the lack of connection between the purposes of the work and those doing it. Storytelling, on the other hand, is all about connections. Remember what stories are: accounts of causally connected events. So, document review is really an investigation into the nature of those connections. Further, stories are a shared human experience; we all have our own stories. In working together to formulate the story of the case, our own stories become part of the story of the group.

Storytelling establishes common meanings and transmits the values characteristic of high-performing teams. Denning writes that the most striking thing about being part of a great team is the meaningfulness of the experience. “People talk about being part of something larger than themselves, of being connected, or being generative … their experiences as part of truly great teams stand out as singular periods of life lived to the fullest.” We have seen the reviewers’ faces light up, their smiles appear, and genuine excitement erupt when participating in story-centric reviews.

In our view, these are issues of leadership, more than management. The dominant language of document review management reflects the values of traditional command-and-control culture. Such management is about structure, schedules, budgets and the like. This management operates out of hierarchical schemes and derives its presumed effectiveness from the power of authority. Naturally, such things have their place in well-run reviews, as most published literature attests. Metrics matter; things need to be measured and counted. But traditional measures of performance are not always the most revealing.

Consider, for example, the story told in the movie Moneyball about Billy Bean’s discovery that the “five tools” traditionally used to evaluate baseball players missed the mark. Metrics such as batting average and speed on the bases mattered, but they were really pointing to something else that was the most telling factor between ball players on winning and losing teams, that is, on base percentage. What mattered was how often batters got on base by any means. What if the metrics relied upon in review command-and-control structures – such as documents per reviewer per hour – are off the mark?

Seventh, remember that the document review may have to be explained and defended. If challenged as to its reasonableness, the review will have its own story to be told. The McDermott case now is a powerful reminder of what may be at stake. Stories about the labors of well equipped, fully engaged, and highly motivated reviewers are bound to be the most persuasive stories of all.

Conclusion

Good storytelling lies at the very heart of good litigation. Neither the information revolutions of the digital age, nor the dizzying advances of technology have changed that.

The challenge lawyers face is that of adapting the storytelling art to the requirements and capacities of our day. Discovery and review must articulate the client’s most compelling story. It must disable the counter-story told by the other side. Story-centric reviews serve as powerful levers for the other assets – both human and hard – committed to the work of review excellence. This is important work. Justice depends on a compelling story and injustices arise when we forget that.