Into the World of Systems Thinking: For Software Engineers Who Keep Thinking in an Increasingly Complex Era is a book I read.
It is written from the perspective of how software engineers can bring systems thinking into their own work.
Rather than being a textbook on systems thinking itself, it reads as an entry point for engineers dealing with increasingly complex software, organizations, and societies, encouraging them to look at overall structures and interactions instead of relying solely on a reductionist view.
It introduces the basic tools of systems thinking — stocks and flows, feedback loops, delays, and leverage points — while connecting them to phenomena that occur in software development and organizations.
It is better read as a book for cultivating the perspective of "seeing what is in front of you as a structure" than as a book for memorizing a specific framework.
Three points left an impression on me:
- It repeatedly presents the view of capturing things as circular structures rather than linear cause-and-effect
- It introduces the idea of looking at "things that don't go well" — bugs, incidents, organizational dysfunction — from the structure of the system rather than from individual responsibility
- The discussion of leverage points, where interventions that seem effective in the short term can backfire over the long term, was particularly interesting
Because it is more about aligning the underlying OS of how we think than providing concrete procedures, I felt it pairs well with roles such as architects, engineering managers, and tech leads who deal with "structures behind individual phenomena."
It is a book that reminds you to focus on structure rather than symptoms when dealing with problems in organizations and systems.
