Overview of each of the 12 modules, including the transformations, practices, cohort activities and lessons.. Also includes the related book groups with brief summaries. Grouped by Cohorts to help you decide whether to join one.

Start with Why: Start with why to avoid erroneous leaps in logic and recommend matterful technology change.

Logical fallacies: As knowledge workers, we rely on reasoning to recommend an action and build things. A logical fallacy is a flaw in reasoning.

Noticing our reactions: Learning to respond is an essential systems-thinking skill. It begins with noticing our reactions.

There's a lot happening in 2023! Here are some events, experiences and books to enjoy.

Power and control can be nice to have but what we need most is … time to think.

Information designed to fit software logic must now be restructured to serve emergent consumer logic.

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

After nearly 20 years, here are five things I’ve learned about (information) systems.

We build technology by developing the people who can design, deliver and maintain that technology.

Events are the way a system communication that something matterful has changed.

Where once there were events, now there are flows of data published continuously.

As complexity increases, more software parts act as a source of information -- with layers that govern communication.

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

Exploring how to draw boundaries around software parts. How do you figure out what to decouple from what?

Exploring patterns for forming new relationships between decoupled parts.

Deep schisms in a system's functional architecture appear when people can't create shared understanding. Collaborative modeling helps.

Moving from monolith to microservices is an incremental decoupling of capabilities. And a mindshift from code thinking to designing well-architected relationships.

DevOps is a restructuring of the way an organization thinks, behaves and cross-functionally delivers software.

If you want to change what you deploy, you first need to change how you think. You can not change your thinking if you aren't aware of your thinking.