When to Use EventStorming
The workshop can be facilitated for many reasons:
Build a ubiquitous language
As the group cooperates in building the model of the business process, they instinctively synchronize the terminology and start using the same language.
Model the business process
An EventStorming session is an effective way to build a model of the business process. Since it is based on DDD-oriented building blocks, it is also an effective way to discover the boundaries of aggregates and bounded contexts.
Explore new business requirements
You can use EventStorming to ensure that all the participants are on the same page regarding the new functionality and reveal edge cases not covered by the business requirements.
Recover domain knowledge
Over time, domain knowledge can get lost. This is especially acute in legacy sys‐ tems that require modernization. EventStorming is an effective way to merge the knowledge held by each participant into a single coherent picture.
Explore ways to improve an existing business process
Having an end-to-end view of a business process provides the perspective needed to notice inefficiencies and opportunities to improve the process.
Onboard new team members
Facilitating an EventStorming session together with new team members is a great way to expand their domain knowledge.
In addition to when to use EventStorming, it’s important to mention when not to use it. EventStorming will be less successful when the business process you’re exploring is simple or obvious, such as following a series of sequential steps without any interest‐ ing business logic or complexity.