Event storming
A workshop where business and technical people map a process as a timeline of events on sticky notes to find rules, gaps and boundaries.
Alberto Brandolini created it. Participants write domain events in past tense (“order placed”, “invoice sent”) on a long wall, then add the commands that cause them, the people involved, the rules and the open questions. In a few hours it surfaces disagreements that specifications hide, and clusters of events often reveal bounded contexts. It works in person or on an online whiteboard.
Related terms
- DDD (domain-driven design): Designing software around the business’s own language and rules, with the code split where that language changes meaning.
- Bounded context: A part of a system where each business term has one meaning and one model, with explicit translation at its edges.
- Event-driven architecture: Services publish facts such as “order placed” and others react to them, instead of services calling each other directly.
