Have you ever wondered why some organizations consistently outperform others in terms of performance, innovation, and adaptability? The secret often lies in mastering a powerful yet surprisingly simple technique. This technique is called event storming, which allows for the visualization, analysis, and transformation of business processes in a reliable manner.
What is Event Storming and why is it important?
Event Storming is a workshop technique aimed at capturing and visualizing complex business processes. It was introduced by Alberto Brandolini, an Italian software consultant, as a way to simplify the understanding of complex systems. Event Storming is particularly effective in modeling event-driven systems, but its applications go beyond software development.
This approach is based on a simple but powerful idea: using sticky notes and markers to represent domain events, commands, aggregates, and other elements on a physical or digital workspace. This way, participants can gain a holistic view of the entire system and its interactions, discover bottlenecks, and identify areas in need of improvement.
Why is Event Storming Important?
- Common Understanding: It brings together different teams, such as software developers, business analysts, and domain experts, promoting a common understanding of complex processes.
- Visualization: It provides a visual representation of system events and their relationships, making it easier to identify potential bottlenecks or inefficiencies.
- Efficiency: Event Storming encourages increased efficiency by enabling teams to iterate quickly and adapt their understanding of the problem space.
Step by Step: How to Conduct an Event Storming Session?
Conducting a successful Event Storming session requires careful planning and execution. Here are the key steps you should take:
Step 1: Assemble a Diverse Team
Gather a multidisciplinary team that includes domain experts, programmers, business analysts, and anyone with relevant knowledge about the system or process you are modeling.
Step 2: Define the Problem Space
Clearly define the scope of your Event Storming session. What business process or system are you trying to model? What are your goals for this session?
Step 3: Create an Event Storming Space
Select a physical or virtual space for the session. You will need a large board or canvas, sticky notes, markers, and a place for participants to move around.
Step 4: Identify Domain Events
Begin by identifying key events in the system or process. These events are typically represented as sticky notes on the board.
Step 5: Explore Relationships Between Events
Discuss and map the relationships between events. Use arrows or lines to connect related events and indicate the flow of information or actions.
Step 6: Add Commands and Policies
Introduce commands (actions that change the system’s state) and policies (rules governing system behavior) to refine your model further.
Step 7: Refine and Iterate
Continuously refine your model as you gain a deeper understanding of the problem space. Remove redundancies and ensure that everyone on the team has a clear picture of the system.
Step 8: Record Insights
During the session, record insights, questions, and potential improvements. These will help guide future iterations of the system.
Step 9: Document the Session
After the Event Storming session, document the results and insights. This documentation will serve as a valuable reference point for future work.
Event Storming: User Registration – Example
- Events (Yellow Sticky Notes):
Events represent things that have happened or will happen in the system. In this case, we are registering user interactions and outcomes related to their registration.
- Commands (Blue Sticky Notes):
Commands are actions or tasks triggered by events. Here, we capture the commands necessary to handle user registration. For example, when the event “Registration Form Submitted” occurs, it triggers the commands “Create User Profile” and “Send Confirmation Email.
- Policies (Pink Sticky Notes):
Policies are rules or constraints that influence how commands are executed or events are generated. For example, the “Password Complexity Policy” ensures that user passwords meet specific criteria, while the “Email Verification Policy” requires email confirmation.
- Aggregates (Green Sticky Notes):
Aggregates represent units in the system that are responsible for handling commands and generating events. In this case, the “User” aggregate is responsible for managing user registrations.
- Process Flow (Arrows/Connections):
The process flow visually illustrates how events trigger commands and policies, and how aggregates handle these actions. It helps in understanding the sequence of steps in the user registration process.
- Questions and notes (additional sticky notes):
Use other sticky notes for questions or notes that will come up during the Event Storming session. You can use them to capture uncertainties or follow-up actions.
Event Storming allows the team to collectively explore and model the system’s behavior, making it a valuable tool for understanding complex processes and designing software systems. In this example, we’ve focused on the user registration scenario, but Event Storming can be applied to various other processes and fields related to IT.
How to Use Event Storming for Business Process Modeling
Event Storming can be a powerful tool for modeling and improving business processes. Here are some ways you can apply it:
- Identifying Bottlenecks: Utilize Event Storming to identify bottlenecks, inefficiencies, or pain points in your current business processes.
- Exploring Opportunities: Collaboratively generate new ideas and opportunities for process improvement within your team through Event Storming sessions.
- Mapping Customer Journeys: Understand the paths and interactions of your customers with your company by modeling their experiences using Event Storming.
- Designing Future State: Create a model of the ideal future state for a process or system, incorporating best practices and improvements identified during the sessions.
Most Popular Tools for Supporting Event Storming
Event Storming sessions can be conducted using physical tools like sticky notes and boards or digital tools. Here are a few popular options:
- Miro: An online whiteboard platform that supports virtual Event Storming sessions.
- Stormboard: A digital workspace for visual collaboration, perfect for remote Event Storming.
- Post-it® App: Allows participants to capture physical sticky notes digitally and share them electronically.
- Event Storming Cards: Physical or digital cards specifically designed for Event Storming activities, often used for quickly creating events and commands.
Tips and Best Practices for Effective Event Storming
As you embark on your Event Storming journey, consider the following tips and best practices:
- Prepare in Advance: Make sure you have all the necessary materials and tools prepared before starting the session.
- Facilitate Collaboration: The facilitator plays a crucial role in maintaining session focus and encouraging active participation from all team members.
- Focus on Outcomes: Remember that the goal of Event Storming is to achieve a shared understanding and specific outcomes. Avoid getting lost in unnecessary details.
- Iterate and Improve: Event Storming is an iterative process. Be open to revising and improving your models as you learn more about the process.
- Involve Domain Experts: Domain experts are invaluable in providing insights into the intricacies of the business domain.
FAQ
Q: How long should an Event Storming session last?
The duration of an Event Storming session can vary depending on the complexity of the process being modeled. Typically, sessions can range from a few hours to a full day. It’s important to allocate enough time to adequately cover the scope without rushing.
Q: What materials are needed for conducting Event Storming?
Materials such as sticky notes, markers, a whiteboard or digital tool, and a collaborative workspace are necessary. Additionally, having access to domain experts and relevant documentation can be beneficial.
Q: Is Event Storming suitable for every type of project?
Event Storming is particularly suitable for projects involving complex business processes or domains. It may not be necessary for straightforward projects with well-defined processes. However, it can still be valuable for gaining a deeper understanding of any project.
Klaudia Szczepara
Marketing Specialist at Euvic
