At first look, EventStorming is deceiptivaly simple: just have a long paper roll available, and a virtually unlimited stock of colored sticky notes and start modelling problems that looked too big to be modelled. But the ability to visually mastering large scale complexity opens the way to many interesting outcomes.

- Better business processes: once you see the process, impediments and correlations are vividly displayed. You can't avoid tackling them.

- Better software architectures: see the areas where stakeholders needs are in conflict, resolve coflicts by leveraging bounded contexts.

- Better learning: exploration of complex domain is now question-driven and with a visible collective sketch. Your team will never be so wise.

- Better interactions: trigger the right conversation between the right people.

In this book you'll find guidance about how to leverage the potential of EventStorming.

Disclaimer: work in progress

The book is still in progress. There's holes and FIXME section. And there's a great need for feedback.

I 've set up a trello project in order to collect some feedback. Don't know yet if that's a good idea or not, but here's the link.