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

Worked example — vendor onboarding change

22 steps, 4 phases, 6 context segments. Scroll right.
Phase 1 · Intake 4
Phase 2 · Assessment 8
Phase 3 · Execution 6
Phase 4 · Closure 4
Timeline aggregates · commands · events · policies
Intake & Triage ·1/2
Intake & Triage ·2/2
Risk & Compliance ·1/2
Risk & Compliance ·2/2
Finance
Scheduling
Vendor Master Data
Change Execution
UNKNOWN · ASK TOM

Nothing connects the CAB decision to Scheduling.

OPEN SINCE 2026-08-24

Change Request
AGGREGATE · G-001 MK
Risk Assessment
AGGREGATE · G-002 MK
Change Window
AGGREGATE · G-003 MK
Vendor
AGGREGATE · G-004 MK
Requesting manager
ACTOR · A-001 MK
Service desk
ACTOR · A-002 MK
Risk analyst
ACTOR · A-003 MK
Finance partner
ACTOR · A-004 MK
CAB chair
ACTOR · A-005 MK
Change manager
ACTOR · A-006 MK
MDM steward
ACTOR · A-007 MK
Platform engineer
ACTOR · A-008 MK
Submit change request
COMMAND · C-001 MK
Change request submitted 2
EVENT · E-002 MK
Triage request
COMMAND · C-003 MK
Request accepted for assessment
PIVOTAL · E-004 MK
Assess vendor risk
COMMAND · C-005 MK
Risk rating assigned
EVENT · E-006 MK
Request security review
COMMAND · C-007 MK
Security review passed
EVENT · E-008 MK
Reserve budget
COMMAND · C-009 MK
Budget reserved
EVENT · E-010 MK
Approve change 2
COMMAND · C-011 MK
Change approved by CAB
PIVOTAL · E-012 MK
Schedule change window
COMMAND · C-013 MK
Window scheduled
EVENT · E-014 MK
Create vendor record
COMMAND · C-015 MK
Vendor record created
EVENT · E-016 MK
Implement change
COMMAND · C-017 MK
Change implemented in production
PIVOTAL · E-018 MK
Activate vendor
COMMAND · C-019 MK
Vendor activated in master data
EVENT · E-020 MK
Close change request
COMMAND · C-021 MK
Change request closed
EVENT · E-022 MK
Whenever a request is submitted, assign a triage owner
POLICY · P-001 MK
Whenever risk is rated high, route to CAB
POLICY · P-002 MK
Whenever a window is set, freeze conflicting changes
POLICY · P-003 MK
Whenever verification fails, reopen the request
POLICY · P-004 MK
Finance re-checks the budget
EVENT · E-023 MK
Re-run credit check
COMMAND · C-024 MK
Emergency change routed as a standard change
EVENT · E-025 MK
Systems & data external systems · read models
ServiceNow
EXTERNAL · X-001 MK
Triage queue
READ MODEL · R-01 MK
Archer GRC
EXTERNAL · X-002 MK
SAP · budget
EXTERNAL · X-003 MK
Risk register
READ MODEL · R-02 MK
CAB agenda
READ MODEL · R-03 MK
SAP MDG
EXTERNAL · X-004 MK
Jira Service Mgmt
EXTERNAL · X-005 MK
Freeze calendar
READ MODEL · R-04 MK
Vendor master
READ MODEL · R-05 MK
Audit trail
READ MODEL · R-06 MK
Friction free zone — hotspots, questions, opportunities
UNKNOWN · ASK PROCUREMENT

How does the vendor appear in ERP? Ask procurement.

OPEN SINCE 2026-08-19

Two intake channels, one SLA clock
HOTSPOT · H-01 MK
Who triages on holidays?
OPEN QUESTION · Q-001 MK
Risk rating redone by hand after each scope change
HOTSPOT · H-02 MK
Auto-approve low-risk vendors
OPPORTUNITY · O-001 MK
Does finance re-check the budget after CAB?
OPEN QUESTION · Q-002 MK
Windows collide with month-end close
HOTSPOT · H-03 MK
Stop re-keying vendor data into MDG
OPPORTUNITY · O-002 MK
Who confirms the vendor is paid on time?
OPEN QUESTION · Q-003 MK
IF RISK IS HIGH IF VERIFICATION FAILS
scroll right · click a sticky to select, ⇧-click to add · click an arrow to select the run · click a lane header to collapse it · the − on a region tab folds the context away, and EXPAND on the block unfolds it
Isolate a type

Legend

click a row to isolate that type

counts are read off the model, so they are what §10 currently earns
  • Context ≠ phase Intake & Triage matches Phase 1 exactly. Risk & Compliance is narrower than Assessment and Change Execution runs straight through the Phase 3 divider.
  • Recurring contexts Intake & Triage and Risk & Compliance each appear twice — steps 01–04 and 21–22, 05–08 and 11–12 — under one name, numbered ·1/2 and ·2/2.
  • Boundary crossings Where a connector leaves a region a hollow square marks the crossing — hollow with a ? until somebody writes the contract, ink-filled with the pattern’s initial once they have. Ownership decides which runs get one, so the runs out to SAP and Jira, which land in no context at all, get none.
  • The long jumps Only four arrows run any distance: high risk skipping to CAB approval, the freeze calendar being read at implementation, and the reopen loop from step 20 back to triage at 03.
the source draws these four notes in four columns; RuleList offers one, two or three, so they run two-up here§10’s long-arrow annotation ("REOPENS AT 03") is prose over the figure (INVENTORY §6) and is not drawn