What is a Hot Spot?
In Event Storming, Hot Spots are used to identify areas of uncertainty, complexity, or potential problems within the business process being modeled. When conducting an Event Storming session, participants map out the domain’s key events on a timeline, and Hot Spots act as visual cues to mark aspects that need further discussion, clarification, or attention.
Here’s a breakdown of Hot Spot as a concept in Event Storming:
1. Definition:
A Hot Spot is essentially a signal or indicator that marks a place in the domain model that is unclear or requires more understanding. It could represent anything that introduces confusion or needs to be revisited. This can include:
Ambiguity in business rules or processes
Potential technical challenges or risks
Misaligned assumptions between team members
Areas requiring additional research or validation
2. Purpose:
The goal of identifying Hot Spots is to ensure that the team acknowledges uncertainties or problematic areas without getting stuck on them during the initial session.
This lets participants continue mapping out other events while noting that a specific part needs deeper examination later.
3. Visual Representation:
Hot Spots are usually represented by specific post-it colors (often red or orange) or shapes, such as "lightning bolts" or circles, to easily differentiate them from regular domain events.
This visual distinction is key to keeping focus on problem areas without letting them derail the flow of conversation.
4. Examples of Hot Spots in Event Storming:
Missing information: When the team lacks crucial details to complete the model, a Hot Spot might be placed where more information is needed.
Conflicting interpretations: If different team members have different understandings of a particular event or process, a Hot Spot marks the conflict for resolution.
Technical constraints: When a part of the process has potential technical challenges, such as performance bottlenecks or security concerns, this is marked with a Hot Spot.
Regulatory or policy questions: Legal or compliance issues that are not well-understood can be highlighted as Hot Spots.
5. Resolving Hot Spots:
After the Event Storming session, the Hot Spots should be addressed in follow-up meetings, research efforts, or discussions with domain experts.
Each Hot Spot typically leads to action items that are either assigned to individuals or teams for clarification and resolution.
6. Impact on Event Storming Sessions:
Hot Spots help maintain the flow of the brainstorming session by letting the team recognize problem areas without getting bogged down.
They enable more productive collaboration, as unresolved issues can be flagged without prematurely trying to solve them during the early stages of domain exploration.
Conclusion:
In Event Storming, Hot Spots act as placeholders for questions, risks, and uncertainties. By identifying and marking them, the team ensures that these potential problems get the necessary attention at a later stage, without interrupting the broader discovery process.