liveBook · Manning

Communication

As explained in Software Architecture Decision-Making

Architectural communication is the deliberate exchange of architectural intent, decisions, trade-offs, and consequences among people involved in a system.

Architectural communication turns intent into architecture that people understand, trust, and can act on. A decision kept in the architect’s head remains unrealized. section 1.5

Communication connects partial views without pretending they are identical. Stakeholders express outcomes and pressure; developers see code and constraints; operations focus on supportability and recovery; security weighs exposure and control; finance weighs cost. section 1.5

Effective architectural communication makes shared consequences visible while preserving delivery reality:

  • Translate business goals into technical direction and explain technical limitations as cost, risk, or future limitation. section 1.5
  • Explain trade-offs clearly enough for the organization to understand what it is accepting. section 1.5
  • Involve security and operations early so their concerns do not become late-stage blockers. section 1.5
  • Work horizontally to expose duplicated work, compare approaches, and detect system-wide consequences without controlling every design decision. section 1.5

Trust is the operating condition: developers must see architectural direction as grounded in delivery reality, while stakeholders must recognize technical concerns as signals rather than excuses. Feedback then supports continued protection of coherence and adaptation. section 1.5 section 1.8

How Software Architecture Decision-Making covers it

How deep it goes
Explains stakeholder translation, trust, and coordination, but does not prescribe detailed communication techniques.
Examples
Uses differing stakeholder views and retry logic as concrete illustrations of communication’s architectural role.
What you can do after
Apply communication to translate goals, limitations, risks, and trade-offs into shared architectural direction.
How it connects
Connects stakeholders, developers, operations, security, finance, trade-offs, trust, and feedback.

Also explained in

Compare how 9 books explain communication →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Software Architecture Decision-Making. The section links point to the parts of the book it draws on.