The difficulty with these articles is that they don't really clearly define what the organization looks like when they say "include all teams in incident manage

The difficulty with these articles is that they don't really clearly define what the organization looks like when they say "include all teams in incident management". Are they talking about a system where there is an "SRE Team" that all incidents go through? That sounds inefficient, and yes include all teams. What does their problem SRE team look like, and what does their ideal SRE team look like. In my experience the SRE team is doing things like building the CI/CD platform, the Environments, Infrastructure, etc. So that when I make an application, and commit my code, it then creates the infrastructure, and deploys my code. In this paradigm, an incident with my application goes to me, and an incident with the infrastructure breaking is on the SRE team. An incident with a firewall being configured wrong doesn't make sense to go to the UI devs that put a new microservice up, and an incident with UI not displaying values right doesn't go to SRE. Since this article says there is no CI/CD in the SRE team, it makes me think that this is some kind of operations incident response team, and thus I would say misnamed.