Mike Wojtynac at DDD Europe 2025
summary
Claim: inviting business people to design-level storming already loses them because sessions are too high level of detail, leaving mostly engineers and tax people in the room. Proposal: skip layered diagrams and run code storming on the domain model so conversations map directly to implementation. Offers no toolchain or numeric evidence, just the observation that reducing abstraction should preserve business engagement and speed feedback loops, and urges trying short domain-first coding sessions to validate whether that actually improves alignment.
AI-written summary · about
related talks
14mSession 1: Event Storming
55mEvent Storming - how to shorten the distance between IT and Business
50mHow EventStorming Transformed Our Domain Modeling Process
41mEfficient Domain-Driven Design: An Introduction to Event Storming
31mHow EventStorming Transformed Our Domain Modeling Process
01h 02mEvent Storming for domain-driven design
01h 02mRethinking Enterprise Software
39mFrom Domain Boundaries to Software Architecture