Learning Systems Thinking

(Full-day workshop) A decade ago, developers built information-sharing software by writing a lot of custom code in a single code base, then adding layers of caching. Now we build information systems: interdependent software and services, data platforms, and event streams.

Many of our software-to-systems initiatives fail, though, and when they do, we double down on traditional linear approaches. But linear thinking cannot resolve systems challenges. We need to shift to systems thinking.

This workshop shows software developers and architects how systems thinking is a much-needed skill, given the emerging complexity of modern systems. Nonlinear approaches to technology architecture can transform how we learn, communicate, and collaborate with others.

Through hands-on exercises and real-world scenarios, you'll learn how to develop critical self-reflection and decision-making skill, model systems thinking and thrive amid complexity and uncertainty. Regardless of your role, these skills will help you lead impactful cultural change within your organization.

You'll learn:

- How linear thinking limits your perspective on software systems

- The obstacles to changing your perspective and how to move past them

- How systems and nonlinear thinking help you understand and navigate complex issues arising from internal and external factors

- Methods for creating sound, cross-functional recommendations in the midst of complexity and uncertainty

- How nonlinear approaches improve the quality of architectural thinking and deliver impactful change for organizations

- How writing, thinking and modeling are deep, impactful architecture practices

- How to provide a modern style of leadership as software becomes information systems

Don’t Hit the Iceberg

(Closing Keynote) A decade ago, developers built information-sharing software by writing a lot of custom code in a single code base, then adding layers of caching. Now we build information systems: interdependent software and services, data platforms, and event streams.

In systems thinking circles, a common model is The Iceberg. At the top, visible above the waterline, are the things that happen. Events (like bugs and outages) and patterns that reinforce them. At the bottom, down deep, are our mental models -- the concepts we draw from when we build software systems.

I've seen many software-to-systems (aka "digital transformation") initiatives fail. They hit this Iceberg and sink spectacularly. What do we do when that happens? We double down on our traditional approaches.

Real transformation can only happen when we go deep into the structures of our collective thinking. Architecture, in the systems age, is not just Kubernetes. It is engaging our mental models and working together to transform them.

Our thinking designs our architecture. Scaling up our linear thinking cannot resolve systems challenges. We need to shift to systems thinking.