Organisation
Strategic Domain-Driven Design
Align software with the business: discover the domain together, draw clear boundaries and connect every deliverable to an impact.
- Indicative duration
- 2 to 3 days
- Level
- Intermediate
- Delivery
- On-site · Remote · Hybrid
- Formats
- In-house
- Open session
- Coaching / mentoring
- Talk / masterclass
Expected outcomes for your teams and business
What the training concretely changes, beyond the classroom:
-
Investment where it differentiates
Your best people work on the core domain; generic needs are bought or simplified.
-
Business and tech aligned
A shared language cuts misunderstandings, rework and features built on wrong assumptions.
-
Teams that move independently
Clear boundaries reduce coordination overhead and cross-team dependencies.
-
A roadmap tied to measurable impact
Every deliverable connects to a business goal, so fewer features ship that nobody uses.
Learning objectives
By the end of the course, participants will be able to:
- Distinguish core, supporting and generic subdomains and invest accordingly
- Build a ubiquitous language shared by business and tech
- Identify bounded contexts and map their relationships
- Facilitate an Event Storming, from big picture to process modelling
- Use Impact Mapping to connect deliverables to business goals
- Turn the strategic design into team boundaries and architecture decisions
Audience
- Developers, tech leads and architects
- Product managers, product owners and domain experts
- Ideally a mixed group of business and tech people
Prerequisites
- No prior DDD knowledge required
- Being involved in building or evolving a software product
Programme
-
Module 1 Why strategic design
- Complexity lives in the domain, not only in the code
- Problem space vs solution space
- From the big ball of mud to explicit boundaries
- Tactical patterns, and why they come second
-
Module 2 Impact Mapping
- Starting from a measurable business goal
- Actors, impacts and deliverables
- Prioritising and slicing by impact
- Connecting the map to the roadmap
-
Module 3 Event Storming
- Big picture: domain events and the timeline
- Hotspots, pivotal events and open questions
- Process modelling: commands, policies and read models
- Facilitation tips and remote variants
-
Module 4 Subdomains and ubiquitous language
- Core, supporting and generic subdomains
- Build, buy or outsource decisions
- A shared language and how to keep it alive
- Spotting language conflicts
-
Module 5 Bounded contexts and context mapping
- Finding boundaries from the Event Storming
- Context map relationship patterns
- Anti-corruption layers and published languages
- Aligning teams with contexts (Conway's law)
Teaching approach
A workshop more than a course: short concept sessions alternate with facilitated exercises on large modelling surfaces (physical walls or online whiteboards). In-house, Event Storming and Impact Mapping run on your own domain, so the workshop already produces usable outputs: an impact map, a big picture of your domain and a first context map.
Tailored to your context
A preparation call helps choose the domain to explore and the right participants. The session can focus on discovery (Impact Mapping, Event Storming) or on boundaries and team organisation (context mapping), depending on where you are. In coaching format, I facilitate the following modelling sessions with your teams.
Let's talk about your needs
A programme to adapt, a team to train, a question about a format? Write to me and let’s discuss.
Get in touchantoinecoulon.consulting@gmail.com