Panel about system thinking, complexity thinking
summary
Panel argues whether design tools or science wins: systems dynamics and cybernetics work inside constrained, engineered settings (Toyota, manufacturing) while complexity science demands scaffolding for emergence and rejects linear root cause; a Google outage case shows failure can stem from concurrent physical events not single causes; they cite simulations and agent-based models, propose measuring organizational abductive capability, and push for narrative methods that scale as micro-narrative at scale rather than retrospective root-cause fixes.
AI-written summary · about
chapters (7)
- 0:00Panel introduction
- 0:31Systems vs complexity thinking
- 8:11Reductionism and root causes
- 20:24Emergent systems in complexity
- 27:05Ashby’s law and requisite variety
- 33:48Diversity and epistemic justice
- 37:19AI’s impact on complexity
related talks
54mSystems Thinking
40mSystems Thinking for Developers
52mPanel Discussion «Is it true that "The best architectures emerge from self-organized teams"»?
43mThe Unbearable Stupidity of Social Sciences
49mManaging in Complexity (and chaos)
41mA Modular Compositional Approach to Engineering Complex Systems
49mSystems Thinking and the Art of Simplification -
52mFrom Code to Complexity: Shifting to Systems Thinking in Software Development