But most companies do not have a lot of experienced architects building products. A lot of companies can barely keep a handle on their dev teams, and worry a lot more about regulation and herding cats than building a decent product, so their Architecture Teams are actually Cover-Your-Ass Teams. Dev teams often don't even know that other teams exist, much less have any way to circulate a single diagram to them all, or talk about what the hell it's even for.
If all you've ever worked in is a tech company in San Francisco/Seattle, let me tell you... It's ugly out here in the land of normal businesses.
So software architecture is really for the average people working in average companies who could use a hand figuring out how to design and implement their product. They have never even heard of C4 or ADR. But those simple models and processes would absolutely transform their work from barely-functioning balls of shit, into the gloriously robust design the author's company came up with. Nobody else is helping them figure out how to do it; best practice is what they've got to work with. If they even know about it.