In my experience the issue is that teams don't have influence beyond their team or sister teams. "We got paged last night because of unexpected problem in Syst

In my experience the issue is that teams don't have influence beyond their team or sister teams. "We got paged last night because of unexpected problem in System X and an associated config change in System Y meant our transitive dependency System Z did something we weren't expecting so our service went down." Ok fine but what can we fix? You can "strategize" as much as you like to fix the wider problem, but is that inside your team's sphere of influence? If your strategy requires addressing the root-cause why, but that means you have to go change/replace other team's infrastructure/operational practices/etc ("we should change System X to use k8s, and then System Z is obsolete and we can refactor System Y to use NoSQL instead of poatgres then we will have solved the why"), it is unlikely to be something that is decided in your small team in reaction to a page. TL;Dr - Your team of 5 or 6 is not the correct group to decide the overall strategy for changing your entire company's technical architecture.