ESSENTIALS - Event Storming for fun and profit
summary
Event Storming maps domain events on orange stickies and questions on pink ones, starts with start at the end, and surfaces concrete seams for redesign. Used on legacy apps, business processes and new designs; in one case procurement lead time drops from 30 days to 12 days and occasional requests fulfill in a few hours by pre‑staging three server types. Sessions need lots of stationery, timeboxing (Pomodoro), 8–40 participants, and produce photos plus clustered aggregates to act on.
AI-written summary · about
chapters (7)
- 0:00Event Storming intro
- 8:54Event Storming basics
- 13:48Event Storming for business
- 21:11Event Storming for legacy
- 27:14Event Storming for new apps
- 33:58Event Storming impact
- 40:39Q&A
related talks
50mHow EventStorming Transformed Our Domain Modeling Process
31mHow EventStorming Transformed Our Domain Modeling Process
49mFrom Days to Hours: How EventStorming Transformed Our Domain Modeling Process
01h 02mEvent Storming for domain-driven design
14mSession 1: Event Storming
40mEventStorming Lessons Learned - tens of thousands of post-its later
01h 02mRethinking Enterprise Software
48mA universe full of events - EventStorming