Remember the last time you built or created something and felt genuinely proud of it? Chances are, you understood it deeply. And you built it with people who did too.

Great software has a story behind it. A shared one. Today, AI accelerates execution. But it cannot generate the thinking and caring together that keep the shared story alive. You can feel when that story is missing. As code becomes cheap, meaning becomes expensive.

This is the ground AI-accelerated teams are losing. Two risks are compounding:

• Cognitive risk: velocity outpacing shared understanding
• Identity risk: shipping systems we have prompted, but don’t feel connected to

This masterclass is about reclaiming that ground. Domain-Driven Design, practiced as a sociotechnical discipline, is one of the most powerful tools available for designing shared understanding and keeping it alive. In the age of AI, thinking together is the edge. DDD has never mattered more.

Over two days, you’ll learn the strategic core of DDD from someone with more than a decade of experience using it to decouple software and connect people in complex environments. Hands-on, analog, and in conversation — the way shared understanding actually gets built.

Who Is It For?

Developers, architects, tech leads, product managers, UX designers, business analysts.

Anyone who has felt the gap between what a system does and how well it’s actually understood.

What You’ll Walk Away With

You will be able to:

• Know when to slow down to discover the domain before speeding up execution
• Use conversation as a design tool: surface what’s assumed, challenged, or missing in old and new code
• Design systems with clear intention and boundaries: from core domain to context mapping
• Apply Ubiquitous Language to keep shared understanding alive
• Walk away with a lived experience of DDD by thinking and modeling together, not just learning the theory

Day 1: Thinking Together

Day 1 is about foundational skills. You start with a real domain and model it together from scratch.

• Languaging: Name complexity in problem, solution and possibility space
• Modeling: Discover the domain through conversation, events and user needs mapping
• Connecting: Design Bounded Contexts around where your work and the rest of the system intersect

Day 2: Design at Scale

Day 2 is about strategic clarity. You take what you built on Day 1 and make larger-scale design decisions with it.

• Core Domain Strategy: Prioritize a large domain landscape and make trade-offs explicit
• Context Mapping: Map how systems and teams relate, depend, and conflict
• DDD+AI: Add Continuous Comprehension (CC) to the CI/CD mix in AI-assisted software development

Both days: sticky notes, shared walls, making the implicit explicit.

Prerequisites

Experience working with software in teams and curiosity about what the future of software development asks of us.