This chapter covers
- Mapping out your business with EventStorming
- Beginning the process of identifying domains and subdomains
- Understanding the principles behind EventStorming
- Planning and running EventStorming workshops
- Identifying business problems and opportunities with EventStorming
- Facilitating EventStorming workshops
Modernization leaders must steer clear of making crucial architectural choices based solely on a limited, shallow grasp of the landscape. It’s easy to fool yourself into thinking a bad design is good when you are too disconnected from the details. When I was coaching a chief product officer at a client in the property sector, he identified three high-level domains as the basis for the new company structure. He was very confident it was the right approach. But when we put the idea in front of various employees, they found multiple reasons why the proposed architecture wouldn’t work. They had a much deeper understanding of domain intricacies, which he lacked. He was intelligent and humble enough to seek and accept feedback, but others choose the Ivory Tower Architect path (http://mng.bz/g7Nx) and enforce their naive ideas.