Commentary

Andrew Conry Murray
 

IT & Legal: Can't We All Just Get Along?

A new survey shows there's a long way to go before IT and legal make a good e-discovery team.

A new survey shows there's a long way to go before IT and legal make a good e-discovery team.IT and legal teams should be like a Nascar pit crew when it comes to e-discovery: fast, efficient, and well-integrated. Otherwise an e-discovery effort can easily crash.

But a new survey of senior IT managers shows a majority of organizations lack a well-oiled IT/legal team. For instance, 67% of respondents say IT and legal aren't working more closely this year than last year. And only 21% say e-discovery is a high priority.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

That leads to problems when a junior attorney bursts into the data center with orders to drop everything and produce every e-mail for a dozen custodians from the years 2000 to 2003. In three weeks. He's not going to get a warm welcome.

Another area of concern is that only 29% of IT respondents say they understand the technical specifications of e-discovery products. But they aren't getting a lot of help from the general counsel's office on this front. Only 12% of IT thinks the legal team understands the technical specifications.

That makes it hard for IT, which is usually tasked with actually procuring discovery products, to make sure what they invest in will actually help.

This survey data mirrors an interview I did with an IT pro at a large energy company who's only job is to act as liaison with her legal department.

Did she have a close-knit relationship with the general counsel? In her words, it was more like the Grand Canyon.

Enterprise search software company Recommind surveyed 250 senior-level IT managers at organizations with an average size of 17,000 employees. The company also plans to survey the general counsels at large companies to get some perspective on their IT brethren. This could get ugly.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links