This session goes into techniques to either help teams realign their architecture with their product needs or set up the appropriate modularity to start.

We go over what strategic DDD is, why it is interesting / what problems it solves, and then go through an example with an organization with a 20year old product that evolved from 1 team to 14 teams (all while shipping less frequently) - and how DDD changed that.

From there we introduce C4 modeling in the context of product. This allows a consistent goal of the product while giving the appropriate freedom for team / modularity architecture as well as integration patters. We also address how archtiecture affects planning.

Lastly, we wrap up with architectural decision records for teams to keep track of the context and tradeoffs of their decisions.


Systems grow and change over time. You can have intentional design, or accidental design.

In this session we will walk through approaches that leverage product context to keep architecture aligned with the needs of the product. We will look at strategic DDD, C4 modeling, and architecture decision records.

Leave this session with simple techniques that you can apply immediately to start blending product with architecture.