One of the key things I learned from a number of mentors in the mass tort defense league was the importance of front-end loading cases. By that I mean getting a grasp early on of the exposure and the \u201coh shit\u201d documents and then immediately formulating the appropriate case strategy based on that grasp. Over and over again, the approach proved itself as the case progressed.<\/p>\n
Another thing I learned along the way was the improved depositions and cross examination of witnesses where I, as the most knowledgeable and experienced lawyer on the case, could myself review and locate the most important documents, as opposed to asking an associate or paralegal to do that work and then report to me.<\/p>\n
The problem with both, of course, was always the cost and time involved to do this important work. All too often clients would balk at paying for this work early on. Convincing them otherwise was a pain, to say the least.<\/p>\n
The Deep Dive Tool<\/strong><\/p>\n Enter Everlaw\u2019s<\/a> new Deep Dive<\/a> tool, which promises to address both challenges. The tool is an enhancement of what was previously called Project Query, according to the Everlaw press release. Deep Dive was announced in open beta at the ILTA conference this week.<\/p>\n In essence, the tool allows the user to query a large data set of inputted documents using natural language. The tool allows users to simply ask questions related to specific issues, parties, or events and get answers. In a class action, you might ask the tool something like \u201cis there any support for the claims that there are common questions of fact among the various putative class members.\u201d<\/p>\n The answers are supported with a list of facts and referenceable documents so users can dive deeper into the breakdown of information available as part of the response. In other words, the tool cites the documents that it uses to answer the questions. You can then drill down into the documents and ask more specific questions based on a subset of the cited documents. The tool does not go outside the documents to answer any inquiry.<\/p>\n Importantly, according to AJ Shankar<\/a>, Everlaw\u2019s\u00a0founder, who demoed the product for a group of journalists over lunch, if Deep Dive can\u2019t find any documents to respond to the question, it will say so. (In the demo, based on the question one of us asked as to who the best legal tech journalist was, Deep Dive demurred and said there were no documents in its data base to answer the questions, thankfully.)<\/p>\n The demo certainly backed up the above claims from Everlaw\u2019s press release.<\/p>\n According to Chuck Kellner<\/a>, Everlaw Advisor, who also attended the demo, Everlaw envisioned three use cases:<\/p>\n 1. Undertaking a data dump before depositions to help either the taking or defending lawyer better prepare.<\/p>\n 2. Using the tool at the beginning of case to assess exposure etc. without a huge investment of time and cost and before discovery.<\/p>\n 3. Designing document review and coding projects. Use of the tool would eliminate the \u201cI don\u2019t know what to look for\u201d problem. The tool can give an overview of the documents to help design the review and coding.<\/p>\n The first two of these were particularly music to my ears. Kellner confirmed what I was thinking. It is designed not for those working on a case but for the case lead and strategist. And as I said before, these are the people that know the overall case the best and know the client the best. Giving them the ability to ask questions will inevitability lead to better results. All too often, eDiscovery vendors portray what their tools will do defensively and not offensively in the hands of an experienced lawyer.<\/p>\n And the ability to ask what documents might support the other side\u2019s allegation is golden to a front-end loading and strategy process. Simply plug in the an allegation\u00a0and then ask what supports or does not support that claim.<\/p>\n A Credible Demo<\/strong><\/p>\n But, here\u2019s another lesson from the Everlaw demonstration. In a conference where too many vendors are promising the sun, the moon, and the stars, Shankar was refreshingly honest about what the tool can and can\u2019t do. He recognized that the questions lawyers need answers to aren\u2019t necessarily easy for AI tools to answer. That Deep Dive might make mistakes, that it\u2019s an aid, not a panacea.<\/p>\n Shankar even did the demo live, not using a screen video like most use in vendor presentations. The technology didn\u2019t necessarily work perfectly during the demo (those who do this in real life know this is an issue for a variety of reasons that have nothing to do with the product). He let the audience ask questions of the tool. He admitted that while he thought he knew what the tool would do in the demo, it wasn\u2019t foolproof. \u201cIt can\u2019t do everything,\u201d he cautioned.<\/p>\n The approach was refreshing and enhanced both his and Everlaw\u2019s credibility in my mind.<\/p>\n A useful tool and a credible demo. Imagine that.<\/p>\n Stephen Embry is a lawyer, speaker, blogger, and writer. He publishes\u00a0TechLaw Crossroads<\/a>, a blog devoted to the examination of the tension between technology, the law, and the practice of law<\/strong><\/em>.<\/p>\n The post Front-End Loading Cases Just Got Easier: Everlaw\u2019s Deep Dive Tool<\/a> appeared first on Above the Law<\/a>.<\/p>\n One of the key things I learned from a number of mentors in the mass tort defense league was the importance of front-end loading cases. By that I mean getting a grasp early on of the exposure and the \u201coh shit\u201d documents and then immediately formulating the appropriate case strategy based on that grasp. Over and over again, the approach proved itself as the case progressed.<\/p>\n Another thing I learned along the way was the improved depositions and cross examination of witnesses where I, as the most knowledgeable and experienced lawyer on the case, could myself review and locate the most important documents, as opposed to asking an associate or paralegal to do that work and then report to me.<\/p>\n The problem with both, of course, was always the cost and time involved to do this important work. All too often clients would balk at paying for this work early on. Convincing them otherwise was a pain, to say the least.<\/p>\n The Deep Dive Tool<\/strong><\/p>\n Enter Everlaw\u2019s<\/a> new Deep Dive<\/a> tool, which promises to address both challenges. The tool is an enhancement of what was previously called Project Query, according to the Everlaw press release. Deep Dive was announced in open beta at the ILTA conference this week.<\/p>\n In essence, the tool allows the user to query a large data set of inputted documents using natural language. The tool allows users to simply ask questions related to specific issues, parties, or events and get answers. In a class action, you might ask the tool something like \u201cis there any support for the claims that there are common questions of fact among the various putative class members.\u201d<\/p>\n The answers are supported with a list of facts and referenceable documents so users can dive deeper into the breakdown of information available as part of the response. In other words, the tool cites the documents that it uses to answer the questions. You can then drill down into the documents and ask more specific questions based on a subset of the cited documents. The tool does not go outside the documents to answer any inquiry.<\/p>\n Importantly, according to AJ Shankar<\/a>, Everlaw\u2019s\u00a0founder, who demoed the product for a group of journalists over lunch, if Deep Dive can\u2019t find any documents to respond to the question, it will say so. (In the demo, based on the question one of us asked as to who the best legal tech journalist was, Deep Dive demurred and said there were no documents in its data base to answer the questions, thankfully.)<\/p>\n The demo certainly backed up the above claims from Everlaw\u2019s press release.<\/p>\n According to Chuck Kellner<\/a>, Everlaw Advisor, who also attended the demo, Everlaw envisioned three use cases:<\/p>\n 1. Undertaking a data dump before depositions to help either the taking or defending lawyer better prepare.<\/p>\n 2. Using the tool at the beginning of case to assess exposure etc. without a huge investment of time and cost and before discovery.<\/p>\n 3. Designing document review and coding projects. Use of the tool would eliminate the \u201cI don\u2019t know what to look for\u201d problem. The tool can give an overview of the documents to help design the review and coding.<\/p>\n The first two of these were particularly music to my ears. Kellner confirmed what I was thinking. It is designed not for those working on a case but for the case lead and strategist. And as I said before, these are the people that know the overall case the best and know the client the best. Giving them the ability to ask questions will inevitability lead to better results. All too often, eDiscovery vendors portray what their tools will do defensively and not offensively in the hands of an experienced lawyer.<\/p>\n And the ability to ask what documents might support the other side\u2019s allegation is golden to a front-end loading and strategy process. Simply plug in the an allegation\u00a0and then ask what supports or does not support that claim.<\/p>\n A Credible Demo<\/strong><\/p>\n But, here\u2019s another lesson from the Everlaw demonstration. In a conference where too many vendors are promising the sun, the moon, and the stars, Shankar was refreshingly honest about what the tool can and can\u2019t do. He recognized that the questions lawyers need answers to aren\u2019t necessarily easy for AI tools to answer. That Deep Dive might make mistakes, that it\u2019s an aid, not a panacea.<\/p>\n Shankar even did the demo live, not using a screen video like most use in vendor presentations. The technology didn\u2019t necessarily work perfectly during the demo (those who do this in real life know this is an issue for a variety of reasons that have nothing to do with the product). He let the audience ask questions of the tool. He admitted that while he thought he knew what the tool would do in the demo, it wasn\u2019t foolproof. \u201cIt can\u2019t do everything,\u201d he cautioned.<\/p>\n The approach was refreshing and enhanced both his and Everlaw\u2019s credibility in my mind.<\/p>\n A useful tool and a credible demo. Imagine that.<\/p>\n Stephen Embry is a lawyer, speaker, blogger, and writer. He publishes\u00a0TechLaw Crossroads<\/a>, a blog devoted to the examination of the tension between technology, the law, and the practice of law<\/strong><\/em>.<\/p>\n The post Front-End Loading Cases Just Got Easier: Everlaw\u2019s Deep Dive Tool<\/a> appeared first on Above the Law<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" One of the key things I learned from a number of mentors in the mass tort defense league was the importance of front-end loading cases. By that I mean getting a grasp early on of the exposure and the \u201coh shit\u201d documents and then immediately formulating the appropriate case strategy based on that grasp. Over […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[16],"tags":[],"class_list":["post-130394","post","type-post","status-publish","format-standard","hentry","category-above_the_law"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/posts\/130394","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/comments?post=130394"}],"version-history":[{"count":0,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/posts\/130394\/revisions"}],"wp:attachment":[{"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/media?parent=130394"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/categories?post=130394"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/tags?post=130394"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n
\n