Design system / rev A

Event Storming Board

A modelling surface for change-management requests. The chrome is monochrome steel on paper; all color in the product belongs to the sticky grammar, so the timeline reads as a legend at a glance. Conventions follow eventstorming.com, adapted where the digital medium can do better than a paper wall.

base
Industry
ground
#f2f2f3
steel
#5980a6
grid
8px / lane 208

Panels

Where async rigor lives: detail, discussion, and the facilitator's review queue.
Detail

Detail

E-002
Change request submitted 2
EVENT · E-002 MK
Type
Domain event
Aggregate
Change Request
Triggered by
Submit change request
Added
MK

Notes

Includes requests raised by e-mail and re-keyed by the service desk — same event, different channel.

Discussion

Discussion

2 OPEN
MK Marta K · 14 AUG

Is the re-keyed e-mail path really the same event? Different SLA start.

DA Dana A · 15 AUG

Splitting it. Raised a question sticky in the parking lot.

Review queue

Review queue

21 ITEMS
The facilitator's rigor, made async: gaps are surfaced, never auto-filled.
the queue is derived from the model on every read, so its count is whatever §10 currently earns rather than the figure’s printed 7so is the discussion’s open count — resolve this thread and 2 OPEN reads 1, because both are one read of the same board