Alerts — TeamWeaver

concern hub_and_spoke

Communication is heavily routed through 1 of 6 members. 73% of cross-functional messages flow through a single node.

Recommendation: Introduce a rotating 'liaison' role for cross-team coordination. Start with sprint planning — have a different team member represent Engineering each sprint.

concern isolated_network

Data Science

Cross-team communication ratio has dropped to 8% from 19% over the past 6 weeks. Topic overlap with Engineering has declined significantly.

Recommendation: Schedule bi-weekly 'show and tell' sessions where Data Science presents work-in-progress to Engineering. Pair a data scientist with an engineer on the next cross-functional project.

watch disenfranchised_nodes

Engineering

2 members have contributed less than 5% of total team communication over the past 4 weeks, down from 12% previously.

Recommendation: Create structured opportunities for input — round-robin in standups, async RFC documents where everyone comments before decisions are made.

watch priority_overload

Product

Team is responding to requests from 4 other teams while maintaining internal deliverables. Meeting load is 14.2 hours/person/week.

Recommendation: Establish 'office hours' — designated times when other teams can bring requests. This consolidates interruptions and protects focused work time.