Identification

The Importance of Early Data Assessment: eDiscovery Best Practices

Why do we have a picture of Santa Claus for an eDiscovery blog post about early data assessment?  Read on.

In the Fall 2016 eDiscovery Business Confidence Survey conducted last month, over a third of all respondents cited Increasing Volumes of Data as expected to be most impactful to the business of eDiscovery over the next six months.  With more and more data to manage, understanding what you have in that data as early as possible has become more important than ever as you attempt to plan the budget for your upcoming discovery efforts.

Knowing how much data you have in gigabytes (GB) or terabytes (TB) that may be subject to litigation isn’t enough to accurately estimate the number of files you have.  As we’ve discussed before, the number of files in each gigabyte can vary widely.

Why is that important?  The more files you have, the more files you potentially have to review.  With review costs estimated to be between 70-80 percent of all eDiscovery costs, a lot more files to review can drive up eDiscovery costs significantly.  Wouldn’t it be better to know early in the case how many files you have?

That’s where early data assessment comes in.  The ability to assess your data early enables you to better estimate your eDiscovery costs, so that you can decide whether to settle or litigate and also so that you can plan resources if you do decide to litigate.

In addition to determining the number of files that you have, it’s also beneficial to determine the expanded size of your collection after processing (so that you can estimate costs for storing or hosting that collection) to determine how many different types of files you have and how many files and data volume is comprised by each file type.  Also, whether any of the files are exception files, such as corrupt or password protected files.  Those files can take a lot of time to address, adding costs to the eDiscovery process.

Want more?  It’s also important to determine how many emails and attachments you have, how many domains those emails represent and also how many email conversations are encompassed with those emails.  And, the timelines for your email collection, so you can identify potential gaps in your collection.

Early data assessment can provide all of that information to you at the outset of litigation.

Here’s the best news: it doesn’t have to cost anything to perform that early data assessment.  CloudNine is offering free early data assessment reporting to provide your organization with valuable information to help shape its litigation strategy.  Consider it an early holiday present this season!  You’re welcome, and happy holidays!

I told you to read on, right?  :o)

So, what do you think?  Do you perform assessment of your data early in the litigation life cycle?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

Illustrated Observations from ILTACON 2016: eDiscovery Trends

We wrap up our week covering the International Legal Technology Association (ILTA) annual educational conference of 2016 (otherwise known as ILTACON 2016) by discussing some of the observations from this year’s show.  Here are a few observations that I have put together, based on my own experiences and discussions with fellow attendees at the show.

Venue

The show this year was held at the National Harbor Gaylord National Resort & Convention Center in the Washington/Baltimore area.  The venue is sizable, but there were several ILTA placards around the conference which made it easy to find the location for sessions and the exhibit hall quickly.  Session rooms were good sized, though, in a couple of the bigger “Maryland” conference rooms, there seemed to be an acoustics problem and it was hard to hear some of the speakers.  Some of that could be due to speakers not fully speaking into the microphones, but it seemed to be prevalent for all speakers, especially in one session that I attended on Wednesday afternoon.  Nonetheless, the venue was enjoyable with a couple of restaurants in the facility (and several more within walking distance) for breakout meetings over meals, if you chose a different location than the ILTA-sponsored meals.  And, as always, meals were included for conference attendees and there were many taking advantage of that option, as you can see here:

ILTA-6

Environment

As for the ILTACON environment, the show once again included some of the innovations and perks that make it stand out from the rest.  For example:

Laminating Business Cards: ILTACON once again had a station for laminating business cards (with a strap to attach to your bag to differentiate it from others) and it literally takes less than a minute for each card (so, of course, I had two made – one each for my CloudNine and eDiscovery Daily cards).  :o)

Catch Box: As they did last year, ILTACON had the unique “Catch Box” microphone to pass around to audience members for questions or comments.  Clever way to get the microphone passed around more quickly (and with a little bit of fun).

CatchBox

 

ILTACON App: Once again this year, ILTA provided an app that you could download to your iPhone or Android that provided all sorts of information, including maps of the exhibit hall and conference center, an activity feed, agenda for each day with details about the event (including date and time, location, speakers, etc.), details about the speakers and exhibitors and materials to download.  Probably the best show app of any of the shows.

TheFilament.com: Down the hall from the second floor session rooms, there was a big board with instructions to read from several thought provoking questions, put your answer on a post-it note and post it on the board.  The artists this time from TheFilament.com, a team of meeting consultants, then represented those answers in cartoon form.  In addition to the cartoon you see at the top of this post, here are a couple of others in answer to the statement “The thing about legal tech that drives me crazy is…”

ILTA-1ILTA-2

Of course, in a sign of the times (pun intended), the conference needed to set ground rules for any Pokemon GO aficionados in the group…

ILTA-5

Exhibit Hall

This year, there were more exhibitors than last year (195, according to the web site) and the exhibit hall was bigger, which made it seem less crowded.  Exhibitors seemed generally pleased with the traffic and the attendance and one noted that less available distractions than last year (when the show was in Las Vegas) made for more interest and traffic at their booth.

Regarding one participant’s experience, Shawn Gaines, Director of Marketing Communications at kCura, told me: “As always, the community at ILTACON is outstanding.  While there aren’t as many attendees as Legaltech New York, ILTACON’s educational focus makes for really in-depth discussions, particularly with folks we don’t always interact with.  For example, we hosted a CIO Summit and met with a great group of CIOs that we don’t always get the opportunity to garner feedback from and understand their greatest needs.  Booth traffic is always fine, but as a vendor, ILTACON is really all about what you decide to make of it.”

Sessions

As usual, there were numerous sessions (over 170, by my count) and several of them related to litigation support, eDiscovery and information governance (including the ones we covered over the last four days).  So, there was plenty of educational opportunities at the show.  I attended several good sessions, here are a couple that stood out for me:

Preparing an ROI for eDiscovery Services: A Litigation Technology Operations Workshop: The session was hands-on and interactive workshop, enabling attendees to create a simulated return on investment (ROI) analysis for eDiscovery services.  Great idea and great exercise.

Refining Your E-Discovery Reporting: This session walked through a case study covering various phases of the process (from receiving a document request to sampling custodians to discussing metrics for processing, review and production).  Terrific presentation and discussion about eDiscovery metrics.

Extracurricular

Of course, no ILTA experience would be complete without some enjoyable times outside of the conference.  My colleagues and I had a thoroughly fun dinner with Mary Mack and Kaylee Walstad of ACEDS on Monday and an enjoyable lunch discussion with David Horrigan of kCura on Tuesday.  Mary also led me to a wonderful Beer for Bloggers happy hour on Tuesday where I got to meet several interesting bloggers and other folks including Kevin O’Keefe of Lexblog, Gretchen DeSutter of Thomson Reuters and Bob Ambrogi of the Law Sites blog (and others).  Thanks to Lexblog and Thomson Reuters for sponsoring the happy hour – it was great fun to talk blogging, other legal topics and other topics in general!

So, what do you think?  Did you attend ILTACON this year?  What did you think of the conference?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

At Litigation Time, the Cost of Data Storage May Not Be As Low As You Think: eDiscovery Best Practices

One of my favorite all-time graphics that we’ve posted on the blog (from one of our very first posts) is this ad from the early 1980s for a 10 MB disk drive – for $3,398!  That’s MB (megabytes), not GB (gigabytes) or TB (terabytes).  These days, the cost per GB for data storage is pennies on the dollar, which is a big reason why the total amount of data being captured and stored by industry doubles every 1.2 years.  But, at litigation time, all that data can cost you – big.

When I checked on prices for external hard drives back in 2010 (not network drives, which are still more expensive), prices for a 2 TB external drive at Best Buy were as low as $140 (roughly 7 cents per GB).  Now, they’re as low as $81.99 (roughly 4.1 cents per GB).  And, these days, you can go bigger – a 5 TB drive for as low as $129.99 (roughly 2.6 cents per GB).  I promise that I don’t have a side job at Best Buy and am not trying to sell you hard drives (even from the back of a van).

No wonder organizations are storing more and more data and managing Big Data in organizations has become such a challenge!

Because organizations are storing so much data (and in more diverse places than ever before), information governance within those organizations has become vitally important in keeping that data as manageable as possible.  And, when litigation or regulatory requests hit, the ability to quickly search and cull potentially responsive data is more important than ever.

Back in 2010, I illustrated how each additional GB that has to be reviewed can cost as much as $16,650 (even with fairly inexpensive contract reviewers).  And, that doesn’t even take into consideration the costs to identify, preserve, collect, and produce each additional GB.  Of course, that was before Da Silva Moore and several other cases that ushered in the era of technology assisted review (even though more cases are still not using it than are using it).  Regardless, that statistic illustrates how the cost of data storage may not be as low as you think at litigation time – each GB could cost hundreds or even thousands to manage (even in the era of eDiscovery automation and falling prices for eDiscovery software and services).

Equating the early 1980’s ad above to GB, that equates to about $330,000 per GB!  But, if you go all the way back to 1950, the cost of a 5 MB drive from IBM was $50,000, which equates to about $10 million per GB!  Check out this interactive chart of hard drive prices from 1950-2010, courtesy of That Data Dude (yes, that really is the name of the site) where you can click on different years and see how the price per GB has dropped over the years.  It’s way cool!

So, what do you think?  Do you track GB metrics for your cases?  Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

George Socha of Socha Consulting LLC: eDiscovery Trends

This is the second of the 2016 LegalTech New York (LTNY) Thought Leader Interview series.  eDiscovery Daily interviewed several thought leaders at LTNY this year to get their observations regarding trends at the show and generally within the eDiscovery industry.  Unlike previous years, some of the questions posed to each thought leader were tailored to their position in the industry, so we have dispensed with the standard questions we normally ask all thought leaders.

Today’s thought leader is George Socha.  A litigator for 16 years, George is President of Socha Consulting LLC, offering services as an electronic discovery expert witness, special master and advisor to corporations, law firms and their clients, and legal vertical market software and service providers in the areas of electronic discovery and automated litigation support. George has also been co-author of the leading survey on the electronic discovery market, The Socha-Gelbmann Electronic Discovery Survey; in 2011, he and Tom Gelbmann converted the Survey into Apersee, an online system for selecting eDiscovery providers and their offerings.  In 2005, he and Tom Gelbmann launched the Electronic Discovery Reference Model project to establish standards within the eDiscovery industry – today, the EDRM model has become a standard in the industry for the eDiscovery life cycle and there are nine active projects with over 300 members from 81 participating organizations.  George has a J.D. for Cornell Law School and a B.A. from the University of Wisconsin – Madison.

What are your general observations about LTNY this year and about emerging eDiscovery trends overall?

{Interviewed the first morning of LTNY, so the focus of the question to George was more about his expectations for the show and also about general industry trends}.

This is the largest legal technology trade show of the year so it’s going to be a “who’s who” of people in the hallways.  It will be an opportunity for service and software providers to roll out their new “fill in the blank”.  It will be great to catch up with folks that I only get to see once a year as well as folks that I get to see a lot more than that.  And, yet again, I don’t expect any dramatic revelations on the exhibit floor or in any of the sessions.

We continue to hear two recurring themes:  the market is consolidating and eDiscovery has become a commodity. I still don’t see either of these actually happening.  Consolidation would be if some providers were acquiring others and no new providers were coming along to fill in the gaps, or if a small number of providers was taking over a huge share of the market.  Instead, as quickly as one provider acquires another, two, three or more new providers pop up and often with new ideas they hope will gain traction.  In terms of dominating the market, there has been some consolidation on the software side but as to services provider the market continues to look more like law firms than like accounting firms.

In terms of commoditization, I think we still have a market where people want to pay “K-mart, off the rack” prices for “Bespoke” suits.  That reflects continued intense downward pressure on prices.  It does not suggest, however, that the e-discovery market has begun to approximate, for example, the markets for corn, oil or generic goods.  E-discovery services and software are not yet fungible – with little meaningful difference between them other than price.  I have heard no discussion of “e-discovery futures.”  And providers and consumers alike still seem to think that brand, levels of project management, and variations in depth and breadth of offerings matter considerably.

Given that analytics happens at various places throughout the eDiscovery life cycle, is it time to consider tweaking the EDRM model to reflect a broader scope of analysis?

The question always is, “what should the tweak look like?”  The questions I ask in return are “What’s there that should not be there?”, “What should be there that is not?” and “What should be re-arranged?”  One common category of suggested tweaks are the ones meant to change the EDRM model to look more like one particular person’s or organization’s workflow.  This keeps coming up even though the model was never meant to be a workflow – it is a conceptual framework to help break one unitary item into a set of more discrete components that you can examine in comparison to each other and also in isolation.

A second set of tweaks focuses on adding more boxes to the diagram.  Why, we get asked, don’t we have a box called Early Case Assessment, and another called Legal Hold, and another called Predictive Coding, and so on. With activities like analytics, you can take the entire EDRM diagram and drop it inside any one of those boxes or in that circle.  Those concepts already are present in the current diagram.  If, for example, you took the entire EDRM diagram and dropped it inside the Identification box, you could call that Early Case Assessment or Early Data Assessment.  There was discussion early on about whether there should be a box for “Search”, but Search is really an Analysis function – there’s a home for it there.

A third set of suggested tweaks centers on eliminating elements from the diagram.  Some have proposed that we combine the processing and review boxes into a single box – but the rationale they offer is that because they offer both those capabilities there no longer is a need to show separate boxes for the separate functions.

What are you working on that you’d like our readers to know about?

First, we would like to invite current and prospective members to join us on April 18 for our Spring meeting which will be at the ACEDS conference this year.  The conference is from April 18 through April 20, with the educational portion of the conference slated for the 19th and 20th.

For several years at the conference, ACEDS has given out awards honoring eDiscovery professionals.  To congratulate this year’s winners we will be giving them one-year individual EDRM memberships.

On the project side, one of the undertakings we are working on is “SEAT-1,” a follow up to our eMSAT-1 (eDiscovery Maturity Self-Assessment Test).  SEAT-1 will be a self-assessment test specifically for litigation groups and law firms.  The test is intended to enable them to better assess where they are at, how they are doing and where they want to be.  We are also working on different ways to deliver our budget calculators.  It’s too early to provide details on that, but we’re hoping to be able to provide more information soon.

Finally, in the past year we have begun to develop and deliver member-only resources. We published a data set for members only and we put a new section of EDRM site with information about the changes to the Federal rules, including a comprehensive collection of information about the changes to the rules.  This year, we will be working on additional resources to be available to just our members.

Thanks, George, for participating in the interview!

And to the readers, as always, please share any comments you might have or if you’d like to know more about a particular topic!

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

For a Successful Outcome to Your Discovery Project, Work Backwards: eDiscovery Best Practices

Based on a recent experience with a client, it seemed appropriate to revisit this topic. Plus, it’s always fun to play with the EDRM model. Notice anything different? 🙂

While the Electronic Discovery Reference Model from EDRM has become the standard model for the workflow of the process for handling electronically stored information (ESI) in discovery, it might be helpful to think about the EDRM model and work backwards, whether you’re the producing party or the receiving party.

Why work backwards?

You can’t have a successful outcome without envisioning the successful outcome that you want to achieve. The end of the discovery process includes the production and presentation stages, so it’s important to determine what you want to get out of those stages. Let’s look at them.

Presentation

Whether you’re a receiving party or a producing party, it’s important to think about what types of evidence you need to support your case when presenting at depositions and at trial – this is the type of information that needs to be included in your production requests at the beginning of the case as well as the type of information that you’ll need to preserve as a producing party.

Production

The format of the ESI produced is important to both sides in the case. For the receiving party, it’s important to get as much useful information included in the production as possible. This includes metadata and searchable text for the produced documents, typically with an index or load file to facilitate loading into a review application. The most useful form of production is native format files with all metadata preserved as used in the normal course of business.

For the producing party, it’s important to be efficient and minimize costs, so it’s important to agree to a production format that minimizes production costs. Converting files to an image based format (such as TIFF) adds costs, so producing in native format can be cost effective for the producing party as well. It’s also important to determine how to handle issues such as privilege logs and redaction of privileged or confidential information.

Addressing production format issues up front will maximize cost savings and enable each party to get what they want out of the production of ESI. If you don’t, you could be arguing in court like our case participants from yesterday’s post.

Processing-Review-Analysis

It also pays to make decisions early in the process that affect processing, review and analysis. How should exception files be handled? What do you do about files that are infected with malware? These are examples of issues that need to be decided up front to determine how processing will be handled.

As for review, the review tool being used may impact how quick and easy it is to get started, to load data and to use the tool, among other considerations. If it’s Friday at 5 and you have to review data over the weekend, is it easy to get started? As for analysis, surely you test search terms to determine their effectiveness before you agree on those terms with opposing counsel, right?

Preservation-Collection-Identification

Long before you have to conduct preservation and collection for a case, you need to establish procedures for implementing and monitoring litigation holds, as well as prepare a data map to identify where corporate information is stored for identification, preservation and collection purposes.

And, before a case even begins, you need an effective Information Governance program to minimize the amount of data that you might have to consider for responsiveness in the first place.

As you can see, at the beginning of a case (and even before), it’s important to think backwards within the EDRM model to ensure a successful discovery process. Decisions made at the beginning of the case affect the success of those latter stages, so working backwards can help ensure a successful outcome!

So, what do you think? What do you do at the beginning of a case to ensure success at the end?   Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine. eDiscovery Daily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Daily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.

The First 7 to 10 Days May Make or Break Your Case: eDiscovery Best Practices

Having worked with a client recently that was looking for some guidance at the outset of their case, it seemed appropriate to revisit this topic here.

When a case is filed, several activities must be completed within a short period of time (often as soon as the first seven to ten days after filing) to enable you to assess the scope of the case, where the key electronically stored information (ESI) is located and whether to proceed with the case or attempt to settle with opposing counsel. Here are several of the key early activities that can assist in deciding whether to litigate or settle the case.

Activities:

  • Create List of Key Employees Most Likely to have Documents Relevant to the Litigation: To estimate the scope of the case, it’s important to begin to prepare the list of key employees that may have potentially responsive data. Information such as name, title, eMail address, phone number, office location and where information for each is stored on the network is important to be able to proceed quickly when issuing hold notices and collecting their data. Some of these employees may no longer be with your organization, so you may have to determine whether their data is still available and where.
  • Issue Litigation Hold Notice and Track Results: The duty to preserve begins when you anticipate litigation; however, if litigation could not be anticipated prior to the filing of the case, it is certainly clear once the case if filed that the duty to preserve has begun. Hold notices must be issued ASAP to all parties that may have potentially responsive data. Once the hold is issued, you need to track and follow up to ensure compliance. Here are a couple of posts from 2012 regarding issuing hold notices and tracking responses.
  • Interview Key Employees: As quickly as possible, interview key employees to identify potential locations of responsive data in their possession as well as other individuals they can identify that may also have responsive data so that those individuals can receive the hold notice and be interviewed.
  • Interview Key Department Representatives: Certain departments, such as IT, Records or Human Resources, may have specific data responsive to the case. They may also have certain processes in place for regular destruction of “expired” data, so it’s important to interview them to identify potentially responsive sources of data and stop routine destruction of data subject to litigation hold.
  • Inventory Sources and Volume of Potentially Relevant Documents: Potentially responsive data can be located in a variety of sources, including: shared servers, eMail servers, employee workstations, employee home computers, employee mobile devices, portable storage media (including CDs, DVDs and portable hard drives), active paper files, archived paper files and third-party sources (consultants and contractors, including cloud storage providers). Hopefully, the organization already has created a data map before litigation to identify the location of sources of information to facilitate that process. It’s important to get a high level sense of the total population to begin to estimate the effort required for discovery.
  • Plan Data Collection Methodology: Determining how each source of data is to be collected also affects the cost of the litigation. Are you using internal resources, outside counsel or a litigation support vendor? Will the data be collected via an automated collection system or manually? Will employees “self-collect” any of their own data? If so, important data may be missed. Answers to these questions will impact the scope and cost of not only the collection effort, but the entire discovery effort.

These activities can result in creating a data map of potentially responsive information and a “probable cost of discovery” spreadsheet (based on initial estimated scope compared to past cases at the same stage) that will help in determining whether to proceed to litigate the case or attempt to settle with the other side.

So, what do you think? How quickly do you decide whether to litigate or settle? Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the author, and do not necessarily represent the views held by CloudNine. eDiscoveryDaily is made available by CloudNine solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscoveryDaily should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.