<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-6791672639619957449</id><updated>2010-08-27T13:15:12.440-07:00</updated><title type='text'>Information Nation</title><subtitle type='html'></subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default?orderby=updated'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><link rel='next' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default?start-index=26&amp;max-results=25&amp;orderby=updated'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>67</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-3739883770318327710</id><published>2010-08-27T13:10:00.000-07:00</published><updated>2010-08-27T13:15:12.450-07:00</updated><title type='text'>Records are Proof</title><content type='html'>Close your eyes and silently read the following chilling words from the August 26, Wall Street Journal article—“On April 20 at 10:43 a.m., a young BP PLC engineer sent a 173-word email to colleagues abroad the Deepwater Horizon drilling rig. The email spelled out a recent change to a key safety test that sparked confusion and debate abroad the rig. Less than 12 hours later, the rig was engulfed in flames so hot they melted steel”.    &lt;br /&gt;&lt;br /&gt;As the fateful day proceeded, it was clear there was confusion about whether or not the well was stable.  “over the next two hours, there were signs the well was slipping out of control. For one, more fluid was flowing out of the well than was being pumped in, according to electronic data reviewed by investigators after the explosion.”&lt;br /&gt;&lt;br /&gt;As the lines are now being drawn to determine who is responsible for the death of 11 people and the largest oil spill in our history, what is clear is that records will likely be central in determining who is at fault.    For example, Brian Morel who “wrote an email about a week before the explosion, saying that it was a ‘nightmare well which has everyone all over the place’ has refused to testify before a federal governmental panel citing his 5th amendment against self incrimination.”&lt;br /&gt;&lt;br /&gt;For those businesses who refuse to recognize the importance of a records program, ask yourself if your business would continue to exist after sustaining a multiple billion dollar penalty. &lt;br /&gt;&lt;br /&gt;Viva La Records Management&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-3739883770318327710?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/3739883770318327710/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=3739883770318327710' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/3739883770318327710'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/3739883770318327710'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/08/records-are-proof.html' title='Records are Proof'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-5234359186995234112</id><published>2010-08-02T12:22:00.000-07:00</published><updated>2010-08-02T12:28:48.131-07:00</updated><title type='text'>Leaks happen.  How do we stop them?</title><content type='html'>This week has been a bad one for the administration when it comes to information leaks.  As they try to figure out who the data colander is and why he/she has exposed 90,000 classified documents about the Afghanistan war which may explain why it’s going so poorly, one needs to ask what can be done to stop such leaks.  &lt;br /&gt;&lt;br /&gt;Well the government had policy (in this case a really serious one) and the soldier with intelligence access didn’t follow it.  Find him and fire him. Not strong enough. Find him and court martial him — same thing. We need it stronger so others don’t follow suit. OK, if we were in Iran what would they do — behead him?  We are free not a Islamic totalitarian regime. Ok, what if we were in Russia - Gulag summer camp and Siberian Labor camp winter get away? Now that is better. But the American people won’t agree and maybe it's “Cruel and unusual punishment." Ok what if we were in France. They would make the leaker the president.  Ok wrong location. &lt;br /&gt;Ok, lets be America. But let’s find better ways to make our point to employees and make it stick. Lets realize that information flows and sometime out of the receptacle and we will need to deal with it.  &lt;br /&gt;&lt;br /&gt;Thoughts?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-5234359186995234112?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/5234359186995234112/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=5234359186995234112' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/5234359186995234112'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/5234359186995234112'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/08/leaks-happen-how-do-we-stop-them.html' title='Leaks happen.  How do we stop them?'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-1189233591140390100</id><published>2010-07-30T07:45:00.000-07:00</published><updated>2010-07-30T07:58:22.369-07:00</updated><title type='text'>The Hard Drive in the Sky</title><content type='html'>If at first you don’t succeed, try, try again. And so it was that we tried “outsourcing” and that fell down flat on its e-face. Then someone called it using an “Application Service Providers” or ASP but that sounded like we would get stung and they failed to understand the importance of giving our data over to a newish under-financed company who maybe didn’t care about privacy, information security, etc.  But then, we went to THE CLOUD. There I met a beautiful fairy who showed me the way of the Cloud Computing—"Isn’t it wonderful" she purred, “the hard drive in the sky.” And I saw it and it was wonderful indeed. Blah, Blah, Blah. &lt;br /&gt;&lt;br /&gt;But businesses are now getting serious about Cloud Computing and I don’t really have the heart burn I may have had before. And that is because real businesses with lots to lose are doing it .  That doesn’t mean you don’t need help navigating this new business relationship as it is different. But rather, it is serious business now done by companies with lots to lose if they screw up. The July 26 WSJ article said it all “Microsoft and Google Vie To Sell U.S. Cloud Mail." &lt;br /&gt;&lt;br /&gt;Oh, so you weren’t really a fairy at all? “No, I am a Stanford graduate in Computer Science with funny slippers and comfy pants.”   I got it.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-1189233591140390100?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/1189233591140390100/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=1189233591140390100' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/1189233591140390100'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/1189233591140390100'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/07/hard-drive-in-sky.html' title='The Hard Drive in the Sky'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-1173185137393786928</id><published>2010-07-29T10:35:00.000-07:00</published><updated>2010-07-29T10:49:43.997-07:00</updated><title type='text'>Records live on.</title><content type='html'>A company lawyer recently said to me, “I dream of a day when we have no records.”  I thought about it and responded.  I wanted to say --“You can fly if you believe Wendy.”  But I held back. &lt;br /&gt;&lt;br /&gt;I don’t know anything about doping or performance enhancing drugs. I know certain athletes have used them and it doesn’t seem fair if one uses them and another doesn’t. But this is a blog about information management not sports or even fairness in sports. Ok. Yesterday, I was reading an article about Lance Armstrong and the continuing investigation into performance enhancing drugs in the Tour de France. I think Lance is amazing—he dated a rock star—I haven’t. He won the most well-known and one of most demanding and grueling bike races in the world. I ride a bike and am lucky to beat my kids to the end of the block. Anyway, what I would say is that people will testify about the issue. They are either credible or not. Records can and will be used to defend or advance the argument against Lance. If I were Lance a few years back, seeing that performance enhancing drugs is becoming an issue going forward, I might regularly get myself tested and retain the results for if and when I need them to prove that I did nothing wrong.  I wonder what his doctor would say. Remember he had cancer and presumably is tested regularly (maybe not for drugs) but maybe his doctors records would show us truth.     &lt;br /&gt;&lt;br /&gt;In the end, your ability to defend yourself is either having good human testifiers or records. For me I would rather have good documented evidentiary support as I know other bikers may feel “sour grapes” and lie. I know people have selective memory. Others of us just forget. In the end, records live on.                    &lt;br /&gt;&lt;br /&gt;Vive La Records.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-1173185137393786928?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/1173185137393786928/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=1173185137393786928' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/1173185137393786928'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/1173185137393786928'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/07/records-live-on.html' title='Records live on.'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-211440480400497681</id><published>2010-07-26T07:58:00.000-07:00</published><updated>2010-07-26T07:59:56.741-07:00</updated><title type='text'>Much Thanks</title><content type='html'>I just completed an amazing trip to China.  I was hosted by Renmin University Professor Xiaomi An and had occasion to talk and interact with her students. I spent a lot of time with her graduate students Weakow Wang and Ye Shen.  First, when it comes to Information Management they are ahead of the pack.  Second, when it comes to navigating China’s bright future, they will play an important role. Finally, when it comes to the deep goodness that makes our world smaller, more connected and joyous, they are some of the reasons why. &lt;br /&gt;&lt;br /&gt;China has come so far so fast. China will go even farther with people like Xiaomi, Weakow and Ye Shen.  Thanks for opening your world to me and teaching me so much.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-211440480400497681?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/211440480400497681/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=211440480400497681' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/211440480400497681'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/211440480400497681'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/07/much-thanks.html' title='Much Thanks'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-3804698496901845989</id><published>2010-07-13T12:39:00.000-07:00</published><updated>2010-07-13T12:47:51.428-07:00</updated><title type='text'>Time to work together</title><content type='html'>In the old days of litigation,  a lawyer representing a company with lots of information might take a huge collection of documents and produce them knowing that the other side would have a hard time finding the relevant stuff from the crud. In other words, the strategy would be “hide the relevant needle in a big hay stack” .  With the change to the Federal Rules of Civil Procedure and the need to “meet and confer”, that has changed. Can’t hide the ball as a plan; need to work together to disclose what you have (we have built RulesMapper to help), need to tell the other side what is “not accessible” and generally work together to focus the discovery process. If there was confusion about working together with your adversary, read Mancia v. Mayflower Textile Services Co. [2008 WL 4595275 (D. Md. Oct. 15, 2008)]. In the case Judge Grimm makes clear that Fed. R. Civ. P. 26 now requires lawyers to cooperate in e-discovery and if they fail it might be considered a violation of the duty of "reasonable inquiry".  Money, time, collegiality and law all require working together. What’s stopping you?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-3804698496901845989?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/3804698496901845989/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=3804698496901845989' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/3804698496901845989'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/3804698496901845989'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/07/time-to-work-together.html' title='Time to work together'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-730198931137191964</id><published>2010-07-12T10:13:00.000-07:00</published><updated>2010-07-12T10:15:23.193-07:00</updated><title type='text'>Tell us about your RulesMapper</title><content type='html'>A client wants to get a better handle on the information assets they have.  In the old days, RM consultants used to get their troops out to inventory the enterprise. Months later and buckets of dough later, there was a spread sheet of stuff that purports to be the records.  We have changed all that as we wanted our clients to spend their money on making retention work not just knowing what they had.  Along the way we developed RULESMAPPER-an information governance dashboard to do the whole records inventory process for way less money and way less time. As it turned out, RULESMAPPER is way better than we thought. Clients tell us all the time how they use RulesMapper for “mapping of sources lite”,  private information management, etc.&lt;br /&gt;&lt;br /&gt;Jeanne Caldwell (the brains behind RulesMapper) and I want hear from you about how you are using RuelsMapper and how we can make it better. &lt;br /&gt;&lt;br /&gt;Thanks&lt;br /&gt;&lt;br /&gt;Randy Kahn&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-730198931137191964?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/730198931137191964/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=730198931137191964' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/730198931137191964'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/730198931137191964'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/07/tell-us-about-your-rulesmapper.html' title='Tell us about your RulesMapper'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-7089048778060543734</id><published>2010-07-07T09:47:00.000-07:00</published><updated>2010-07-07T09:59:41.942-07:00</updated><title type='text'>The new Information Parking Lot</title><content type='html'>When people vote with their feet, it is worth watching which the way they go. When employees flock to Sharepoint, it is worth figuring out why? But I already know why they flock to Microsoft’s new Information Parking Lot. Employees like it. Employees find value in it. They use it and it makes business “faster, better, cheaper”. So don’t be so quick to say no to any useful Information Parking Lot without knowing more.  There are information management, records management and compliance purists that can find fault. Get over it. Look closely enough at anything and you will find fault.  At least I know where my information assets are parked.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-7089048778060543734?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/7089048778060543734/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=7089048778060543734' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/7089048778060543734'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/7089048778060543734'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/07/new-information-parking-lot.html' title='The new Information Parking Lot'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-8301015206109766987</id><published>2010-07-06T07:41:00.000-07:00</published><updated>2010-07-06T08:09:48.327-07:00</updated><title type='text'>Call to Action</title><content type='html'>How do I know if records retention is working for my organization today?  If employees are not applying the rules and getting rid of content — it is not working. If share drive environments grow unfettered then perhaps retention is not working. If IT systems are purged without regard to what’s in the computers then it's broken. But I already know it's broken. It is not working for most companies because the business world changed but the rules of records retention didn’t keep up with change. I am advocating for change.  &lt;br /&gt;&lt;br /&gt;In an IT-centric information governance world, you need to get real, real fast.  If you think a set of retention rules that are event-based (don’t start to run until the happening of a future event) can work today with technology, I have another belief — it's too hard to build work flows for every future business event just to get rid of content. What that tells me is we should seek to have as few event based retention rules as possible. If employees aren’t doing retention as they are too busy already, then find another way. &lt;br /&gt;&lt;br /&gt;Bottom line, I want to hear from you if you will work with me to change the industry. Are you in?&lt;br /&gt;&lt;br /&gt;Randy Kahn&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-8301015206109766987?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/8301015206109766987/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=8301015206109766987' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/8301015206109766987'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/8301015206109766987'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/07/call-to-action.html' title='Call to Action'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-2027593801328628715</id><published>2010-06-28T07:13:00.000-07:00</published><updated>2010-06-28T07:14:23.010-07:00</updated><title type='text'>Finally a ruling on City of Ontario, Ca. v. Quon</title><content type='html'>At long last the Supreme Court has ruled on City of Ontario, Ca. v. Quon.  I say at long last because I have heard so many things about the case that it’s nice to hear the real facts and clear up any confusion about the law. This is the case involving a police SWAT guy who was given a paging device by the police department and then had his messages reviewed after he exceeded allotted departmental usage. Quon, the SWAT guy, cared because he had used the text capability provided for “BUSINESS PURPOSES” for mostly personal messages and had sent some sexually explicit and salacious texts as well. Anyway, the Supreme Court handled the case rather well. While not really addressing whether or not QUON had an expectation of privacy, they concluded that the search of the stored messages was not unreasonable, blah, blah, blah.  &lt;br /&gt;&lt;br /&gt;Well, the case stands for the same beliefs Kahn Consulting had been guided with in all our policy work over the years for clients. Make sure you have policies and that they clearly communicate the “rules of the road”.  Make clear employees do not have an expectation to privacy and that the rules apply to all technologies of telecommunications systems provided by the employer. &lt;br /&gt;&lt;br /&gt;There was special issue in the case that needs special attention. The texts were stored on the provider’s computers not the Police department’s servers. This issue needs special attention. Given the complexities and law on this issue, I am not going to give simple rules here that may confuse you. Suffice to say, as you contemplate storing content on “THE CLOUD” think about how accessing the business content when it is not on your server may have legal implications. If you need help, give us a call.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-2027593801328628715?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/2027593801328628715/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=2027593801328628715' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/2027593801328628715'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/2027593801328628715'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/06/finally-ruling-on-city-of-ontario-ca-v.html' title='Finally a ruling on City of Ontario, Ca. v. Quon'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-9006750412239717855</id><published>2010-06-25T11:31:00.000-07:00</published><updated>2010-06-25T11:35:28.256-07:00</updated><title type='text'>Arbitrariness</title><content type='html'>Arbitrariness, I am not sure if it’s a word.  But, it is a thing worth exploring.  When folks do something for poorly thought out reasons, or no reasons at all, that is arbitrariness.  Like, for example, making a record by filming the CIA interrogating terrorists. Why was it done and why are we continuing to do it--So that we can demonstrate to the world that we are not too tough on terrorists. But I digress.&lt;br /&gt;&lt;br /&gt;A guy builds a spreadsheet for the Mine Safety and Health Administration but configures it so we can only see a mine that has safety problems and not the parent company which may own many mines, all with safety problems. It is arbitrariness that allows the bad design to limit the safety agencies ability to track trends by offending companies.  Arbitrariness!&lt;br /&gt;&lt;br /&gt;Or When the same Mine Safety agency only allows a certain number of offending mining companies to be “assigned tougher enforcement” for their failings—that too is arbitrariness.  In the June 24 Wall Street journal, the article states “The Labor Department’s Inspector General found that federal mine safety regulators may have improperly limited enforcement of mines with serious safety violations… District managers could select no more than one mine a field office and a maximum of three mines a district office.”   I sure hope we spread out the “bad boys” of mining so that it comports with the Mine Safety “one bad boy per region” rule. Arbitrariness.&lt;br /&gt;&lt;br /&gt;When a CIO keeps 10 years of disaster recovery back-up tapes and asks why they keep getting their clock cleaned in discovery—that is arbitrariness.&lt;br /&gt;When a records manager pushes out the updated retention schedule with 600 rules instead of the 1200 they had before “simplification” that is arbitrariness.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-9006750412239717855?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/9006750412239717855/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=9006750412239717855' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/9006750412239717855'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/9006750412239717855'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/06/arbitrariness.html' title='Arbitrariness'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-6668399387276032029</id><published>2010-06-14T10:39:00.000-07:00</published><updated>2010-06-15T07:13:00.396-07:00</updated><title type='text'>Does a request for information matter?</title><content type='html'>Many have concluded that the risk and exposure of litigation cause companies to make business decision about legal claims. So if faced with a $500,000 expense to do discovery of electronic stored information(ESI), some would rather settle the case for $100,000 even if it has no merit. &lt;br /&gt;&lt;br /&gt;But does the mere request for information from a government regulator impact the company? Well of course it can. Take for example the request for records by a federal agency of a well known public company in the news recently.  The day the information request became known the stock went down 5% which is millions and millions of dollars.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-6668399387276032029?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/6668399387276032029/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=6668399387276032029' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/6668399387276032029'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/6668399387276032029'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/06/does-request-for-information-matter.html' title='Does a request for information matter?'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-2121688123619183521</id><published>2010-06-09T10:40:00.000-07:00</published><updated>2010-06-09T10:46:49.764-07:00</updated><title type='text'>Where's Waldo?</title><content type='html'>Randy’s Theory of Information Mismanagement-If at first you fail to do anything or do something albeit poorly, you will most certainly revisit your failings at the first smell of litigation or regulatory investigation. &lt;br /&gt;&lt;br /&gt;Let apply this theory-&lt;br /&gt;&lt;br /&gt;How about we start with the June 8 Wall Street Journal article entitled “Goldman Accused of Stalling By Panel”. It appears that the Financial Crisis Inquiry Commission sent Goldman a subpoena. It also seems that maybe Goldman didn’t respond with needed documents in a timely fashion. So in a rush, Goldman chucked huge chunks of data over the fence to the agency. How much you ask? Well 5 terabytes. That is the equivalent of hundreds of millions of pages. Guess what the response was “we should not be forced to play ‘Where’s Waldo on behalf of the American people.' Ouch. &lt;br /&gt;&lt;br /&gt;If electronic information is mismanaged upfront, finding it when you need to is a major headache—SEE GOLDMAN.&lt;br /&gt;&lt;br /&gt;Spending a little money to get your house in order proactively may not take all the hurt out of finding Waldo, but it sure can help.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-2121688123619183521?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/2121688123619183521/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=2121688123619183521' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/2121688123619183521'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/2121688123619183521'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/06/wheres-waldo.html' title='Where&apos;s Waldo?'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-6532759650478903704</id><published>2010-05-28T10:05:00.000-07:00</published><updated>2010-05-28T10:13:08.187-07:00</updated><title type='text'>Proactive v. Reactive</title><content type='html'>We did a bunch of records and information management (RIM) consulting work for a big oil company a few years ago. The company was motivated to build a world class RIM program because they believed that could be significantly more productive “per well drilled” if they better managed their business information.  In other words, they liked eating from the “carrot” jar when being motivated proactively to get serious about harnessing information.&lt;br /&gt;&lt;br /&gt;There is another oil company right now battling in the gulf, battling regulators, battling wall street, battling bad PR, battling angry fisherman, battling angry citizens, battling a tourist industry, battling environmentalists, etc.  I couldn’t help but think how records will play in resolving this problem which will go on for years — clean-up, new regulations, and lawsuits. &lt;br /&gt;&lt;br /&gt;I also want to say that in the cloud of news media, which tends to focus on the gusher,from myself and the whole Kahn Consulting team, we are deeply sorry for the loss of life the tragedy has caused. Our hearts go out to you.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-6532759650478903704?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/6532759650478903704/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=6532759650478903704' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/6532759650478903704'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/6532759650478903704'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/05/proactive-v-reactive.html' title='Proactive v. Reactive'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-4190592259256203280</id><published>2010-05-27T11:42:00.000-07:00</published><updated>2010-05-27T11:50:06.147-07:00</updated><title type='text'>Facebook is fixing its problem</title><content type='html'>The intent of social networking is to share. The business model of Facebook was to make an environment that promotes sharing. Well they now are being asked to tweak that model. For business sake, Facebook is responding.  Here is the story in a nutshell. Facebook is under attack by privacy advocates. I get it, they feel like too much personal info is too available and controls aren’t good enough. So what is Facebook doing—its fixing the problem.  I like free market fixes and Facebook is a perfect example of a market driving change. No lawsuits had to be filed (I am sure they will be anyway) or regulators had to jump in to tell Facebook that the way things are structured isn’t good enough and needs to change. So what Facebook is doing is making more basic data private.  It's making it easier to control different kinds of information to remain private, provide more ability on the users part to have even more customized settings and provide better control from outsiders to users.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-4190592259256203280?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/4190592259256203280/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=4190592259256203280' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/4190592259256203280'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/4190592259256203280'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/05/facebook-is-fixing-its-problem.html' title='Facebook is fixing its problem'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-8746431763346768433</id><published>2010-05-20T07:37:00.000-07:00</published><updated>2010-05-20T07:42:10.105-07:00</updated><title type='text'>Are they working???</title><content type='html'>After a few years with the new Federal Rules of Civil Procedure, I am left asking if it has helped. Is discovery any different? Well, I think so, but discovery is still expensive, a pain and major league inconvenience for many—but, I never thought that would go away anyway. There are cases that tell me much as changed. For example, in Calixto v. Watson Bowman Acme Corp, a case about intellectual property rights, the plaintiff sought to compel discovery on back-up tapes with a significant cost to ready them for the searching process. In the case, the court found that the backup tapes were not reasonably accessible due to undue cost and burden. That said, the defendant had to restore one backup tape to see if it contained deleted email from an employee. As you might remember one major change with the new rules was that discovery on “inaccessible data” would not necessarily be forced. The case is one example to say that it seems like they are working.  What do you think?  Write me with your thoughts.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-8746431763346768433?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/8746431763346768433/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=8746431763346768433' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/8746431763346768433'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/8746431763346768433'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/05/are-they-working.html' title='Are they working???'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-2580264411113018216</id><published>2010-05-18T10:25:00.000-07:00</published><updated>2010-05-18T10:32:05.736-07:00</updated><title type='text'>IT Ain’t About The Cloud</title><content type='html'>There is lots of conversation about the privacy and e-communications in the work world, especially with the Supreme Court ruling expected soon in City of Ontario, Calif. v. Quon. As you may know, the case is about the expectation of privacy when an employee uses an employer provided communications devise for personal reasons. In the case a police officer’s sent personal text messages on a department device were reviewed by the department and the officer sued for a violation of his expectation of privacy.  Confusion between official department policy which made clear the employees should NOT expect any right to privacy were watered down with a  supervisor ‘unofficial’ actions which allowed officers to personally pay for overuse text messaging charges with an understanding the their personal messages would not be reviewed. Even though the department policy was clear regarding the official “no expectation of privacy” for employee use of department-issued electronic communications devices(which the employee signed off on), the supervisor's “unofficial policy” and “creation of an unauthorized expectation of privacy” creates the rub in the case. Now in the employee’s favor he did pay for part of the use of the device and he did send personal messages off-duty so perhaps the employer was not clear about when and how the device should be used and maybe it in part became a “personal” device when he paid for its use. So what is clear—this case makes clear that employers better BE CLEAR about directives. This case is not about third party storage of the messages “in the cloud”, though some have made it about that very issue. This case is not about the court undoing employers rights to review e-communications when they are CLEAR about their “no expectation of privacy” policy. This case is not about what private vs. public employees should expect from their employer regarding monitoring. This case is only about the reasonable expectation of privacy of one officer when policy is made ambiguous by word and deed. The court may broaden its ruling but the case is about varying official policy and unofficial practices and how that impacts what employees expects. Remember in Information Nation: Seven Keys to Information Management Compliance, one of the keys makes clear the need to be consistent. Clear policies consistently applied.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-2580264411113018216?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/2580264411113018216/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=2580264411113018216' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/2580264411113018216'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/2580264411113018216'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/05/it-aint-about-cloud.html' title='IT Ain’t About The Cloud'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-1557357433212430812</id><published>2010-05-17T07:35:00.000-07:00</published><updated>2010-05-17T07:39:33.916-07:00</updated><title type='text'>Going “Business Naked” is Way Too Much Exposure</title><content type='html'>Many many months ago, homeowners started complaining of odors, metal being corroded,  respiratory ailments, headaches, nose bleeds, etc.  After many more months of investigations, it was determined that drywall produced in China was the likely culprit. Apparently Chinese produced drywall has a concentration of a sulfurous chemical, not found in US produced drywall and it was causing the problem. Anyway there has been lots of governmental wrangling over the issue for many more months. Many articles written about the problem and the passage of more time.  Finally, today  it was announced that rather than wait for lawsuits to be filed (because that is no fun and likely way more expensive) the Chinese drywall makers are agreeing to settle with large and small home builders in the US who in turn will likely settle with home owners and fix the “stinky” drywall problem. &lt;br /&gt;&lt;br /&gt;But how do we know which homes got Chinese drywall?  As you will recall, we had a major housing boom (a long, long time ago) and drywall was in hot demand. Builders were looking for a source for drywall from anywhere and anybody.  So we bought from the Chinese and it happened to have a high sulfur content or something similar which caused a bunch of problems. Well, I guess it’s good we live in America where we regulate what goes into drywall, baby food, dog food, paint for kids toys, etc.  But we are a global economy and get products from all over the world-like Chinese drywall for example. Anyway, once it went into homes, how do they know which home got Chinese drywall? Absent a complaint, how do we know which houses to investigate and which walls to replace? &lt;br /&gt;&lt;br /&gt;RECORDS. RECORDS. RECORDS.  According to the May 17, 2010 Wall Street Journal story covering this matter, “Builders will have to document that their problem drywall did indeed come from KPT (the Chinese drywall manufacturer)and show reasonable repair costs”.  Ok, got it-have records to show they bought Chinese drywall, records where the drywall was installed and records to prove expenses. We live in a world where records allow business to happen. Without them we are “business naked”.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-1557357433212430812?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/1557357433212430812/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=1557357433212430812' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/1557357433212430812'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/1557357433212430812'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/05/going-business-naked-is-way-too-much.html' title='Going “Business Naked” is Way Too Much Exposure'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-2012623253461534877</id><published>2010-03-05T11:50:00.000-08:00</published><updated>2010-05-10T07:43:10.990-07:00</updated><title type='text'>Where’s The Information Toyota</title><content type='html'>As if the heightened media attention on Toyota, its alleged design defects and the presence of the Mr. Toyoda on Capitol Hill was not enough negative attention, the February 27, 2010 Wall Street Journal article entitled, “Toyota Accused of Withholding Records” cuts to the heart of the issue seemingly haunting the car maker. If there were multiple common complaints about design defects which caused accidents, and the company knew of such problems, then why didn’t the company act earlier and with greater resolve. Companies “speak” with either records and/or its employees.  While employees forget, lie, retire, etc., records, if available, can demonstrate what happened and when. If complaints were made that showed common problems in certain car models, then law dictates records should exist and those records should document such failures. If requested in a lawsuit or investigation records should have been provided whether or not they hurt Toyota.&lt;br /&gt;   &lt;br /&gt;I make no apologies for Toyota--if they hid or destroyed evidence of design defects then they should pay the price. In other words, intentionally hiding evidence is a serious issue that needs to be punished. On the other hand, if information was not produced because after reasonable attempts, it could not be found, then maybe the courts or regulators should punish less harshly or maybe not at all. I don’t know if this is relevant to the problems facing Toyota, but I do know it is a reality in litigation in today’s explosive information world. Information volumes are growing so fast that knowing all the potentially relevant evidence in a lawsuit is almost impossible.  Compounding matters, employees use endless new communications technologies making management of the expanding information universe worse than drinking from a fire hose.  Finding all relevant evidence in the world that executes contracts in email, modifies them in a text message and breaches them in a blog is a challenge for all of us.   In today’s litigation world, if you look closely enough at any company, you will understand why unearthing and producing ALL relevant information is a nonstarter. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;---  Submitted by Randolph Kahn, ESQ.  Author of Information Nation and Email Rules.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-2012623253461534877?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/2012623253461534877/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=2012623253461534877' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/2012623253461534877'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/2012623253461534877'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/03/wheres-information-toyota.html' title='Where’s The Information Toyota'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-7878840386190774207</id><published>2010-05-03T13:27:00.000-07:00</published><updated>2010-05-10T07:39:24.235-07:00</updated><title type='text'>Manage your email.</title><content type='html'>Poor “Fab”.  You ask me, "Who is or what is Fab?" He is Fabrice Tourre, a highly compensated French speaking financial guru at the epicenter of the Goldman debacle clouding Wall Street and Washington these days. He is the guy who wrote the email “suggesting” that the investments Goldman was involved with were not nearly as attractive as they wanted others to believe. I don’t really want to get into the Goldman case or what Fab knew or didn’t know. Rather, I wanted to go back to the 50,000 pound gorilla in the room. The point is best stated by the April 29, 2010 Wall Street Journal Article entitled, “Backlash Against Email Builds”.  Don’t blame the messenger for the idiotic actions of your colleagues. As far back as “Email Rules” I was telling you to manage the medium. If done right it is your organization’s best productivity tool. When mismanaged it is a major source of headache. Duh.  Fab was doing his job. Maybe he was saying stuff he shouldn’t have. Maybe he was being flip. Whatever. Get over it and manage it. And perhaps you need more training. Have I got a training session for you :)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-7878840386190774207?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/7878840386190774207/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=7878840386190774207' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/7878840386190774207'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/7878840386190774207'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/05/manage-your-email.html' title='Manage your email.'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-3819050608329040796</id><published>2010-05-07T12:26:00.000-07:00</published><updated>2010-05-10T07:36:15.282-07:00</updated><title type='text'>Not Good. Not Bad. Just Are.</title><content type='html'>I am often asked if Records Retention should consider the likelihood of being forced to produce records in a lawsuit. My response--records are neither good nor bad, They just are. And you manage them without regard to how they may impact you later on. Sometime they can really offer up protection not just be the treasure trove of smoking guns. Take for example the recent move by the Catholic Church. The Catholic Church has been rocked with endless sexual abuse scandals in which it has been widely reported that the Church “covered” up numerous egregious child molestations for years across the globe. Now the Church is going to use its records to come clean. According to the Wall Street Journal on May 7, 2010, “Roman Catholic bishops in countries across Europe are trying to get ahead of a widening sexual-abuse scandal by employing a potentially risky strategy—pre-emptively digging through church archives to see what skeletons remain to be unearthed”&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-3819050608329040796?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/3819050608329040796/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=3819050608329040796' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/3819050608329040796'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/3819050608329040796'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/05/not-good-not-bad-just-are.html' title='Not Good. Not Bad. Just Are.'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-6236110119325016424</id><published>2010-02-18T08:32:00.000-08:00</published><updated>2010-02-18T08:33:13.091-08:00</updated><title type='text'>The Nose Test</title><content type='html'>We were drafting a legal hold policy for a client’s law department when the client asked when it was necessary to issue a legal hold notice to preserve information. My answer usually involves an application of the nose test—which is “the first smell of trouble”. But what is trouble? Great question. Let me consult my nose. My nose says, “it might involve getting into trouble with a regulator or court.”   OK, got it.  But that is really way too simple. No doubt failure to provide employees with timely notice of the need to preserve information for a pending, threatened or imminent lawsuit is essential. In a recent court case a judge made the following statement “…plaintiffs failed to timely institute written litigation holds and engaged in careless and indifferent collection efforts after the duty to preserve arose. As a result, there can be little doubt that some documents were lost or destroyed.” But, making a determination of when to do it is not simple and has serious implications.  &lt;br /&gt;Say I’m an insurance company, do I need to issue a legal hold notice every time I get a letter from an annoyed insurance policy owner. Oh. If I issue early—at the FIRST smell of trouble, I might over-preserve. How about preserving after we get served with a lawsuit? Well, that may be too late especially if a lot happens before the lawsuit. What if we get a nasty gram from a lawyer demanding the matter be addressed? How about a letter to mediate? How about a written complaint filed with the state department of insurance? How about a notice by the state that it intends to commence an investigation? You get the idea, before a lawsuit is filed, much can happen that should commence the legal hold notice process. So what to do. We deal with it all the time and if you want our help, please call early and often.  Clearly earlier in time is safer. So a threatened lawsuit is earlier in time than a filed one but it has implications. Bottom line it’s a lawyers question and don’t let them delegate to you IT or RIM.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-6236110119325016424?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/6236110119325016424/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=6236110119325016424' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/6236110119325016424'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/6236110119325016424'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/02/nose-test.html' title='The Nose Test'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-4006569807050138045</id><published>2010-02-10T08:06:00.000-08:00</published><updated>2010-02-10T08:17:01.503-08:00</updated><title type='text'>Case Law and Text Messages</title><content type='html'>A client recently asked me what is real life meaning of ESI (electronically stored information, the term used by the Federal Rules Of Evidence ”FRE”). In the old days I used to say “if it was relevant and available even if it was on the bottom on my shoe, cough it up”. Well, that may have been a bit too cute, but the point remains—evidence that is even potentially relevant needs to preserved and produced to the other side in litigation, even if it hurts your legal position. Only a little has changed with the amendments to the FRE. There are exceptions—you may not have to produce “inaccessible data”.   But in the end, you may have to do discovery on e-stuff that you normally don’t think about. There are cases where even temporary cache files had to be produced. There is now case law that covers text messages. &lt;br /&gt;In Southeastern Mechanical Services, Inc. v. Brody (M.D. Fla. Aug. 31, 2009) employees had to produce text messages from devices owned by the company and personally owned devices.  Because the employees apparently “cleaned” the devices in this case, it turned into a destruction of evidence case.  Beware, ESI could be just about anything. Plan, Prepare, Preserve and Produce.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-4006569807050138045?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/4006569807050138045/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=4006569807050138045' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/4006569807050138045'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/4006569807050138045'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/02/case-law-and-text-messages.html' title='Case Law and Text Messages'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-2699166023939737271</id><published>2010-02-03T11:09:00.000-08:00</published><updated>2010-02-03T11:13:46.842-08:00</updated><title type='text'>To Preserve or Not To Preserve? That is the question</title><content type='html'>Hey IT-don’t accept the quiet delegation by the lawyers of determining relevance in a lawsuit. Err-Maybe overly broad(preserve everything) legal holds are not good. Err-Hey lawyer do your job and tell me, IT, what to preserve based on the facts of YOUR case. Lawyers (some of the lazy or fearful ones) like to lock down the whole place when they learn of a lawsuit. Keep everything just in case is their battle cry. Well its bad guidance most of the time, unless really required. Stopping the inner workings of the IT shop to preserve everything, creates a whole host of new issues. So don’t bite until you make the lawyers show you why it’s needed. Case in point. The Federal Court-7th Circuit are developing principles to better manage e-discovery. The E-Discovery Committee’s stated goals are “the fostering of a better balance for the ‘just, speedy and inexpensive’ determination of cases…” &lt;br /&gt;&lt;br /&gt;Under proposed Principle 2.04 (Scope of Preservation)&lt;br /&gt;(a) Every party to litigation and its counsel are responsible for taking reasonable and proportionate steps to preserve relevant and discoverable ESI within its possession, custody or control. Determining which steps are reasonable and proportionate in particular litigation is a fact specific inquiry that will vary from case to case. The parties and counsel should address preservation issues at the outset of a case, and should continue to address them as the case progresses and their understanding of the issues and the facts improves.&lt;br /&gt;&lt;br /&gt;Whether or not it becomes the “rule” or not, it’s good guidance to you. The courts don’t require everything needs to be preserved, so don’t do it just because.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-2699166023939737271?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/2699166023939737271/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=2699166023939737271' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/2699166023939737271'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/2699166023939737271'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/02/to-preserve-or-not-to-preserve-that-is.html' title='To Preserve or Not To Preserve? That is the question'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6791672639619957449.post-4373423642899182636</id><published>2010-01-28T07:50:00.000-08:00</published><updated>2010-01-28T07:56:48.744-08:00</updated><title type='text'>Flying through THE CLOUD with a  Lawyer on Your Back.</title><content type='html'>Just about everything I hear lately has something to do with “THE CLOUD”.  I am just wondering is that like outsourcing or the ASP (application service provider) model of the dotbomb era? Don’t get me wrong, I like jingoisms as much as the next guy. I just need to know what they mean and their implications. Cloud computing is using the internet to bring technology or more likely software application to you. And it is not really bringing them to you it is making them available to you over the internet. For me they are really like the ASP model of yesterday year.  So I take no issue with the name Cloud Computing. In fact I don’t think “THE CLOUD” is inherently good or bad. But it is different and you should consider how it is different from using software you pay for within your computing environment.  Just a few things to think about when using someone else’s software application on their environment for business purposes—in other words, “Cloud Computing”. &lt;br /&gt;1. Sometimes relationships go bad or even end and when they do how will you get your information back or have access to it without their “Cloudware”&lt;br /&gt;2. You can’t delegate your legal responsibilities so remember privacy, security, records retention, tax filing support , etc.  don’t go away just because your data is floating elsewhere.&lt;br /&gt;3. If you need to have access to your Cloud data for litigation purposes, will your provider accommodate the request and in a timely and defensible fashion?&lt;br /&gt;4. When a regulator wants to see the data or check to make sure it is being stored in accordance with regulations (if they exist for the industry or type of data at issue) will the government deem the environment OK for the task for which they were hired?&lt;br /&gt;5. The rules the Cloud Co. may be following may be different than yours so make sure they follow rules you can live with or contractually make them  follow your rules. &lt;br /&gt;6. Anticipate new governance, risk and compliance risks.&lt;br /&gt;7. Make sure the Cloud Co. deals with your disaster recovery requirements. &lt;br /&gt;8. Make sure your litigation response process and e-discovery plan can be accommodated in the Cloud.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6791672639619957449-4373423642899182636?l=infonation.kahnconsultinginc.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://infonation.kahnconsultinginc.com/feeds/4373423642899182636/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='https://www.blogger.com/comment.g?blogID=6791672639619957449&amp;postID=4373423642899182636' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/4373423642899182636'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6791672639619957449/posts/default/4373423642899182636'/><link rel='alternate' type='text/html' href='http://infonation.kahnconsultinginc.com/2010/01/flying-through-cloud-with-lawyer-on.html' title='Flying through THE CLOUD with a  Lawyer on Your Back.'/><author><name>Kahn Consulting, Inc.</name><uri>http://www.blogger.com/profile/11367856263754886994</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='00583272081423073833'/></author><thr:total>0</thr:total></entry></feed>