Learning objective
Discover a domain process collaboratively by arranging meaningful events in time.
Why it matters
Specialists hold incompatible versions of a workflow, while software requirements hide exceptions.
Core concept
Participants write past-tense domain events, order them, mark hotspots and decisions, then identify commands, actors and boundaries. The wall is a discovery artifact, not a complete executable design.
Scenario
A food-delivery platform believes refunds start with customer complaints, but warehouse staff report that stock substitutions occur before the customer is notified.
Worked decision
Map order accepted, item unavailable, substitute chosen, notice sent, consent received and refund issued; expose the missing consent event.
Decision rule
Validate with real cases and turn hotspots into questions.
Ethical boundary
Turning the workshop into a software architecture debate before participants agree on what happens.
AI lens
Use AI to organize evidence, then verify its source and keep decision authority with people.
Quick check
What would invalidate the first proposed action? Turning the workshop into a software architecture debate before participants agree on what happens.
Next step
Complete the EventStorming case.