get the newsletter

Design and Deliver Impactful Systems

Architecting Systems

Featured Posts

Find more »

Read articles to get a feel for Architecting Systems

Emergence

Emergence

Emergence is a process, the ways simple interactions among individual parts form more-complex behaviors and patterns.

Communication Patterns - Intro

Communication Patterns - Intro

As we move from software to systems of software, time and relationship is where complexity increases at breakneck speed.

Nonlinear Thinking

Nonlinear Thinking

Exploring nonlinear thinking and approaches from experienced systems thinkers working inside, and outside, technology.

Architecting Systems

Design and Deliver Impactful Systems

Develop the skills you need in an increasingly-complex world. Skills that help you think outside the software box and build knowledge systems.

    We won't share your data with anyone, ever. Unsubscribe at any time.

    Recent Editions

    Find more »

    Read articles that are available to free subscribers

    Welcome

    Welcome

    Architecting Systems is not (just) a newsletter -- it's a digital ecosystem of systems thinking tools and practices.

    Architecture is Designing Knowledge Flow -- SAG

    Architecture is Designing Knowledge Flow -- SAG

    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 isn't Kubernetes -- NDC London

    Architecture isn't Kubernetes -- NDC London

    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.

    Masterclass in Systems Thinking -- goto

    Masterclass in Systems Thinking -- goto

    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 isn't Kubernetes -- JaxNY

    Architecture isn't Kubernetes -- JaxNY

    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.

    school of systems

    Join the Community

    Want to dive into learning, right now? Join the community of systems explorers.

    The Systems Library

    Learning Resources for Systems Thinkers

    Nonlinear skills, practices and approaches for technology professionals building knowledge systems. Recommend your favorites!

    Collections & Types

    Articles, talks, books, podcasts, courses and more ... organized by themes and practices that nourish and support systems thinking and design.

    Discover Experts

    Browse resources published by systems experts and find more perspectives to support your learning practice.

    SoftwareCrafters Collective

    Contribute Your Insight

    Converse with other technologists faced with increasing complexity. We learn from each other while practicing the art and science of systems design.

    Take Courses

    Courses on demand and real-time cohort courses that improve our skills and strengthen our practice.

    Practice Together

    Informal groups to support a specific practice, like daily writing or pitching your ideas.

    New Book

    Essential Skills and Practices for Software Professionals

    Learning Systems Thinking Book

    I keynote at technology events, as well as develop onsite, remote and custom workshops. Here are some upcoming events.

    Architecture is Designing Knowledge Flow -- SAG

    Architecture is Designing Knowledge Flow -- SAG

    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 isn't Kubernetes -- NDC London

    Architecture isn't Kubernetes -- NDC London

    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.

    Masterclass in Systems Thinking -- goto

    Masterclass in Systems Thinking -- goto

    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 isn't Kubernetes -- JaxNY

    Architecture isn't Kubernetes -- JaxNY

    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 isn't Kubernetes -- wJaxDE

    Architecture isn't Kubernetes -- wJaxDE

    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 isn't Kubernetes -- goto CPH

    Architecture isn't Kubernetes -- goto CPH

    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.