Skip to content
Arquitetura de Software — Study

Part III — Techniques & Soft Skills

Chapter 25 — Negotiation and Leadership Skills

Core ideas

  • Architects constantly negotiate with business stakeholders, other architects, and developers — each requires a different tactic.
  • Techniques: gather info and leverage grammar/keywords (“always,” “never,” “impossible” signal soft spots); use “divide and conquer” to scope demands; lead with the business justification; save the “why” as a closing argument; when conflict escalates, calm and demonstrate (build a prototype/proof rather than argue).
  • The 4 C’s of architecture leadership: Communication, Collaboration, Clarity, Conciseness. Lead by example, not title; be pragmatic yet visionary; be present (skip unnecessary meetings, but be available). “The 20-minute rule” for staying current; integrating with the dev team.

Trade-offs to argue

Negotiation is trade-off analysis applied to people: winning every point costs relationships; conceding everything costs the architecture. Find the least-worst human outcome.

Self-check

0/3 answered