I have been working in a company that has a large monolith. The developers have been split into domains and largely been focussed on their own area.
Over time each of the domains has atrophied their understanding of the other domains.
We recentlty had some larger cross domain projects started. These also cross into some of the systems that surround the monolith.
The pure DDD ideal of having a service belonging only to one team is now causing new bottlenecks. If a service needs to be used by all the surrounding systems this will happen.
The easiest solution would be to start accepting PRs from outside of the supporting team. The downside is that the bottleneck now becomes reviewing the changes.
We really need to have a big picture view of the system somewhere. Currently we have many competing (and contradictory) views.
Designers would benefit from this. We recently we given a piece of UI work that requires a new API from the constrained team.
We would have benefited from a user needs mapping session to make it clear which team owns the various capabilities.
Developer Rants 