Mobile releases are good enough… right? 

Maybe your releases take too much time and are an annoyance for the engineers who have to focus their attention on them — but that’s just work. Work is supposed to be frustrating and waste everyone’s time, yeah?

Don’t read this white paper if you’re okay with: 

Spending time on admin tasks instead of features: Releases can take 4 to 10 hours of an engineer’s time. Would it actually be all that helpful to get this down to 30 minutes?   

Managing a list of 100 manual release steps: This stresses a lot of engineers out every single time they have to do it. You could get this down to just a few manual tasks, but why bother?  

Nobody knowing what’s going on with the release: Only the release manager ever knows how the release is going, but you (and everyone else) can just pester them every 30 minutes in Slack. What good would providing visibility to everyone do? 

A fragile release process: Every third release is delayed because of some failure in the process or a lack of communication. You could get updates out to your customers on a standardized basis, but do they really deserve that?   

Mobile apps only drive an [insert here] percentage of your revenue, so this is all probably good enough. Why make even more money if you don’t have to?