Systems Thinking

The article defines systems thinking as a way to understand how elements work together inside a system. It uses examples from bugs in software, team structure, mentoring, retrospectives, and climate to show that changing structure and understanding feedback loops can change outcomes.

Reading notes

#

• The ordinary way of solving a problem is an open loop, while systems thinking tries to close the loop by asking what caused the issue and how similar issues can be prevented.
• A system is a group of elements working together within boundaries and with a purpose.
• Systems thinking focuses on identifying the elements in a system and how they cooperate.
• A bathtub is used as the simplest example of a system, where inflow and outflow determine the water level.
• A stock is something that has memory in the system and can accumulate or decrease over time.
• Flows are changes that influence the stock.
• Feedback loops are closed chains of connections between flows.
• A balancing feedback loop maintains equilibrium.
• A reinforcing feedback loop leads to growth or decline.
• Structure generates behavior, and changing system behavior means changing its structure.
• Conway’s law is given as an example of how organizational communication structure shapes the systems teams design.
• Mentoring a junior engineer created a positive feedback loop that improved skills, client satisfaction, bug reduction, and time available for more mentoring.
• Retrospective sessions were used to learn from mistakes and improve the system.
• Systems thinking is presented as useful for understanding Earth’s limited resources and climate change.
• The article cites The Limits to Growth as a book that connected exponential growth with negative feedback effects on the planet.