Loading content
Event Storming is a method that enables teams to understand and model complex business processes by visually representing events, actors, and workflows. This method promotes collaboration and shared understanding within teams and among various stakeholders.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Event Storming is a collaborative modeling method that makes domain events visible as a timeline to build shared understanding of complex domains.
Alberto Brandolini developed the method around domain-driven design as a large-scale color-coded workshop format.
Participants collect past-tense domain events on a timeline and add triggers, commands, actors, policies, read models, and external systems. Hotspots mark uncertainty or conflict, while process boundaries and language shifts help identify aggregates and bounded contexts.
Business-relevant facts show what happens over time in the domain.
Commands, actors, and policies explain what produces events and what follows.
Hotspots and language differences expose knowledge gaps and domain boundaries.
Event Storming fits shared domain learning, process design, and strategic DDD. It needs real domain participation and strong facilitation; the workshop model is a hypothesis to refine with cases, rules, and system reality.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.