ChatDiagram
Tools/Event storming diagram maker

Event storming diagram maker.

Turn a business process into an event storming diagram with color-coded commands, domain events, policies, and aggregates. Describe the process in time order, then refine the model with the people who know the domain.

FlowchartEnter to send

Free account, no card · Export SVG, PNG or PDF

See it work

Event storming diagram examples.

Same tool, four requests. Every drawing below is a real render.

What you type
Create an event storming diagram for an online grocery order: Place order causes Order placed; authorize payment causes Payment authorized; reserve items causes Items reserved; pick order causes Order picked; dispatch delivery causes Order delivered. Color commands blue, events orange, and the payment policy green.
Then tryAdd a Payment declined event and an order cancellation command.Add an Order aggregate beside the first event.
Flowchart: Grocery order
Flowchart · Sugiyama layered DAG + orthogonal routing · schematex-flowchart

Rather start from a finished drawing? Browse 1200 flowchart templates →

The drawing

What an event storming diagram is.

Event storming is a collaborative domain-modeling practice that maps what has happened in a business process. The map usually starts with domain events in time order, then adds the commands that caused them, the policies that react, and the aggregates that own the change.

It is most useful as a shared working model, not as a final system specification. Keep event names in the past tense, command names as actions, and discuss gaps or disagreements with domain experts.

Standard
Sugiyama layered DAG + orthogonal routing
Engine
schematex-flowchart
Editable
Double-click text, drag nodes
Export
SVG · PNG · PDF
Flowchart: What an event storming diagram is
Who uses it

Who uses event storming diagrams.

Flowchart: Product and engineering teamsProduct and engineering teams

Find the commands, events, and policy decisions in an online ordering flow before designing services.

Flowchart: Healthcare operations teamsHealthcare operations teams

Map appointment booking and reminder steps with clinical and administrative stakeholders.

Flowchart: Commerce teamsCommerce teams

Clarify return and refund responsibilities across support, warehouse, and payment systems.

How it works

How to make an event storming diagram in three steps.

01

Describe it

One paragraph is enough to start.

“Create an event storming diagram for an online grocery order: Place order causes Order placed; authorize payment causes Payment authorized; reserve items causes Items reserved; pick order causes Order picked; dispatch delivery causes Order delivered. Color commands blue, events orange, and the payment policy green.”
02

See the drawing

Drawn by the right engine.

Flowchart: Grocery order
03

Say what changes

Every edit keeps a version.

Add a Payment declined event and an order cancellation command.
V2 · DRAWN FROM V1, NOTHING RETYPED
FAQ

Common questions

What is an event storming diagram?

It is a visual map of a business domain that connects domain events with the commands, policies, people, and aggregates around them.

What is the difference between a command and an event?

A command asks for an action, such as Place Order. An event records a fact that occurred, such as Order Placed.

Who should join an event storming session?

Include domain experts, product owners, engineers, and people who operate or support the process. Different perspectives expose missing rules.

How should I begin an event storming map?

Start by placing important domain events in chronological order. Add commands that cause them, then policies and aggregates where the group needs more context.

Related tools

Other drawings for the same work.

Map your domain now.

Free account, no card. Describe the process and its important business events.

Open the editor