Event Storming is a powerful facilitation technique used to explore complex systems and generate shared understanding among stakeholders. Originating from the domain of Domain-Driven Design (DDD), Event Storming brings together people from various domains of expertise to collaboratively model business processes, identify critical events, and uncover key system behaviors. This method fosters alignment and helps create a clearer view of the system’s requirements, constraints, and opportunities.
1. The Concept of Event Storming
At its core, Event Storming focuses on understanding and mapping the flow of business events that drive the system. These events represent significant occurrences within a business process that trigger a chain of actions or reactions. Events could be anything from “Customer Created” to “Payment Processed” or “Order Shipped.” Through this method, participants can highlight important events, dependencies, and key touchpoints, ensuring a deeper understanding of how different components interact.
2. Why Event Storming Works
The simplicity of Event Storming makes it highly effective. By using large, colorful sticky notes to represent events, decisions, and interactions, this approach avoids the complexity of diagrams or overly technical documentation. The visual nature of the method encourages participants to contribute and engage actively, regardless of their technical background. Whether you’re dealing with developers, business analysts, or subject-matter experts, Event Storming allows everyone to contribute their insights in a non-technical way, leveling the playing field and enabling shared understanding.
3. The Process of Event Storming
The process typically follows these steps:
-
Preparation: Gather the right stakeholders—usually a mix of people with domain expertise, business knowledge, and technical backgrounds. You’ll need a large wall or whiteboard and sticky notes in different colors.
-
Identify Key Events: Start by brainstorming significant events that occur within the system or business process. For instance, in an e-commerce system, you might identify events like “Order Created,” “Payment Received,” or “Shipping Completed.” These events should be written on orange sticky notes.
-
Mapping the Flow: Once the events are identified, the next step is to arrange them in chronological order, mapping the flow of the business process. As participants add their knowledge, the system begins to take shape visually, allowing for a better understanding of how things work.
-
Identifying Commands, Aggregates, and Policies: For each event, ask what triggers it (a command) and what happens afterward (an action). This helps identify aggregates (main entities in the system) and policies (business rules that control the flow). Use different colors of sticky notes to represent these components, and place them alongside the events.
-
Find Gaps and Bottlenecks: As the event map grows, gaps, ambiguities, and inefficiencies become apparent. This is one of the most valuable aspects of Event Storming, as it allows teams to uncover hidden complexities that were previously overlooked.
-
Refinement and Iteration: After the initial mapping, review and iterate on the event storming model. Teams can dive deeper into specific events, ask more detailed questions, and make adjustments to ensure that all necessary details are captured.
4. Roles in Event Storming
Event Storming is an inclusive process, and every participant brings their expertise to the table. These roles are typically involved in the process:
-
Facilitator: The facilitator’s role is to guide the session, ensure that everyone contributes, and maintain focus on the goal of shared understanding. They may encourage discussion, clarify concepts, or push for deeper insights.
-
Subject Matter Experts (SMEs): SMEs provide the domain knowledge necessary to ensure the event map accurately reflects the business process. They help identify key events, describe them in detail, and explain how the system behaves in different scenarios.
-
Developers: Developers offer technical insights on how events translate into system behavior. They can highlight technical constraints, possible bottlenecks, and potential solutions to issues uncovered during the event storming process.
-
Business Analysts: Business analysts help ensure that the model aligns with business objectives. They ask questions about why certain events happen and how they relate to business outcomes, helping to ensure that the solution reflects business priorities.
-
End Users: If possible, including actual users or customer representatives can bring valuable perspectives about the system’s usability and how the events translate into user interactions.
5. Benefits of Event Storming
-
Unified Understanding: Event Storming ensures that all stakeholders—from business leaders to developers—are aligned with the goals and complexities of the system. It provides a visual, real-time model of the system that can be shared and adjusted collaboratively.
-
Reveals Gaps and Ambiguities: By actively participating in the event storming session, teams can identify missing pieces, unclear requirements, or potential flaws in the system design early on, saving time and resources later in the development process.
-
Fosters Collaboration: Event Storming breaks down silos by engaging a wide variety of stakeholders. This collaborative environment encourages open dialogue and knowledge sharing, creating a culture of mutual respect and understanding.
-
Flexible and Adaptive: The process is highly adaptable, meaning it can be used for a wide range of purposes—from system design to process optimization, risk identification, or strategic alignment.
-
Faster Decision-Making: With all key stakeholders in the room, decisions are often made faster, and there’s a collective understanding of the decisions made, reducing the need for repeated discussions and clarifications.
6. Practical Tips for a Successful Event Storming Session
-
Keep it Short and Focused: A typical Event Storming session can last a few hours to a full day. Keep the pace energetic and focused to avoid mental fatigue. If the session is complex, break it into smaller parts for deeper dives.
-
Create a Safe Environment for Ideas: Encourage participation from everyone, regardless of their role or expertise. The goal is to generate ideas freely, with no judgment. This allows the team to explore all possibilities and come up with innovative solutions.
-
Use Color Effectively: Utilize different colors of sticky notes to represent different aspects of the system (e.g., events, commands, aggregates). This makes it easier to navigate the map and identify patterns.
-
Capture and Share Insights: After the session, document the results and share them with all stakeholders. This ensures that the shared understanding developed during the session is preserved and can be referred to later in the process.
-
Iterate: Event Storming is not a one-time exercise. As new insights emerge, the map should be updated. Over time, this process creates a rich, detailed understanding of the system that evolves as the project progresses.
Conclusion
Event Storming is an effective method for facilitating shared understanding in complex systems. By visually mapping events and their relationships, this technique enables cross-functional teams to identify gaps, understand business processes, and design systems that align with both technical and business goals. With the right facilitation and a collaborative mindset, Event Storming can be a game-changer in ensuring all stakeholders are aligned and equipped to move forward confidently.