From Days to Hours: How EventStorming Transformed Our Domain Modeling Process
summary
EventStorming claims to compress domain discovery from days to hours by running time‑boxed, collaborative workshops that use a long wall, a visible timer and piles of sticky notes (orange for events, blue for votes, green for policies). A 10–15 minute chaotic exploration often unfolds into a 2.5‑hour session that produced 10 hotspots for one small system, surfaced commands, read models, aggregates and bounded contexts, and even led to abandoning a needless feature; digitize results into Miror afterward.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 1:10Why EventStorming matters
- 2:13Common domain modeling pitfalls
- 5:50What EventStorming discovers
- 7:16Better domain modeling process
- 9:25EventStorming in a nutshell
- 10:30EventStorming for teams
- 11:34Key steps to success
- 14:06Preparing workshop
- 16:34Chaotic exploration phase
- 18:43Timeline and pivotal events
- 21:15Group dynamics and hotspots
- 22:43Actors and external systems
- 24:34Storytelling walkthrough
- 25:37Prioritizing hotspots
- 27:44Big picture wrap-up
- 29:07Facilitation tips
- 31:18Technical insights
- 34:31Finding bounded contexts
- 35:35Discovering aggregates
- 37:22EventStorming questions
- 38:05EventStorming for existing systems
- 39:10Facilitator tips
- 40:14Introducing EventStorming
- 41:36When to stop
- 41:57Online vs in-person
- 43:24Next steps
- 44:28Summary
- 44:52Q&A
related talks
50mHow EventStorming Transformed Our Domain Modeling Process
31mHow EventStorming Transformed Our Domain Modeling Process
47mESSENTIALS - Event Storming for fun and profit
33mEvent Storming for Everyone
01h 02mEvent Storming for domain-driven design
14mSession 1: Event Storming
40mEventStorming Lessons Learned - tens of thousands of post-its later
37mGet ready for the storm - Remote Event storming in action