It's way too easy to just add a lot of friction if you go too far. I also think it would be way healthier if teams acted as "maintainers" rather than "sole dev

It's way too easy to just add a lot of friction if you go too far. I also think it would be way healthier if teams acted as "maintainers" rather than "sole developer" of a service. For example if team A wants feature from service team B manages they should be free (after communicating that so there is no confict/work duplication) to just make that feature and submit pull request to the team B. Then team B can make sure it's up to their standard but that's shorter work than getting the whole machine of "submit a ticket for team B to add feature, find manpower to do it, and schedule work" running.