Re:Inside the longest Atlassian outage
by staticautomatic on Wednesday April 13, 2022 @11:00PM
(#31022993)
Fair enough, but anyone who’s been around the block on crisis communications knows that you’re supposed to hit the big red “stop all regular communications until we get a fucking handle on this” button.
The defense that this is a scheduled posting doesn’t help their argument at all. It really points to the fact that they were entirely unprepared to respond to an event like this. Like you said — when you’re in the middle of a crisis, there is no such thing as “regular communication”.
You think Atlassian should have the ability to stop posts on all of their individual employees' social media posts?
Re:Inside the longest Atlassian outage
by DharmaPolice on Thursday April 14, 2022 @12:53AM
(#31023537)
I think senior management would want to have a mechanism to halt their own scheduled posts in a crisis, yeah.
This was a conference they hosted, not just some Atlassian team members partying in Vegas: https://events.atlassian.com/team22
Thousands of Atlassian customers bought tickets, flights, and hotels for the event. It's unreasonable to suggest that they should cancel it all days before the event.
> Atlassian's Global Head of Customer Success probably should have been fired but here she is promoting Atlassian Cloud on LinkedIn three days ago: https://www.linkedin.com/mwlite/in/gertie-rizzo-5b70061
She responded that it was a scheduled post. This is normal on LinkedIn: Marketers write a lot of posts all at once and schedule them to come out periodically. They're not literally sitting down in front of LinkedIn and typing out their daily puff piece.
Please, let's drop the pitchforks. It's not a good look for us on HN, especially when the facts are being completely misinterpreted.