Event Storming - Collaborative Domain Modelling

At its core, Event Storming is about capturing the entire domain and visualising it in a consensual Big Picture in the form of sticky notes on a long wall. By distilling all relevant events from the domain and putting them consensually in a chronological order, intensive discussions with massive knowledge crunching about what is really going on in the entire domain arise.

On the one hand, business and subject matter experts learn from each other about the higher-level contexts that go beyond their respective silos. And even though some companies don’t want to admit it, at some point there will be no one left, who really understands how the company or a (complex) process works from end to end.

On the other hand, there is no better opportunity to get to know the domain and clarify or at least raise all questions directly to the business experts, as "Ambiguity does not compile." By having all people together in a room these questions can be addressed immediately and also bring new insights and potential for improvement to light.

By the end of an intense day the Big Picture can be clustered into functional areas or so called sub-domains, which serve as a great intermediate artefact for further investigation towards deriving a domain aligned system architecture. However, the Event Storming method is universal, and therefore not limited just to software design.