alexe-ev Align Cross-Team Communication
Purpose
Help teams design effective communication systems that maintain alignment across product, engineering, design, and business stakeholders without creating overhead.
Skill type
Conceptual skill
Use this skill when
- Teams are working in silos and discovering misalignment late
- Engineering builds the wrong thing because product communication is unclear
- Stakeholders are surprised by product decisions or status
- A new cross-functional team needs communication norms established
Do not use this skill when
- The goal is executive communication and narrative (use build-executive-narrative)
- The goal is operating cadence design (use design-operating-cadence)
Required inputs
- Teams involved in cross-functional work
- Current communication pain points or failure modes
Optional inputs
- Current communication channels and tools
- Stakeholder types and needs
- Meeting cadence
Upstream context
Works best when:
- Operating cadence is designed
- Team structure is clear
Downstream handoff
Output can feed:
- design-team-rituals
- manage-tooling-documentation
Instructions
- Map all cross-team communication flows: who needs what information, how often, in what format.
- Identify current breakdown points (where misalignment happens most).
- Design synchronous and async communication channels for each flow.
- Define norms for decision communication: who is informed, consulted, and accountable.
- Design status update and escalation protocols.
- Define feedback loops back to product from engineering and design.
Output
Provide:
- Communication flow map (who needs what, when, how)
- Current breakdown points
- Recommended communication channels by type
- Decision communication norms (RACI or similar)
- Status update and escalation protocol
- Feedback loop design from engineering/design to product
Risks / caveats
- More communication channels is not better alignment — reduce noise, increase signal
- Decisions that aren't communicated still need to be justified — design for transparency
- Async-first works well but requires strong written communication norms