Strategic event storming
A template for conducting strategic event storming workshops to distill business events, commands, personas, and bounded contexts from your prioritized user journeys.
Start with 2.3 Strategic event storming to build your core event maps. You’ll use the user journeys and use cases created during while defining your business capabilities, functions, and your roadmap. Strategic event storming should focus on those user journeys that have been prioritized.
Use a good tool. The best tools are walls, post-it notes, and non-permanent sharpie-style pens. But if you’re in a remote work environment, use a really good online white board, like Miro. Set up a good template, and pre-populate it with your user journeys, ubiquitous language, and a handy quick-reference chart. Miro has an excellent template ready to go.
Process
- Identify and sequence all events in the target use cases.
- Discuss and expand each event sequence to include commands leading up to events.
- Create personas, or actors, to trigger commands.
- Identify any open questions, risks or “hot spots” to make sure nothing falls through the cracks.
- Optionally, identify bounded contexts between events, personas, and subsystems (this detail can be added later, too).
Strategic event map reference
| Event map (link) | General use case | Key personas |
|---|---|---|
| [Link to event storming board] | Sally (Customer) purchases a product and finances the purchase with a loan from the bank. | Sally (Customer), Marcus (Bank Manager) |
| [Link to event storming board] | Sally applies for loan prequalification and receives an automated decision based on income, credit history, and risk score. | Sally (Customer), Eva (Underwriter) |
| [Link to event storming board] | Customer Service responds to a missed loan payment, contacts the borrower, and brings the account current under the bank’s collections policy. | Sally (Customer), Tom (Customer Service Rep) |
| … |