Architecture programs need explicit communication strategy. Without it, work happens in silos.
Audiences:
- Executives — strategic direction, ROI.
- Business stakeholders — what's coming, when, how it affects them.
- Architects (across teams) — alignment, sharing.
- Engineers — standards, decisions, mentorship.
- Vendors — requirements, feedback, partnership.
Channels:
1. Quarterly Business Reviews (QBRs).
For executives + senior business. Roadmap, KPIs, decisions needed.
2. Architecture Review Board.
Bi-weekly / weekly. Decisions on significant architecture changes.
3. Architects' guild / community of practice.
Monthly. Architects across teams. Standards, learnings, roadmap.
4. Engineering all-hands.
Quarterly. All engineers + architects. Strategic context, important changes.
5. Internal newsletter.
Monthly. Architecture updates, success stories, deprecations announced.
6. Documentation hub.
Confluence / similar. Persistent, searchable.
7. Slack / Teams channels.
- #architecture-team — internal.
- #architecture-public — broader audience.
- Per-project channels.
8. ADR / decision log.
Significant decisions captured persistently.
9. Roadmap review.
Quarterly. Where we are, where we're going.
10. Vendor communication.
Quarterly business reviews with each vendor.
Communication patterns:
- Asynchronous default — written, persistent.
- Synchronous when needed — meetings for decisions, alignment.
- Visual — diagrams over walls of text.
- Concise — respect attention.
Senior insight: architecture without communication is theatre. Decisions made in private don't propagate.
The senior framing: communicating is part of architecting. Allocate 15-20% of architect time to communication. Without that, decisions don't land.