Tech
Meetings Held Instead of Interfaces Redesigned
If two departments or two modules need constant meetings to coordinate, the diagnosis points to a bad interface, not a need for more meetings. The time those humans spend in meetings should be invested in redesigning the interface until the meetings are no longer needed.
Constant meetings between two modules are a sign that the architecture is forcing humans to do the work that an interface should be doing. The extra the report prints is domain coupling, from parts that still have to move together, plus coordination estimated from pull request timing, review rounds, and spread across repositories and authors.