Don't Hit the Iceberg

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.

Previous

Systems Thinking for Software Professionals

Next

Modern Agility