Event Storming

Comment l'animer

1. 1

   Set up a very long continuous paper surface (6–10 metres of wall space).

2. 2

   Explain the colour coding: orange = domain events (past tense: 'Order Placed', 'Payment Failed'), blue = commands, yellow = actors/users, red = hotspots (questions, conflicts).

3. 3

   Start with chaotic exploration: everyone simultaneously places orange events on the timeline without structure.

4. 4

   Sort events into chronological order. Discuss and resolve conflicts.

5. 5

   Add commands (what triggers each event?) and actors (who issues the command?).

6. 6

   Place red hotspot notes wherever there is confusion, disagreement, or missing information.

7. 7

   Cluster events into bounded contexts — these become the system boundaries.

8. 8

   Use hotspots as input for follow-up design sessions.

Conseils

• The mess is part of the process — the first pass will be chaotic.

• That's correct.

• Hotspots are the most valuable output: they mark the places where assumptions haven't been tested.

• Include both domain experts and technical staff — the mix is essential.',

Variantes

Run a 'Big Picture' Event Storming (whole business) before a 'Process Level' session (single flow). Use digitally with colour-coded cards in Miro for distributed teams.