Breaking up monolithic "cloud" teams has been something I've found myself arguing for lately.
Most of the orgs I've worked for have a "cloud" team, which is actually an IaaS team.
I've tried illustrating the gap between traditional IaaS and modern PaaS/CaaS/FaaS.
The governance, tools, skills and ways of working are all different enough that a single monolithic "cloud" team isn't likely to cover them both.
At the working level: Be a good example of whatever paradigm you're in.
Execs: Please don't put the same people in charge of multiple (largely opposite) paradigms.
