Running Collaborative Domain-Driven Design (DDD) Mapping Sessions
Designed for Senior software engineers and solution architects tasked with leading cross-functional agile teams in building complex business systems to spark real collaboration and high-energy learning.
A 2-hour virtual session for agile teams distributed across multiple locations. Participants struggle to get business and technical people speaking a shared language, often leading to misaligned requirements, rework, and domain confusion. The session aims to demystify DDD mapping and give teams repeatable techniques to map their own domains collaboratively.
Mystery Model Reveal
Open with a blurred screenshot of a well-known but complex domain map (e.g., Spotify’s business architecture). Invite participants to guess what the map depicts and what problem it might have solved. Show the unblurred image and briefly explain the actual context.
Tap to view the full activity.
Why this works
Activates curiosity and primes participants’ brains for pattern recognition, making them eager to understand how such models are built.
Jargon-Busting Buzzer
Run a rapid-fire quiz: display 5 terms often misused in DDD (e.g., ‘Entity’, ‘Bounded Context’, ‘Aggregate’). Poll the group: does this term mean the same thing as in everyday tech, or does DDD have a twist? Debrief with the correct DDD meaning and why it matters.
Tap to view the full activity.
Why this works
Surfaces common misconceptions and ensures everyone starts with the same vocabulary, reducing friction in the main activity.
Silent Sticky Note Storm
Invite everyone to jot down, in silence, the most confusing processes or terms in their current project. Each person contributes 2-3 digital or physical sticky notes, which are then clustered in real time.
Tap to view the full activity.
Why this works
Creates a psychologically safe entry point by making participation anonymous and low-pressure, surfacing hidden challenges.
Boundary Blitz Breakout
Divide into small groups for a time-boxed challenge: given a fictional product (e.g., an online bookstore), each group draws a quick domain map with at least three bounded contexts. Groups then ‘pitch’ their maps to the whole room, justifying boundaries in 60 seconds.
Tap to view the full activity.
Why this works
Injects energy and teamwork; forces rapid iteration and debate, mirroring real-world mapping pressure.
Legacy System Dilemma
Present a brief case study: a real company attempted a DDD mapping session, but business and dev teams clashed over where one domain boundary should go, resulting in costly rework. Ask: ‘What would you do differently?’ Facilitate a quick group discussion.
Tap to view the full activity.
Why this works
Engages critical thinking and bridges theory to the messy realities of organizational politics and technical debt.
Personal Mapping Manifesto
Invite participants to craft a one-sentence “manifesto” about how they will change the way they approach mapping sessions, drawing on today’s learning. Volunteers can share for collective inspiration.
Tap to view the full activity.
Why this works
Promotes active reflection and personal ownership, increasing transfer from workshop to real-world behavior.
Sign up to unlock 3 more activities
Get the full pack, facilitation flow, and more ready-to-run ideas.