"Why risk it if you don't have to?" <- is the dead tell.
Risk pervades everything we do. Every decision you make has risk on both sides, and humans are incredibly bad at reasoning about risk. en.m.wikipedia.org/wiki/List_of_c…
deploy == risk
no deploys == no risk
Indeed, this is how many people do think about risk; and if you zoom far enough in on any single deploy, it may even seem true. Any individual deploy *may* temporarily elevate risk.
🐌 What of the risk of delaying deploys?
🕷 What about the risk of batching up multiple changes by multiple devs?
🐛 Or the chances of forgetting what was in those diffs, days later?
🦗 Or the risk of decoupling the development of code from delivery to users?
🐞 And what risks do you run by *not* fixing bugs or delivering any value to users for 20% of every week?
Only you can decide which is higher risk for your org at this point in time. What matters is that you see clearly how to reduce that risk.