| What is with this thread of conversation? "Don't send emails like that because they could end up in eDiscovery." How about, don't do things in a way where eDiscovery is likely to be an outcome, and actually foster processes that act on quality issues instead of telling the people you're shouldering with making this work with enough weight on their conscience that the only way they feel like they can cope with the foreseeable tragedy is to at least make sure there is some note in the record somewhere that they tried and could do nothing despite it all? I have absolutely no respect for for anyone who is so caught up with these messages sound, that they can't read between the lines to see the picture of the completely dysfunctional dynamic these people had to be operating within. The lower an engineer ends up stooping, the worse and more endemic the problems they are facing likely are. If your company has those types of email at all, whether they get out should be the least of your concerns! The mentality being demonstrated admonishing delivery and sweating on the damage from dirty laundry being aired instead of the fact there is dirty laundry to air at all is like worrying whether or not you left the faucet on when your house is below sea level, and the tsunami is already on the way. And apologies to those from New Orleans, or the Netherlands; to be fair I could have used leaving the burner on and fires on the way and pissed off the Californians and Aussies, but water was the first thing that came to mind. And I'm not letting the engineers entirely off the hook either! If they felt that strongly, they should have walked away to, but I can forgive a lot more in the name of familial security than I can the pursuit of profit at all costs. |