That's good, but that still produces friction AND reduces the sense of the ownership of the owning team. > I just don't want there to be a no-man's-land. A di

That's good, but that still produces friction AND reduces the sense of the ownership of the owning team. > I just don't want there to be a no-man's-land. A different model I've seen is that the ownership of the whole system is shared across the trusted senior members (every team has one, but you need to get an approval from an external one). One thing this avoids is the bottleneck on specific teams (only team X can approve the PR, but they're now super busy with their own features).