Reply to thread

Message: <blockquote data-quote="Whizbang Dustyboots" data-source="post: 9618214" data-attributes="member: 11760">Unless you solve for the basic condition -- an organization full of unhappy people and a larger community of even unhappier freelancers and third-party contractors -- efforts to run around putting out fires is ultimately doomed to fail, since only one person has to successfully leak.You can't threaten your way into stopping leaks, as even a casual glance at the news for the past century will show.The way to have the OGL crisis not leak would have been to make it crystal clear to the everyone in the loop that this was absolutely not happening at the moment (which they definitely didn't do) and that they were genuinely just asking innocently (which was also not the message conveyed to the leakers we heard from).And even then, the whole concept was so outrageous -- and apparently done over the objections of unhappy in-house staff -- that it was probably impossible to stop 100% of leaks.So, listen to your in-house staff and make them feel like the system works for being heard. And when you engage with people outside that circle, work even harder at it.In this case, the OGL crisis should have been stopped when people in-house were saying "whoa, this is a terrible idea," instead of just steamrolling them and telling them it was going to happen.</blockquote>