EventStorming from the trenches
summary
A family-owned tank manufacturer gets a four-workshop program that uses EventStorming plus the Dot Game, Quest, extreme contracts and Popcorn Flow to map hundreds of observed events into hot spots, converge them into five prioritized hot spots, form eight cross‑functional teams and run two-week experiments. The teams deliver small, reversible changes, set owners, report to a soviet, create a shared Microsoft Teams group, and after three months the siloed structure is visibly shaking and continuous improvement is still running.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 5:14Why EventStorming matters
- 7:25Customer context and story setup
- 10:36Must-haves for the workshop
- 18:12First workshop: EventStorming basics
- 25:01QUEST framework explained
- 32:14Dot Game and process bottlenecks
- 35:49Second workshop: Hot spot prioritization
- 41:18Third workshop: Problem-solving options
- 46:16Fourth workshop: Commitments and experiments
- 48:03Outcomes and customer feedback
related talks
50mHow EventStorming Transformed Our Domain Modeling Process
41mEfficient Domain-Driven Design: An Introduction to Event Storming
27mTheory to action: Architecting and implementing your team operating system
15mEmotions, Examples, Entropy
01mMike Wojtynac at DDD Europe 2025
01h 04mAdvanced Software Teaming
34mPractical Event Storming with AsyncAPI v3 and ZenWave SDK
01h 00mMob Programming, A Whole Team Approach