21 people, 4 teams. They adopted AI tools across the organization 3 months ago. Leadership is excited. Individual output is up. But something isn't adding up.
+21%
Code commits, PRs, messages per person
0%
Features shipped, cycle time, goals hit
5
Behavioral signals that need attention
Everyone is producing more. But the team isn't moving faster.
TeamWeaver connected to Meridian's Slack, GitHub, and Google Calendar. No surveys, no extra work. Here's what the communication patterns revealed.
As AI content rises, participation and cognitive diversity decline. Six weeks of data.
Engineering stands out. Red across participation, cognitive diversity, and response speed.
Sarah manages Engineering. This landed in her inbox before standup.
Here's what needs your attention on Engineering, Sarah.
Participation has declined 34% over 4 weeks. Two members haven't initiated a discussion in 12 days. Response latency up 2.3x.
Have 1:1 conversations focused on workload, not output. Consider redistributing the AI tooling migration that landed primarily on these two members.
78% of cross-functional messages flow through a single team member. Information bottleneck risk is elevated.
Introduce a rotating liaison role for cross-team coordination. Start with sprint planning.
AI-generated content rate is 31%. Cognitive diversity dropped to 0.38 and question frequency is down 45%.
Institute a 'challenge round' in design reviews where AI-generated proposals must be questioned before adoption.