Architecture spans multiple functions. Architects coordinate.
Counterparts:
1. IT operations.
- Network, infrastructure, identity teams.
- Architect engages on: SSO, MFA, integration network paths, infrastructure decisions.
2. Security.
- CISO, security architects, security operations.
- Engages on: threat modeling, encryption, audit requirements, incident response.
- Frequent collaboration; sometimes contentious.
3. Compliance / Legal.
- Compliance officers, privacy officers, legal counsel.
- Engages on: GDPR, HIPAA, regulatory requirements, contracts.
4. Business stakeholders.
- Department heads, line-of-business leaders.
- Engages on: requirements, priorities, change management.
5. Other architects.
- Enterprise Architects, Solution Architects from other domains.
- Engages on: standards alignment, cross-platform integration.
6. External vendors.
- Salesforce account team, AppExchange ISVs, consulting firms, integration partners.
- Engages on: roadmap, support, contracts, technical issues.
Patterns:
Working with security:
- Engage early. Don't surprise them late in design.
- Speak their language: threats, controls, audit.
- Acknowledge their concerns; address with technical solutions.
- Document decisions for audit.
Working with compliance:
- Translate regulations into technical requirements.
- Document compliance posture.
- Plan for audits.
Working with business:
- Translate business goals into technical requirements.
- Translate technical constraints into business trade-offs.
- Balance ambition with pragmatism.
Working with vendors:
- Build relationships beyond transactional.
- Provide feedback they value.
- Anticipate roadmap.
Common pitfalls:
- Silo-ing — each function in isolation.
- Avoiding security — security pushed to end; rework.
- Vendor over-reliance — vendors solve problems instead of internal team learning.
- Stakeholder fatigue — too many meetings; not enough decisions.
Senior insight: architects are integrators of teams as much as systems. Cross-functional success isn't a soft skill; it's central to architecture work.
Influence patterns:
- Listen first — understand each function's concerns.
- Find common ground — most disputes have shared underlying interests.
- Document decisions — future-proof against re-litigation.
- Build coalition — pre-align supporters before formal decisions.
The senior framing: technical excellence without organisational alignment fails. Architects who excel technically but politically fail produce great designs that don't ship.
The most senior architects are deeply technical AND deeply organisational. Both. Hard to develop, valuable when you do.