How can we deal with change management

3 common myths about change management in the cloud

It is true that at Atlassian we are constantly working on improvements, testing and releasing new features, updates and patches. And in an environment where business needs, security best practices, and user expectations are constantly changing, this is the only way to stay tuned.

A slow release schedule has consequences. For example, neglecting security will have dramatic consequences for your business. In the first half of 2019 alone, 4.1 billion data records were disclosed in the event of data breaches. What if a hack brings your business to a standstill? Experts estimate that business downtime averages $ 5,600-9,000 per minute costs.

Compliance is also affected. If your systems do not meet the legal requirements in your location or in your industry, you can expect big problems. For this reason, compliance updates need to be carried out just as quickly as security updates.

It also makes sense that you could lose your innovative edge. Slow release schedules allow competitors to overtake your teams right now when speed is the only way to make a profit.

A less clear (but no less important) consequence is teamwork time. Small, frequent updates are something that you can get used to quickly and that don't slow the teams down. Annual or semi-annual updates, on the other hand, require that your teams sometimes first have to deal intensively with new functions or interface updates. And of course such large updates can also introduce new bugs that your teams have to work around for months without regular bug fixes.