Systems Thinking For Dev Organisations
summary
Overview of systems thinking applied to dev orgs with concrete methods: use stocks and flows and causal maps to spot feedback loops, distinguish balancing and reinforcing loops, and apply fixes that don’t undermine long‑term solutions. Examples include Romania’s 1967 Decree 770 (births spike then infant mortality rises 5–10×), a platform hack that bundles pinned microservices then flips a switch to full CI/CD, and remedies like quotas or privatization to avoid the tragedy of the commons. Tools mentioned: devpod, vcluster, devspace and the Kubernetes reconciliation loop.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker background
- 3:14Systems thinking and theory overview
- 13:03Systems archetypes and traps
- 19:26Fixes that fail and policy resistance
- 21:17Shifting the burden archetype
- 26:17Tragedy of the commons
- 29:25Applying systems thinking to platforms
- 32:54Book recommendations and closing
related talks
37mSystems Thinking for Dev Organisations - Lian Li
01h 25mA Systemic Approach to Organisation Design & Change Management
11mLeading software teams with systems thinking
01h 00mDev Culture Hacking and Org Refactoring Transformation tips from Software Pros
37mDevOps Topologies 10 years on: what have we learned about silos, collaboration...
53mHatching software development ecosystems (the gordian knot)
52mUnderstanding UnHealthy Syndromes of Software Delivery
18mBuilding Platforms, Breaking Code How Your Org Chart Can Support or Wreck Progress