In some companies teams are not divided in a way that follow technical faultlines, but rather after "product owners" so that the only valid divison lines are ex

In some companies teams are not divided in a way that follow technical faultlines, but rather after "product owners" so that the only valid divison lines are exteral facing superficial aspects. E.g. think a car company where you are not organized as "engine team" and "transmission team", but rather "sedan team" and "SUV team", and the engine and transmission just need to happen somehow. The microservices fad and "every team own their own services" fad combined can really get performance to a halt in such a setting. Product owners are suddenly the unwilling and unwitting chief architects. At least with a monolith, everything is reasonably standardized and people from different teams can be expected to contribute to larger parts of it..