Systems are communication structures -
summary
Explains how large content platforms (examples: The Economist, Wikimedia, Drupal-era sites) break down into recurring low-level patterns that dictate architecture, and argues emergence comes from practiced collective reasoning not top-down control. Covers concrete tactics: form claims with explicit reasons, spot six common logical fallacies, use informal logic and top-down elaboration templates, define terms before designing, and prefer encapsulation over full rewrites. Also links cognitive practices — conceptual integrity, yes-and culture — to team modernization and measurable reduction of recurring design failures.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 5:45What is an architect
- 9:49Rules of emergence
- 11:48Uncertainty
- 12:43Interact without central
- 14:34Emergent systems dependent
- 16:00Art of ambiguity
- 17:52Making claims
- 21:26The umbrella example
- 25:03Does it matter
- 26:36Collective reasoning
- 28:33No culture
- 30:28Define everything
- 34:30Conceptual fallacies
- 39:01Selfawareness
- 44:02Empathy
- 44:41Energy
- 46:17Food
- 50:24Questions
related talks
30mIt's About Systems
40mSystems Thinking for Developers
52mFrom Code to Complexity: Shifting to Systems Thinking in Software Development
22mDesign Systems are Dead. Long Live Design Systems – Luke Murphy
49mArchitecture is Designing Knowledge Flow
30mCommunicating design systems
36mThe human factor you might be missing when designing your system
01h 01mDesigning for complexity