Grocery Order Event Storming
This event storming diagram maps a grocery delivery order from checkout to delivery. Blue nodes are commands that request work, orange nodes are facts that happened, and the green node is a policy that reacts to the order being placed. The simple chain is a useful opening model because the group can ask where exceptions, ownership, and external systems belong. In a workshop, add cancellation, substitutions, out-of-stock handling, and refund events only after the happy path is agreed. Keep the event names concrete and in the past tense so participants can distinguish a recorded business fact from an instruction. Review the underlying definitions and totals before using this view to make an operational decision.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
Grocery delivery domain discovery
Key decisions
- Name facts: Keep events in past tense.
- Separate triggers: Show commands separately from events.
- Expose policy: Make payment authorization explicit.
When to reuse this
Use for a chronological workshop map of a bounded business process.
Frequently asked questions
Why are events orange?
What is the payment policy?
Where do exceptions go?
Tweak it with chat, export PNG/SVG, or fork it for your own use case.