ddd-event-storming

One-line summary

A collaborative workshop format invented by Alberto Brandolini: domain experts and engineers map a business process as a left-to-right sequence of past-tense events on a wall (physical or virtual), surfacing commands, actors, policies, read models, and hotspots along the way.

When to use this skill

• Greenfield project — discovering the domain and its bounded contexts before writing code.
• Existing system that nobody fully understands — reconstructing the domain knowledge that's gone tribal.
• Cross-team alignment — bringing domain experts and engineers into the same conversation.
• Identifying bounded context boundaries — events that don't fit a single context usually mark a boundary.
• Designing a single feature or process — process-modeling EventStorming zooms in on one workflow.

When NOT to use this skill

• Tactical code-level question — EventStorming is a domain-discovery workshop, not a code design tool.
• The domain is genuinely well-understood and stable — the workshop pays off when there's confusion or fresh perspective needed; not when everyone already agrees.
• Without a domain expert participating — running EventStorming with only engineers reproduces what engineers already think, not what the business actually does.

Core content