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

Non-linear flow

Parallel tracks inside a context. Structure that guides, not a grid that traps.

Real processes fork, run in parallel, fail and loop. The board keeps one rule from the linear reading — time runs left to right — and drops the rest: inside a context region a sticky can sit on any track, tracks are created by dropping a sticky in empty space below an existing one, and regions grow to fit. The global lanes from section 05 stay as rails at the bottom of the canvas for systems and friction; everything above them is free.

Request accepted for assessment
PIVOTAL · E-004 MK
Risk & Compliance
Track · Vendor risk
ALWAYS
Assess vendor risk
COMMAND · C-005 MK
Risk rating assigned
EVENT · E-006 MK
Track · Security
IF NEW
Request security review
COMMAND · C-007 MK
Security review passed
EVENT · E-008 MK
Track · Budget
IF SPEND > $50K
Reserve budget
COMMAND · C-009 MK
Budget reserved
EVENT · E-010 MK
EACH SUBSIDIARY
Join — all three
Approve change
COMMAND · C-011 MK
Change approved by CAB
PIVOTAL · E-012 MK
the region, the stickies, the arrows and all five marks are shipped components; only the coordinates are this page’s
New marks
  • Fork dot One source, several outgoing arrows. Every branch needs a guard.
  • IF SPEND > $50K
    Guard chip The condition, in the author's own words. Unlabelled branches go to the review queue.
  • Join — all three
    Join bar Tracks that must all complete before the next step. A bar with one output, never a pile of arrowheads.
  • EACH SUBSIDIARY
    Iterator badge "For each …" on the sticky itself, rather than a step that repeats the timeline.
  • Track · Vendor risk
    Track label Mono, top-left inside the region. Tracks are named, ordered top to bottom, and can be reordered or collapsed.
  • Free, but not loose Free placement inside a region; the region itself snaps to the 8px grid and to its neighbours’ edges, so the board stays legible when four people work in it at once.
  • Time stays horizontal The only hard constraint: a sticky may not sit left of something it depends on. Break it and the connector turns into the loop-back style, which is honest rather than wrong.
  • Regions nest A region can hold sub-regions one level deep — enough for "Assessment / Security" without becoming a folder tree.
  • Why not colored frames Miro-style colored regions compete with the sticky grammar. Regions stay dashed steel-grey; identity comes from the label, not the hue.