# Event Storming [Event Storming – The Complete Guide | Qlerify](https://www.qlerify.com/post/event-storming-the-complete-guide) [[Event Storming – The Complete Guide Qlerify|📎]] - Levels of Event Storming - Big Picture - Process Modeling - Software Design - Chaotic exploration - Hotspots (problems) - Opportunities (ideas or improvements) - Pivotal Events - Swimlanes - Process Modeling Grammar - Event → Policy → Command → System → Event - Policy → \[Human\] → \[Read Model\] → Command - Bounded Contexts - Aggregates - This layout visually defines the Aggregate’s public API - accepts (Commands) - produces (Events) [8 Steps in the Event Storming Process | Lucidspark](https://lucid.co/blog/8-steps-in-the-event-storming-process) [[8 Steps in the Event Storming Process|📎]] - Event storming was created in 2012 by Alberto Branolini, who believes that "problems cannot be solved with the same mindset that originated them." - 8 steps of the event storming process - Step 1: Gather your team - Orange = Events - Blue = Commands - Pink = System - Yellow = User - Tan = Aggregate - Grey = Policy - Step 2: Roll out - Step 3: Storm your events - Step 4: Organize your events - Step 5: Continue the model - Step 6: Group together - Step 7: Find your microservices - Step 8: Next steps