Your Blog post @jesper made me immediately think of Wardley Maps (Simon Wardley), specifically when describing software systems that build on top of each other because they have early fast moving, slow-moving, and slower production components to their lifecycle. The QA involvements in the fast-moving scouting-mode parts of a business are often almost absent, and these grows in QA maturity as parts age.
I am recalling a time where a large company I worked in had a small core of QA thought leaders, ultimately they not only taught methodology and helped make decisions, but sometimes did have to do the real work. Over time this little team dissolved sadly ~2017, but it was called a TCoE, and I wonder if it dissolved at the same time that it did for other large companies. Personally I was always a fan of actually doing-the-doing, but the need to have someone knowing where the risks lay longer term. So a TCoE that works to be heading future risks off tactically by training testers in new tech or tools beforehand becomes useful if you are big. And having some “distance” gets useful, but it also makes it easy to fire you.
I always though for example that Test Evangelist was a approximate title in the TCE, but that Test Analyst, for example, was part of the product team of testers, and held detailed domain knowledge (and you probably don’t want to fire him/her).
But yes, would like to have been able to propose a Wardley Map of our process a decade ago and possibly, understood it all much better.