I thought, in terms of Jira and Confluence at least, it was just accepted that being slow and underperforming was the status quo and if it was running at a speed you'd consider normal, that's an exception (and cause for alarm... like "did that actually save or is there a silent JS error not being displayed?").
> 3.3. Restrictions. Except as otherwise expressly permitted in these Terms, you will not:
> (i) publicly disseminate information regarding the performance of the Cloud Products; or (j) encourage or assist any third party to do any of the foregoing.
I wouldn’t expect the larger question of what organizational and management issues lead to the problem in the larger sense to be made public. At least not while the issue is still fresh. Maybe down the road as a business school case study after some of the players retire.
However, there's one point that makes me skeptical: there are no organizational changes, or changes to leadership, or anything in that direction.
This sounds like "the tech guys screwed up, culture and management is fine here". Which it might be, or it might not.
I would have loved to see
5. We will stop pushing customers so hard towards using our cloud
for one, but that wouldn't be convenient for Atlassian.