[Riod]

This was rather clumsily written. Even if your company messed up, shoving your CEO with a boot up his ass is bad for morale. The reason why most communiques are generic is because there's very little upside to being abrupt publicly.

[exw]

<<The reason why most communiques are generic is because there's very little upside to being abrupt publicly.>>

You are quite wrong, if anything, employees appreciate openness and decisiveness, vs. sweeping changes under the rug with generic language. There is actually a ton of upside to creating honest communication, but it's much harder than hiding behind empty phrases, which then builds a culture of speculation (of what "really happened"), politics, and distrust.

I have no idea what really happened behind the scenes and why exactly the new CEO used this language, but I can assure you that any email from David Sacks will not be clumsy, but very deliberate and written to achieve a specific purpose. (There is some speculation on earlier threads around of why it might have been written this way).

[Riod]

Not talking about employees. You can release whatever message you want internally. It's the external message where upside downside needs to be a consideration. By which I mean whatever you say in email can be printed and quoted. Disseminate the message not email

[exw]

I both appreciate and agree with your point, but in this case I think the issues was that their new CEO had to assume that, given the high visibility of the company, whatever message he was going to send out to his internal team was also going to get leaked to the press.

If you are in that type of situation, you have to chose between your employees and external parties, and looks like he decided that creating a trusted relationships with his employees was more important...

[Riod]

Maybe that was how he was thinking about it. Hope it works out for them. Cheers.