Making Time for Thinking
Power and control can be nice to have but what we need most is … time to think.
Read articles to get a feel for Architecting Systems
Power and control can be nice to have but what we need most is … time to think.
Diana Montalion shares why traditional software approaches fall short in today’s complex systems—and how systems thinking offers a better path forward.
To build truly large software systems, you need to see beyond the code. In this episode of Developer Voices, Diana Montalion, author of Learning Systems Thinking, explores how understanding systems—including people, priorities, and processes—can help developers design better, more adaptive software.
A live discussion on systems thinking, nonlinear skills, and software resilience
Interview at GOTO 2024 discusses systems thinking in software architecture and how effective knowledge flow shapes organizational dynamics and team performance.
Learning to respond is an essential systems-thinking skill. It begins with noticing our reactions.
Read articles that are available to free subscribers
Architecting Systems is not (just) a newsletter -- it's a digital ecosystem of systems thinking tools and practices.
Power and control can be nice to have but what we need most is … time to think.
Diana Montalion shares why traditional software approaches fall short in today’s complex systems—and how systems thinking offers a better path forward.
To build truly large software systems, you need to see beyond the code. In this episode of Developer Voices, Diana Montalion, author of Learning Systems Thinking, explores how understanding systems—including people, priorities, and processes—can help developers design better, more adaptive software.
In the tech industry, we are most interested in knowledge stock: What do you know? What information can you apply easily? Whiteboard tests, for example, assess a candidate's stock of knowledge.
This hands-on workshop introduces essential non-linear skills and practices for software professionals.
Keynote discusses the increasing relational complexity in software and emphasizes three essential qualities of well-functioning systems: resilience, self-organization, and hierarchy, which challenge traditional thinking and promote better outcomes through collaboration with the system's inherent properties.
The tech industry needs to shift from focusing on individual knowledge stock to fostering knowledge flow to make better decisions amidst change. This involves understanding the differences between data, information, knowledge, understanding, and wisdom, and recognizing the importance of developing knowledge systems as a core architectural practice.
In the tech industry, we are most interested in knowledge stock: What do you know? This focus is holding many individuals, teams and organizations back. As relational complexity increases, individual knowledge stock is insufficient. What we need is knowledge flow.
school of systems
Want to dive into learning, right now? Join the community of systems explorers.
Nonlinear skills, practices and approaches for technology professionals building knowledge systems. Recommend your favorites!
Articles, talks, books, podcasts, courses and more ... organized by themes and practices that nourish and support systems thinking and design.
Browse resources published by systems experts and find more perspectives to support your learning practice.
Converse with other technologists faced with increasing complexity. We learn from each other while practicing the art and science of systems design.
Courses on demand and real-time cohort courses that improve our skills and strengthen our practice.
Informal groups to support a specific practice, like daily writing or pitching your ideas.
I keynote at technology events, as well as develop onsite, remote and custom workshops. Here are some upcoming events.
In the tech industry, we are most interested in knowledge stock: What do you know? What information can you apply easily? Whiteboard tests, for example, assess a candidate's stock of knowledge.
This hands-on workshop introduces essential non-linear skills and practices for software professionals.
Keynote discusses the increasing relational complexity in software and emphasizes three essential qualities of well-functioning systems: resilience, self-organization, and hierarchy, which challenge traditional thinking and promote better outcomes through collaboration with the system's inherent properties.
The tech industry needs to shift from focusing on individual knowledge stock to fostering knowledge flow to make better decisions amidst change. This involves understanding the differences between data, information, knowledge, understanding, and wisdom, and recognizing the importance of developing knowledge systems as a core architectural practice.
In the tech industry, we are most interested in knowledge stock: What do you know? This focus is holding many individuals, teams and organizations back. As relational complexity increases, individual knowledge stock is insufficient. What we need is knowledge flow.
In the tech industry, we are most interested in knowledge stock: What do you know? This focus is holding many individuals, teams and organizations back. As relational complexity increases, individual knowledge stock is insufficient. What we need is knowledge flow.
Architecture, in the systems age, is not (just) Kubernetes. It is is designing relationships between parts (people and tech parts) then adapting those relationship patterns as circumstances change.
In my lifetime, we have experienced the equivalent of 20,000 years of change. Nonlinear change. In many respects, we are the architects of change, yet we seem to do the same things again and again, expecting different results.
Systems thinking practices that will help you make impactful changes -- despite the emerging complexity of modern systems.