It’s true that here at Atlassian, we’re constantly improving, testing, and releasing new features, security updates, and patches. But in a world where business needs, security best practices, and user expectations are constantly changing, that’s the only way to keep up.
There are costs to a slow release schedule. The most obvious is that if security falls behind, a disaster could be in your business future. In the first half of 2019 alone, data breaches exposed 4.1 billion records. And if a hack takes your business offline? Experts estimate downtime costs companies an average of $5,600 to $9,000 per minute.
Another obvious cost is compliance. If your systems aren’t compliant with the legal requirements of your location or industry, you’re in for a world of hurt, which means compliance updates need to happen just as fast as their security counterparts.
Also obvious is the cost of being behind the innovation curve. Slow release schedules make it easy for competitors to outpace your teams in a world where speed can make or break profits.
A less obvious (though no less important) cost is team time. Small, frequent updates are easy to get used to and won’t slow teams down, while yearly or bi-yearly updates require your teams to face a sometimes-massive learning curve on new features or interface updates. Not to mention that those big updates may introduce new bugs—and without frequent fixes, teams have to work around them for months on end.