Take the deployment strategy. The choice is wide, with Blue-Green at one extreme: with this you take the least risk, but it is the most complex and costly. This is because you always have two environments running here that you can switch between. As a result, when changes or problems occur, you experience minimal downtime.
The other extreme is working with backups. And there are some variants in between, such as the Canary release. In doing so, you direct one of the traffic to a new version, the other part does not. If something goes wrong, at most half the customers are affected. Relatively easy, but with a bit more risk.
When it comes to mitigating risk, starting small and in-house is recommended. Automate a task that is performed relatively frequently and has many manual components. You thus create a defined entity to practice with. If something goes wrong, your customers won’t suffer. While you do see immediate results. Low risk, high impact. If you have gained some experience, then you can roll it out more broadly.