Optimise your team structure
using the evidence in your commits

What it measures

• Change CouplingModules modified together in the same commits — a hidden dependency that static analysis cannot see because it emerges from behaviour, not code structure.
• Cross-Team Coupling RiskWhen coupled modules belong to different teams, every shared commit is a coordination event. This view makes the overhead measurable — in numbers, not in anecdotes.
• Coupling DirectionMeasures whether coupling is symmetric or asymmetric — revealing which module drives the dependency and which follows.
• Team AlignmentCombines coupling, ownership, and team data into a quantitative basis for restructuring decisions — previously days of manual work, now automated.
• Ownership Drift TimelineStacked area chart showing how each team's share of a module shifted quarter by quarter — makes Conway's Law drift visible before it becomes an incident.

When to use it