Architecture: The Absence of Self-Organisation
summary
Argues that self-organization is ubiquitous but architecture intentionally limits it: an architecture is a boundary that steers local interactions toward a desired outcome rather than pure emergence. Uses an hourglass, Berlin Hauptbahnhof crowds and Vienna building contrasts (consistent façades vs Hundertwasser individuality) to show when rules must be stronger. Claims the best long-lived systems come from teams that craft rules and structures, not from laissez-faire emergence, and proposes three actionable principles: principle of responsibility, principle of empowerment, principle of agency.
AI-written summary · about
chapters (10)
- 0:00Introduction and context
- 4:05Self-organization dynamics
- 8:08The hourglass model
- 11:51Intentional structures
- 14:58Architecture as limitation
- 18:58Architectural styles
- 21:19Rules and team performance
- 24:10Demanding self-organization
- 26:26Architectural principles
- 32:35Q&A and conclusion
related talks
51mSoftware Architecture for Humans!
46mTHE too MANY FACES OF ARCHITECTURE
25mThe (too) Many Faces of Architecture
27mSoftware Architects and Autonomous Teams
48mArchitecture: The Stuff That's Hard to Change
24mThe (too) Many Faces of Architecture
45mArchitecture: The Stuff That's Hard to Change
44mDeliberate Architecture