Learning Systems Thinking • Diana Montalion & Charles Humble • GOTO 2024

Systems thinking requires examining and improving both individual and group thinking patterns, moving beyond just technical solutions

Knowledge flow (ability to generate and share new knowledge) is more valuable than knowledge stock (accumulated expertise) in modern software organizations

Counter-intuitiveness is a key concept - the obvious solution often makes systemic problems worse due to complex relationships between parts

Microservices and distributed systems require non-linear thinking and understanding relationships between components, not just technical decoupling

Effective systems thinking requires:

• Metacognition (thinking about thinking)
• Comfort with uncertainty
• Willingness to examine biases
• Ability to synthesize diverse perspectives

Success comes more from enabling knowledge flow and building conceptual integrity than individual technical expertise

Organizations need to move beyond reductionist thinking and template solutions to understand root causes and system dynamics

Systems thinking helps identify leverage points - places where small changes can produce big impacts

Linear/reductionist thinking and systems thinking are complementary - both are needed but must be applied appropriately

Changing organizational thinking patterns and communication is as important as changing technology for solving systemic problems