Communication Patterns: A Guide for Developers and Architects
Authors: Jacqui Read
Publisher: O'Reilly Media
Length: 2024
Jacqui Read's patterns for visual, written, verbal, knowledge-transfer, and remote communication for developers and architects.
Original
TranslationBrief
The essential idea
Jacqui Read's Communication Patterns treats communication as an engineering capability that can be designed through reusable patterns and explicit antipatterns. Its four parts cover visual communication, written and verbal rhetoric, communicating knowledge through durable artifacts and rituals, and remote communication protocols for asynchronous teams.
The practical patterns start with audience and context, make documents decision-oriented, standardize diagram legends and notation, define asynchronous response and escalation contracts, create recurring knowledge handoffs, and make accessibility a default. Together they reduce the cost of aligning complex decisions across people with different expertise, time zones, and responsibilities.
Decision lens
Key takeaways
Engineering communication should be deliberately designed rather than left to individual habit.
Audience, context, and expected depth should be decided before creating a document or diagram.
Decision-oriented writing makes the outcome, owner, risks, and next steps easy to find.
Knowledge persists through ADRs, reviews, walkthroughs, and debriefs, not through an ownerless wiki archive.
Remote communication needs explicit channels, response SLAs, escalation rules, and a path from chat to durable records.
Contrast, readability, legends, and non-color-only encoding are part of communication quality.
Narrative-free diagrams, unstructured long text, and a single channel for every purpose are recurring antipatterns.
Workplace experiment
Apply it at work
- 1
Adopt a design-document template with context, options, trade-offs, decision, risks, owner, and next steps.
- 2
Add a minimal legend and notation policy to the team's important architecture diagrams.
- 3
Separate channels for decisions, announcements, discussion, and incidents, with response and escalation expectations.
- 4
Run a weekly thirty-minute knowledge-handoff ritual and convert recurring verbal agreements into durable artifacts.
- 5
After thirty days, review where context still disappears and update the communication contract from evidence.
Choose one action, define the observable effect, and keep the first test small enough to reverse.
Evidence
Sources and further reading
Additional sources
Channel, aggregator, and commentary links confirm the work; they are not the primary source.