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.

1. Event StormingA (really) quick introduction
Steve Maraspin
UX Scotland - Edinburgh, Jun 7th 2017

2. A MODEL

3. ANOTHER ONE

4. YET ANOTHER

5. https://commons.wikimedia.org/wiki/File:Software_dev_med.jpg
SOFTWARE ENGNEERING

6. https://simple.wikipedia.org/wiki/Flow_chart

9. https://upload.wikimedia.org/wikipedia/commons/b/b1/UML_Sequence_diagram.JPG

10. https://www.flickr.com/photos/two-wrongs/3188730766
LIMITATIONS

11. Issues of Traditional Modeling Tools
(in software development)
● Losing the big picture
● Ignoring the End-User
● Being data-flow/database driven
● Complexity

17. Pizza
ordered

18. Pizza
ordered
Pizza
baked

19. Pizza
ordered
Pizza
baked
Put pizza
into oven

20. Pizza
ordered
Pizza
baked
Put pizza
into oven

21. Pizza
ordered
Pizza
baked
Put pizza
into oven
Orders
pizza

22. Pizza
ordered
Pizza
baked
Put pizza
into oven
Orders
pizza
Online
orders?

23. Pizza
Ordered
online
Pizza
baked
Put pizza
into oven
Make
Internet
Order
Pizza
Ordered
In store
Make
Desk
Order

24. DRILL DOWN
https://en.wikipedia.org/wiki/File:USA_New_York_City_location_map.svg

25. OVERVIEW
https://www.jpl.nasa.gov/news/news.php?feature=4541

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)

29. UNLIMITED MODELING SPACE
https://pixabay.com/p-1050036/?no_redirect

30. INTERESTING
https://pixabay.com/en/discovery-space-shuttle-launch-2041999/
DISCOVERIES

31. SYSTEM ANALYSIS
https://pixabay.com/p-365769/?no_redirect

32. https://commons.wikimedia.org/wiki/File:Lausanne_first_grade_class.jpg
LEARNING

33. https://pixabay.com/en/workplace-team-business-meeting-1245776/
SHARING

34. NOT A REPLACEMENT
https://pixabay.com/p-365769/?no_redirect

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
● It’s 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, it’s much
easier to achieve a goal. To share an idea for a solution)

37. https://www.flickr.com/photos/florianric/7263382550

38. Thank You

39. http://eventstorming.com/
https://www.slideshare.net/ziobrando/event-storming-recipes

40. @maraspin