There have lately been a boatload of good stories written about Google’s so-called ‘Billion Dollar E-Discovery Blunder.’ Yes, it was a blunder, and, though the damages are dwindling, maybe it will end up costing Google a billion bucks; but, I’m not so sure it’s all that much an e-discovery issue. That said, I’m going to wind this post up with a suggestion of a simple technique for QA/QC in e-discovery you can use to keep your client or company from the same predicament.
First, the Blunder: Oracle sued Google claiming that Google’s Android smartphone platform infringes Oracle’s Java programming language patents. With almost $27 billion in revenue and $6 billion in profits, Oracle is #96 on the Fortune 500 list of companies that suck at e-discovery. Google is #92, with $29 billion in revenues and $8.5 billion in profits. So, it’s a well-matched, Goliath vs. Goliath fight (and even Goliath is going, “Damn, they’re big and rich”).
Plus, it’s got to be personal for many folks in Silicon Valley. Redwood City and Mountain View, California are just minutes apart, so you can imagine that when the two Larrys (Oracle’s Ellison and Google’s Page) bump into each other at Fry’s or waiting in line at the DMV, it’s can’t be all guy hugs and fist bumps. Continue reading








