Technical brilliance means nothing if you can't communicate it. Architects must translate between technical and business domains.
Know Your Audience
Executives:
- Business outcomes
- Risk and investment
- Strategic alignment
- 5-minute summary
Product Managers:
- Capabilities and timelines
- Trade-offs
- Dependencies
- User impact
Engineers:
- Technical details
- Rationale
- Implementation guidance
- Constraints
Visualization Techniques
A picture is worth a thousand words:
C4 Model Levels:
1. Context - System and users
2. Containers - Applications and data stores
3. Components - Internal structure
4. Code - Implementation details
Influencing Without Authority
Architects rarely have direct authority. Influence through:
- Building relationships
- Demonstrating competence
- Providing value
- Finding common ground
- Respecting expertise
Writing That Works
- Lead with the conclusion
- Use active voice
- Keep sentences short
- Include visuals
- Edit ruthlessly