Event Storming
A collaborative method for capturing and analyzing business processes through visual modeling.
Classification
- ComplexityMedium
- Impact areaBusiness
- Decision typeDesign
- Organizational maturityIntermediate
Technical context
Principles & goals
Use cases & scenarios
Compromises
- Misunderstandings among stakeholders.
- Insufficient preparation can lead to chaos.
- Focusing on details can distort the big picture.
- Prepare participants for the workshop.
- Formulate events clearly and precisely.
- Plan regular feedback rounds.
I/O & resources
- Sticky Notes and Markers
- Space for Conducting the Workshop
- Prepared Agenda
- Visual Process Representation
- Documentation of Outcomes
- Identified Stakeholders
Description
Event Storming is a method that enables teams to understand and model complex business processes by visually representing events, actors, and workflows. This method promotes collaboration and shared understanding within teams and among various stakeholders.
✔Benefits
- Improved Shared Understanding
- Identification of Bottlenecks
- More Efficient Processes
✖Limitations
- Can be time-consuming.
- Requires engaged participants.
- Can overwhelm complex topics.
Trade-offs
Metrics
- Number of Identified Bottlenecks
Counts the bottlenecks identified during the Event Storming.
- Participant Engagement
Measures participant engagement during the workshop.
- Quality of Outcomes
Evaluates the quality of the outcomes produced during the Event Storming.
Examples & implementations
Event Storming for an E-Commerce System
A team uses Event Storming to model the user journey and associated events for a new e-commerce system.
Optimizing an Order Process
Through Event Storming, a team identifies bottlenecks in the order process and develops solutions for efficiency improvement.
Requirements Analysis for a Mobile App
A team uses Event Storming to capture and prioritize requirements for a new mobile app.
Implementation steps
Identify and invite workshop participants.
Define the agenda and objectives of the workshop.
Capture events and actors during the workshop.
⚠️ Technical debt & bottlenecks
Technical debt
- Insufficient documentation of outcomes.
- Lack of follow-up on identified bottlenecks.
- Unclear responsibilities after the workshop.
Known bottlenecks
Misuse examples
- Conducting Event Storming without clear objectives.
- Not inviting important stakeholders.
- Not documenting events.
Typical traps
- Assuming all participants have the same understanding.
- Overlooking important stakeholder perspectives.
- Focusing on the outcome instead of the process.
Required skills
Architectural drivers
Constraints
- • Time Constraints for Workshops
- • Availability of Stakeholders
- • Technical Limitations of the Tools Used