Review

Overall great read. I originally decided to read this looking for something more focused on system diagramming and system designing but I came away with something probably more valuable. The shift in thinking about systems from the perspective of “what do I build” to “what do I communicate” is probably my biggest take away. It’s about much more than using the right diagrams in the right place. It’s about building an ecosystem and culture around a shared knowledge. You may use diagrams and charts to communicate certain things but it’s the higher level “non-linear thinking” that really makes the larger impact.

While this book is written within the context of software development, it’s definitely something that anyone could pick up and come away with valuable insights around leadership, learning, modeling, and more.

Highlights

“Our thinking is influenced by code we’ve already delivered! Patterns of behavior in the software system impact the way people think about the software.”

“We cannot control our thinking, or other people’s thinking, but fortunately, systems thinking is not about gaining more control…it is about making better choices.”

“You need the friction that arises when your point of view bumps up against other points of view; that’s where you’ll discover conflicting mental models and positive opportunities for change. You need the support of collective practices that illuminate, rather than reinforce, your blind spots and biases.”

“Teams with a good process can use almost any tool to organize their work. Teams without a good process aren’t helped by any tool they might adopt.”