Discovering domain terminology is essential, and this terminology becomes a part of the Ubiquitous Language. However, the process of discovery can be rather lengthy and not always successful. When we discuss how the business works and what problems are we going to solve by writing software, too often the conversation comes down to discussing features that the business is keen to implement. A set of features, of course, can be called "software," but it does not necessarily form a system. And to build a comprehensive solution for a particular problem, more system-level thinking is required.

But who is going to tell us how the business operates as a system? Whom shall we talk to and what format this conversation should take? We will uncover issues like these and try to find some answers in this chapter.  

In this chapter, we will cover the following topics:

• Learn what EventStorming is
• Study the practical aspects of EventStorming
• Get to know how to facilitate a workshop yourself
• Decide what to do after the workshop ends