tag:blogger.com,1999:blog-28611335.post-1148429045723215642006-05-23T20:01:00.001-04:002006-09-26T20:15:28.393-04:00First of all, "I" want to say one thing. We've come a long way from BRS and the DOS versions of Summation. Back in the day, these document review applications "rocked," they were effective, they were all we had! Today, the plethora of document management tools of the market is enough to give any sane person a reason to take a purple pill. Its great to have choices, but we can't spend the rest of our days, perusing tools that are constantly releasing new versions with features to exploit what the marketing mavens see as the competitions shortcomings and trump what they consider to be the next big thing the other guy is coming out with.<br /><br />Did they forget something?<br /><br />Did they ask me what "I" need (where I=Litigation Support Manager + Legal Assistant + Associate + Partner + Client)? Forgive me, but perhaps"I" am being too presumptuous and perhaps my expectations are unrealistic. If so, then "I" need someone to help me readjust my expectations to something reasonable. But remember now, "I" am the client. "I" am the quintessential customer, and "I" have many different incarnations, a few of which have been identified in the ad hoc WHO AM"I" formula above.<br /><br />As the <strong>Litigation Support Manager</strong>, I need to have a tool that is:<br /><ul><li>Robust </li><li>Easy to maintain </li><li>Easy to troubleshoot </li><li>"Open," i.e., SQL back end and a front end with ample API support and have interconnectivity with other tools commonly used for data management. </li><li>Should I also mention, the company that meets the criteria above should also be around next fiscal quarter? </li></ul><br />As a <strong>Legal Assistant</strong>, I have extraordinary pressure. I have to prepare for depositions, create witness prep. kits, do document pulls, complex searches and groupings, hearings. I need a tool that has:<br /><ul><li>A flat learning curve; it's intuitive and easy to use. </li><li>The functional logic flows with my workflow; you need to understand what I do and the order in which I do it from a best practices perspective. </li><li>Is reliable; in other words, I should not find undocumented features sometimes known as bugs. </li></ul><p>As the <strong>client of the law firm</strong> that has chosen the tools that will host my documents for the matters in which I pay them handsome fees, I expect that:</p><ul><li>I should be a able to collaborate with my chosen counsel, whenever and from wherever I choose. </li><li>I should be able to up to date progress and billing get metrics on the litigation matters they are working on as well.</li></ul><p>Since for the most part, I am the General Counsel or some branch of the Legal Department that reports in to the GC's office, <strong>the Corproate Board of Directors is also peripherally interested</strong> in how we collaborate. </p><ul><li>How will you help me shine?</li><li>How will you keep me in the know?</li><li>Can you help me with the compliance aspect of the information in my litigation document collection?</li><li>How will you help me take the large sums of money that have been spent on the particular matter, embodied in the work product that is in the repository (your repository) and turn it into a institutional knowledge based capital asset? </li></ul><p>What I mean by the lofty statement is, how can you help me create post litigation (or representation) based value and utility in the documents and work product that might otherwise be destroyed pursuant to a protective order? </p><p>"I" know some of these questions can be construed as challenging, but if you think you've got the responses that make sense, that get the juices flowing in each of my alter egos, them please take up the challenge by pointedly responding to each of the concerns delineated above. </p><p>Yours truly, </p><p><br />The Universal "I"</p><div class="blogger-post-footer">The contents of this blog are for commercial fair use only. Any for profit use must be cleared with the author. </div>Richard E. Davis, JDhttp://www.blogger.com/profile/10343318932502593370noreply@blogger.com