I've been rereading Baudrillard's Simulations, the book most people regard as
the basis for the Matrix motion pictures. Not coincidentally, it's the book that Neo pulls off the shelf in his apartment during the first episode. It's an excellent (if difficult) book to read, because he has a valuable ability common to lunatics: the ability to see the way the world really is, with so much greater clarity than the rest of us who are "sane." Anyway, it's a small book
with big
ideas -- big ideas with practical application.
My personal favorite concept in the book is this: representations can kill what they represent. I call this Baudrillard's Paradox. A couple of his more provocative examples include...
God dies with the birth of religion.
What is truly social dies with the advent of socialism.
So, what does this have to do with anything practical? I'll give you two examples, starting with a personal one.
At Eyeris, we operate a Systrust/SAS-70 certified hosting operation. There are lots of documented procedures and controls. Lots. Those procedures evolved over years of thoughtful work by Eyeris' founders. Careful documentation then allowed the process to be delegated to others. And, most of the time, everything runs great. But, when things go haywire in the process, it's almost always for the same reason: a thoughtfully designed process document becomes a substitute for thoughtful work. Now, clearly, I am not advocating seat-of-the-pants make-it-up-as-you-go processes; but, we have to remember that ALL good work is brain-turned-on, eyes open, creative, thoughtful work -- whether it's documented and routine, or not.
A more general example of Baudrillard's Paradox is this:
True business intelligence dies
where Business Intelligence thrives.
BI as we know it today is a representation or simulation, attempting to mimic the signs of business intelligence. That is, if you observe some of the signs of true business intelligence, you will see reports going from thoughtful analysts to decision makers. But, the presence of reports does NOT imply thoughtful analysis. In fact, it can mean the opposite -- stunting the urge to analyze, by providing a (poor) substitute. BI needs to get back to its thoughtful, messy, human, creative, experimental, investigative roots -- and away from the antiseptic, lifeless, thoughtless farms of frozen, pre-digested reports.