An internal Google email shows how the company cracks down on leaks
theverge.com
theverge.com
> The lawsuit alleges that Google’s leaks policy covers essentially all company information and prohibits reasonable discussion about company activities.
...
> One policy allegedly even prevents employees from writing a novel about working for a large Silicon Valley corporation — like, for instance, Dave Eggers’ dystopian novel, The Circle — without first getting final draft approval from Google.
John Doe v. Google, Inc [1].
[1] https://www.scribd.com/document/334736972/John-Doe-vs-Google...
> If you’re considering sharing confidential information to a reporter—or to anyone externally—for the love of all that’s Googley, please reconsider! Not only could it cost you your job, but it also betrays the values that makes us a community.
So the question is-- what constitutes "confidential" at Google?
Let's say a bad apple-- coworker or boss-- is abusing their power in a way that affects a particular class of employees, and the employee has exhausted the proper internal channels without success/resolution.
Is that information "confidential" according to the typical contract Google employees sign?
I'd really like to hear an answer from a current or former Google employee, and preferably a yes/no answer.
One would need to understand the frequency at which misses vs false-alarms happen to judge whether this is a big deal or not.
From one data-point alone, this is absolutely a "non-story".
No, you do not give the accuser (and in this case, the company firing someone from their job) the 'benefit of the doubt' in my world.
Either it's a clear cut case (fine) or it's not (if you fire someone in this case, you're an asshole working for a shitty company).
Now, I'm not saying that Google DID this. But the defendant should have the benefit of the doubt.
"Please remember: whether malicious or unintentional, leaks damage our culture. Be aware of the company information you share and with whom you share it. If you’re considering sharing confidential information to a reporter—or to anyone externally—for the love of all that’s Googley, please reconsider! Not only could it cost you your job, but it also betrays the values that makes us a community."
I certainly understand the potential business impact leaking information, but what is the aspect of the Google culture a leaked email harms?
Google is enormously transparent internally. The more there are leaks, the less incentive there is to be transparent.
The "corporate person" is being a sociopath as usual and rather than saying "it harms our company" they attempt to spin it into something that hurts the individuals that work at the company. It doesn't. It hurts the "corporate person", but they can't come out and say that.
Eric Schmidt believes you shouldn't do anything you wouldn't want to share with anyone (aka Google). Why doesn't that work both ways? Does Google have "something to hide"?
Or is Google exempt from the whole "privacy is a thing of the past" situation these companies are trying to force on us all?
An interesting challenge when I was there was leaving your workstation unlocked. You go up to get a soda or something and don't want to lock your workstation, go get your beverage, come back and reenter your password. But you should, someone in your cube or nearby could prank you and send an email to the group of an embarrassing nature. Of course they could also send an internal only email to re/code which if they didn't like you might get you fired.
The key is keeping the investigation folks above reproach. If they can't convince that they have done a fair job investigating, you open yourself up for a lot of issues down the road.
Interesting story involving Mr Katz: http://www.dailymail.co.uk/news/article-2224589/Google-threa...
"Bureau of Diplomatic Security, Office of Investigations and Counterintelligence,Counterintelligence Division (CI division)"
With 3 branches:
DS/CI/ASB - Analysis Branch
DS/CI/IB - Investigations Branch
DS/CI/PPR - Policy and Programs Branch