5. Presentation - Draft * Although represented as a linear workflow, moving from left to right, this process is often iterative. The feedback loops have been omitted from the diagram for graphic simplicity. Project Management Aim: Displaying ESI before audiences (at depositions, hearings, trials, etc.), especially in native & near-native forms, to elicit further information, validate existing facts or positions, or persuade an audience. Goal: Develop facts, leverage technology, facilitate communication and persuade.
6. Identification - Draft * Although represented as a linear workflow, moving from left to right, this process is often iterative. The feedback loops have been omitted from the diagram for graphic simplicity. Project Management Aim: To identify subject matter experts, resources involved, potential sources of data; to determine the depth and breadth of potential liability; to aggregate information sources for developing course of action. Goal: Evaluate, leverage and mitigate.
7. Preservation - Draft * Although represented as a linear workflow, moving from left to right, this process is often iterative. The feedback loops have been omitted from the diagram for graphic simplicity. Project Management Aim: When duty to preserve is triggered, promptly isolate and protect potentially relevant data in ways that are: legally defensible; reasonable; proportionate; efficient; auditable; broad but tailored; mitigate risks. Goal: Mitigate risks.
8. Collection - Draft * Although represented as a linear workflow, moving from left to right, this process is often iterative. The feedback loops have been omitted from the diagram for graphic simplicity. Project Management Aim: When data needs to be used, collect potentially relevant data in ways that are: legally Defensible; forensically sound; proportionate; efficient; auditable; targeted. Goal: Mitigate risks.
9. Processing - Draft * Although represented as a linear workflow, moving from left to right, this process is often iterative. The feedback loops have been omitted from the diagram for graphic simplicity. Project Management Aim: Perform actions on ESI to allow for metadata preservation, itemization, normalization of format, and data reduction via selection for review. Goal: Identify ESI items appropriate for review and production as per project requirements.
10. Review - Draft * Although represented as a linear workflow, moving from left to right, this process is often iterative. The feedback loops have been omitted from the diagram for graphic simplicity. Project Management Aim: To gain an understanding of document content while organizing them into logical sub-sets in an efficient and cost effective manner. Goal: Develop facts, reduce risk, reduce cost, leverage technology, facilitate collaboration and communication.
11. Analysis - Draft Project Management Aim: To develop, facilitate, test and validate processes for handling e-discovery efforts. Goal: Assess and understand ESI throughout the life of the case for the purpose of making educated decisions and developing a defensible, strategic plan.
12. Production - Draft * Although represented as a linear workflow, moving from left to right, this process is often iterative. The feedback loops have been omitted from the diagram for graphic simplicity. Project Management Aim: To prepare and produce ESI in an agreed upon and usable format. Goal: Efficient production in compliance with agreed production specifications and timelines, reduce cost, reduce risk, reduce errors.
Narrative: The information basics are distilled out and at the center – with the notable inclusion of “ dispose ” as the end state of information. And the “ information gates ” in the middle.
Narrative: The line of business has an interest in information proportional to its value – the degree to which it helps drive the profit or purpose of the enterprise itself. Once that value expires, they quickly lose interest in managing it, cleaning it up, or paying for it to be stored. One of the things that the IMRM does is distinguish value from regulatory obligation or IT efficiency.
Narrative: Their charter is typically to manage risk for the company. It underscores that it is the legal department ’ s responsibility to define what to put on hold and what and when to collect data for discovery; and RIM ’ s responsibility to ensure that regulatory obligations for information are met including what to retain archive for how long. Together they both have an enormous role in how and when companies can dispose of data. As with the business segment, it calls on legal and RIM to be specific about the duties for information – what they are and when those duties end.
Narration: IT stores and secures information under their management. Of course their focus is efficiency and they ’ re typically under huge pressure to increase efficiency and lower cost. What these reliefs of this diagram show is that without collaboration and unified governance, IT doesn ’ t know and can ’ t speak to what information has value or what duties apply to specific information. One of the things IMRM can help companies address is that for IT to manage data efficiently, it is essential to link specific duties and business value to the information assets.
![e-Discovery George Socha Socha Consulting LLC [email_address] April 14-15, 2011](https://image.slidesharecdn.com/georgesocha-110417233307-phpapp01/85/George-Socha-1-320.jpg)
