Orogogus wrote on Sep 20, 2023, 01:26:
RogueSix wrote on Sep 19, 2023, 20:10:Then people would just mock them for acting as if the news didn't exist. "Deafening silence" is the usual term for when a company tries to ignore something. And employees don't usually appreciate it when they have to learn about these things from outside sources, or managers when they hear about them from their subordinates before Corporate.
Sepharo wrote on Sep 19, 2023, 19:59:The sole reason that they felt forced to write an internal memo at all speaks volumes about their adrenaline levels. The confident way to deal with this would have been to not comment at all, at least not in a written format.
Where are you two seeing panic?
Well, it was too late for that already, right? The employees read about the leaks in the news first. Then MS sent out that memo for internal "damage control" (not really). They should have reacted with a public one liner press release like "We do not comment on unannounced projects
" just as many/most other corps in their position do. Then investigate internally regarding the source of the leak.
Like, when someone quits/is fired and there's no company email, the higher up they were the more it's going to lower employees' opinion of the company; if they get it from the news while the company says nothing then they'll think the company's a joke
I do not think that is comparable. Besides, if a higher up of some significance quits/leaves/is fired then, depending on the size of the company, the right thing to do (imo) would be to either inform the employees directly in a team meeting/team call, or in a huge corporation, to inform/brief the team leads and have them pass on the information to the individual teams.
This really depends though. Like, if the boss of Machine Games quits/leaves/is fired, would you really have to inform everyone across the entire Microsoft corporation in an internal memo? Not in my world. I'd keep this within Machine Games and the executive leads at Bethesda. That is all the people who need to know.
If you make too much of a big deal of something then you do not engage in damage control but you make yourself look like you are in "panic mode". Which MS did here. They handled it poorly and the fact that the internal memo leaked on top of the actual leak is the icing on the shitcake
They should have brushed this off with a short public press release. Then investigate internally regarding the source of the leaks. Everything else (teams/projects potentially affected by the leak) should have been discussed with the leads of those teams/projects directly and internally.