event-storming

Event storming is a workshop technique for domain discovery that models business events, actors, and policies on a timeline to clarify domain behavior and surface causality before implementation.

Model bounded contexts by mapping domain events on a timeline, adding commands and actors, then grouping aggregates and policies to define explicit boundaries for downstream state-machine and API design.

Use event storming for workflow analysis when you need to surface temporal ambiguities, capture hotspots, and identify invariant-driven aggregates before committing to an event-driven architecture implementation.

Identify aggregates by extracting invariants from the event timeline, and define policies as explicit condition-action rules that connect commands to the resulting domain events and state transitions.

Event storming facilitates handoff by producing a coherent flow of events, aggregates, and read models that directly inform downstream bounded-context scoping, state-machine logic, data schemas, and API design.

Event storming works for event-driven architecture planning by enforcing event-first naming discipline and capturing explicit condition-action policy rules to reveal system flow before technical implementation.