From Days to Hours: How EventStorming Transformed Our Domain Modeling Process - Vadzim Prudnikau

Event storming is a collaborative workshop focused on discovering domain knowledge through visual modeling using sticky notes and a large physical wall space

Key elements include:

• Domain events (written in past tense)
• Hotspots (unclear areas needing discussion)
• Commands (user actions/intentions)
• Policies (business rules)
• Actors/external systems
• Bounded contexts (service boundaries)

Phases of event storming:

• Chaotic exploration (unstructured brainstorming)
• Enforcing timeline (ordering events)
• Process modeling (adding details)
• Finding bounded contexts

Success factors:

• Have the right people (domain experts + developers)
• Proper room setup with uninterrupted wall space
• No laptops/phones allowed
• Time pressure and visible timer
• Clear facilitation
• Polite interruption of long discussions

Benefits include:

• Faster knowledge transfer vs traditional requirements gathering
• Common language between business and developers
• Early identification of problems and opportunities
• Service boundaries discovery
• Future API design insights
• Reduced incorrect assumptions

Best practices:

• Start small with manageable scope
• Avoid technical terms with domain experts
• Document results accessibly
• Time box all activities
• Mix different groups/roles
• Have backup facilitators

Common pitfalls to avoid:

• Running without proper preparation
• Allowing one person to dominate
• Not having the right domain experts
• Going too technical too early
• Not time-boxing activities
• Skipping important phases due to time pressure