Core Idea
When negotiating with other architects, focus on data, shared architectural principles, and common goals rather than opinions or positional authority, as technical peers respond best to evidence-based reasoning.
Context: Architects frequently negotiate with enterprise architects, domain architects, and peer application architects. Unlike discussions with business stakeholders or developers, these involve technical peers with strong, well-reasoned opinions that may conflict with yours.
Key to Success - Data-Driven Discussion: Other architects respond to empirical evidence, performance metrics, and historical precedent:
- Ineffective: “I think microservices are better”
- Effective: “Our transaction volume of 500/second doesn’t justify the operational overhead of microservices, as shown by this performance analysis”
Use Shared Architectural Principles: Most architects share values like simplicity, maintainability, and scalability:
- Frame your position in terms of these shared principles
- Example: “This design follows the Single Responsibility Principle we’ve both advocated for, reducing coupling and improving testability”
Avoid Positional Authority:
- Don’t say “I’m the senior architect, so we’ll do it my way”—this destroys trust
- Reference authoritative sources as supporting evidence within a larger argument, not as conversation-ending appeals to authority
Focus on Common Goals: Both architects want the system to succeed, meet requirements, and be maintainable:
- When disagreements arise, return to shared objectives
- Explicitly acknowledge that your proposed solution has downsides—intellectual honesty creates space for collaborative problem-solving rather than adversarial debate
Why This Matters
Organizational Impact: Architect-to-architect disagreements can paralyze decisions and create organizational friction:
- Poor negotiation leads to compromise solutions that satisfy no one, or entrenched positions where ego trumps engineering
- Data-driven, principle-based negotiation maintains professional relationships and reaches decisions grounded in evidence
Career Implications: In matrix organizations or large enterprises, architects must frequently align decisions across domains and product lines. Effective peer negotiation is essential for career advancement and organizational impact.
Related Concepts
- Negotiation-Facilitation-Skills — foundational negotiation approaches for architects
- Negotiating-with-Business-Stakeholders — contrasting approach for non-technical stakeholders
- Architecturally-Significant-Decisions — what decisions warrant architect-level negotiation
- Architecture-Decision-Records — documenting outcomes of architectural negotiations
- Architecture-Decision-Anti-Patterns — common failures in decision-making processes
- Team-Boundaries — organizational context where architect negotiations occur
Sources
- Richards, Mark and Neal Ford (2020). Fundamentals of Software Architecture: An Engineering Approach. O’Reilly Media. ISBN: 978-1-492-04345-4.
- Chapter 23: Negotiation and Leadership Skills, pp. 341-356
- Available: https://www.oreilly.com/library/view/fundamentals-of-software/9781492043447/
Note
This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.