EventStorming¶
Explore a business domain together by making its meaningful events visible, relating them, and challenging the resulting shared account.
Core Idea¶
EventStorming is a collaborative workshop for exploring a business domain through meaningful things that happened or can happen, called domain events. Participants put events into a shared view, relate them, and challenge what the view omits or misstates. People with different knowledge test that account against their experience rather than accepting a single narrator's version. Differences in language, gaps, and unresolved issues become visible. The method has several styles and no single required deliverable.[ref-b1d4839462dc][ref-f3f3b14720f1]
Scope of Application¶
Use the name for facilitated, shared, event-led inquiry into a business domain; a wall or digital board can hold the account.[ref-b1d4839462dc][ref-9fa34fbec976]
- Existing process: Easy LMS mapped its development workflow remotely to find gaps and confusion.[^ref-9fa34fbec976]
- Business landscape: Lowlanders mapped mortgage events in a Big Picture workshop.[^ref-567d42628bff]
- Service exploration: The creator includes envisioning services and new business models among the workshop styles.[^ref-b1d4839462dc]
- Software design: The creator also includes designing event-driven software as a workshop purpose.[^ref-b1d4839462dc]
Big Picture work often uses a timeline, though some event groups are cyclic or unordered; ordering every event would misrepresent those parts of the domain.[^ref-f1d57389e8ca]
Clarity¶
Ask which events participants named and what they learned by comparing them. Lowlanders found that “pieces” meant different things in different mortgage contexts and kept an unresolved disagreement visible.[^ref-567d42628bff] Easy LMS found duplicates, branches, and hotspots in its workflow.[^ref-9fa34fbec976] This workshop differs from event sourcing or a persistent event-centered data schema; neither architecture is required. The test is what the group learned, not how many notes it produced.
Manages Complexity¶
Participants contribute what they know without any one person needing a complete picture. Comparing their events exposes conflicts and missing steps; a facilitator can mark a hotspot instead of forcing agreement.[^ref-f3f3b14720f1] The shared account stays provisional: an event cluster may suggest a boundary, but it does not prove where a team or software service belongs.[^ref-567d42628bff] Uncertainty becomes a concrete question to investigate later.
Abstract Reasoning¶
Use three moves: elicit events in domain language; compare how participants order and name them; then probe gaps, exceptions, and disagreements.[^ref-f3f3b14720f1] The group builds an internal Representation of business happenings on a visible surface. Participants interpret and revise that shared account, even when parts are uncertain or unordered. Its names and relations are working hypotheses, not a final inventory.
Knowledge Transfer¶
The method carries from Easy LMS's development-process question to Lowlanders' mortgage-domain question because both groups built and challenged shared event accounts.[ref-9fa34fbec976][ref-567d42628bff] One clarified a workflow; the other explored possible boundaries. A solo process diagram is not thereby EventStorming because collaborative challenge is part of the method. Beyond business-domain inquiry, an event timeline is an analogy; Representation names the wider idea of mapping something onto a medium for interpretation.
[^ref-b1d4839462dc]: EventStorming, “EventStorming”, opening description, Styles, and Services (Onsite and Remote). Full creator-controlled page directly inspected. Styles describe supported purposes, not a claim that every workshop has each output. [^ref-f3f3b14720f1]: Alberto Brandolini, “Discovering Bounded Contexts with EventStorming”, “Enter EventStorming” and “Structure of a Big Picture workshop,” Steps 1–4. Full creator-authored essay directly inspected; Big Picture steps are not universal requirements for all styles. [^ref-f1d57389e8ca]: EventStorming, “Conversational System”, opening problem and “Therefore.” Full creator-controlled page directly inspected; it allows a nonsequential segment within a shared event workshop. [^ref-9fa34fbec976]: Easy LMS, “How we use EventStorming to make our processes clear”, 7 September 2021, sections on its development-process workshop and outcome. Full first-person practitioner account directly inspected; reported clarity is not a controlled efficacy measure. [^ref-567d42628bff]: Kenny Baas-Schwegler, “Towards Autonomous Aligned Teams with Domain-Driven Design”, Agile Alliance experience report, §§4.2–5. Full first-person mortgage workshop account directly inspected; Lowlanders is a pseudonym and later boundary mapping is a facilitator interpretation.
Relationships to Other Abstractions¶
Current abstraction EventStorming Domain-specific
Parents (1) — more general patterns this builds on
-
EventStorming is part of Representation Prime
EventStorming contains a shared event representation that participants build and challenge as an internal part of the workshop.
Hierarchy path (1) — routes to 1 parentless root
- EventStorming → Representation → Abstraction
Neighborhood in Abstraction Space¶
EventStorming sits in a sparse region of the domain-specific corpus (99th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Unclustered & Miscellaneous (2721 abstractions)
Nearest neighbors
- Database application — 0.76
- Data Model — 0.75
- Conceptual dependency theory — 0.73
- Naked objects — 0.73
- Actual Notice — 0.73
Computed from structural-signature embeddings · 2026-10-17