From Days to Hours: How EventStorming Transformed Our Domain Modeling Process
summary
EventStorming reduces weeks of meetings to hours by running a time‑boxed, facilitator‑led workshop that fills a long wall with color‑coded sticky notes to map domain events, actors, external systems and commands, then turns unclear items into hotspots and a voted backlog. Real runs surface surprising counts—10 hotspots for a small feature, 20 for a release process—and produce concrete artifacts: preliminary APIs, read models, integrations and bounded contexts, sometimes prompting radical outcomes (merge services or abandon a project). Digital followup uses photos or Mirrorboard.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:50EventStorming for developers
- 10:39What EventStorming is
- 13:54Preparing for session
- 18:30Big picture EventStorming
- 23:47Identifying actors
- 26:38Walkthrough and hotspots
- 32:59Finding bounded contexts
- 34:46Process modeling
- 40:28When to skip phases
- 43:01Common questions
- 46:32Running in company
- 48:20Online EventStorming tips
- 50:47Success stories
- 53:18Key takeaways
related talks
37mGet ready for the storm - Remote Event storming in action
47mEvent Storming — Closing the Gap Between IT and Business
42m100,000 Orange Stickies Later
48mEvent Modeling
54mThinking in Events
40mArchitecture Modernization with DDD
51mUXDD: A New Pragmatic Methodology for Domain Modeling and User Experience.
54mDomain-Driven Design and Team Topologies for Product-led Organizations