These days, caring for users more than you already do needs a budget. Otherwise, the question raised about reliability in your last meeting, the outage you just recovered from and could be prevented, etc, they all end up backlog residents. So the matter isn't simply about whether you care, a lot of people do, they just can't for various reasons. Some aren't even aware. Capacity and awareness are to be considered with too. This gets translated into care for consumers, users, business and continuity. Then long story short is yes, you need a reliability strategy. It depends. It always does. Insight into reliability is valuable, especially when you can implement before things break. Where I find this especially relevant: If you work with: Containers and Kubernetes Internal developer platforms A team large enough to fight over merge conflicts CI/CD pipelines that break more than they build [if you're not able to ship your ideas from cradle to grave with ease,...