Event Storming is a technique for modeling complex systems and processes. It involves gathering people from different backgrounds to collect facts about events and constantly review the model as new information emerges. The key benefits are that it helps keep everyone engaged in discovery and taming complexity, builds shared understanding, and works towards shared goals. While not replacing other modeling tools, it is especially useful for complexity involving rules, policies, and connected systems more than interfaces.
11. Issues of Traditional Modeling Tools
(in software development)
Losing the big picture
Ignoring the End-User
Being data-flow/database driven
Complexity
28. Recipe
Gather people with different backgrounds together
Collect events (IE facts)
Feel free to stick / scratch notes, and constantly review
the model as new stuff (aka complexity) emerges
Make sure your modeling surface is big enough. You
want to make sure you can explore, discover new things.
(Sticking as many notes as possible within a tiny phisical space is not the point)
35. All models are wrong,
but some are useful
George E. P. Box
36. Key Points
Not an alternative to existing UX oriented modeling techniques
Especially useful where complexity (rules, policies, connected
systems, ...) is more prominent than interaction
Gets people with different backgrounds together
Its based on facts and discovery at the same time. This helps
keeping everyone (IE developers, designers, managers, )
always involved and engaged. At every session, you can
expect many Wow moments and unexpected outcomes
Helps discovering (and taming) complexity
Builds a shared understanding of the context; a shared
vocabulary. And, most importantly, shared goals (...when
people are all working towards the same direction, its much
easier to achieve a goal. To share an idea for a solution)