Browse Editions

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.

Systems thinking practices that will help you make impactful changes -- despite the emerging complexity of modern systems.

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 this workshop, you’ll understand how interrelated and interdependent parts (in people and software) act together to create patterns Through hands-on exercises and a real-world scenario, you'll You’ll learn to create conceptual models to guide impactful decisions.

In this workshop, you’ll understand how interrelated and interdependent parts (in people and software) act together to create patterns Through hands-on exercises and a real-world scenario, you'll You’ll learn to create conceptual models to guide impactful decisions.

A two-day, hands-on Masterclass exploring systems thinking practices. As the relational complexity of our software systems increases, our traditional, linear thinking approaches are insufficient. Software professionals, especially those building interdependent software and services need to think in systems.

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.

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.

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.