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

Bounded context canvas

Drill into one region. The ddd-crew canvas v5 layout, in this system's hand.

Inbound and outbound messages are the region’s actual crossing arrows, so the canvas fills itself from the board and only the prose fields need a person.

NAME

Risk & Compliance

BOUNDED CONTEXT CANVAS V5
github.com/ddd-crew/bounded-context-canvas · CC BY CR-2291

PURPOSE

Decide whether a proposed change may proceed, and record why. Owns risk rating, security review and CAB routing for every change request; owns nothing about scheduling or vendor data.

STRATEGIC CLASSIFICATION

DOMAIN
CORE DomainClass, 3 of 3
BUSINESS MODEL
COMPLIANCE BusinessModel, 1 of 3
EVOLUTION
CUSTOM BUILT Evolution, 2 of 4

DOMAIN ROLES

ANALYSIS CONTEXT DomainRole, 1 of 3

INBOUND COMMUNICATION

COLLABORATORMESSAGE
Finance Budget reserved

UBIQUITOUS LANGUAGE

Words that mean something specific here

TERMMEANINGSTATE
Emergency change— not named —UNDEFINED
CABChange advisory board. Meets Tuesday and Thursday; quorum of three, one of whom must be from Security.CLASHES
Risk ratingLow, medium or high. Set when the request is assessed and recalculated on any scope change.DEFINED
Standard changeA pre-approved change pattern. Skips CAB, but never skips security review.DEFINED

BUSINESS DECISIONS

High risk always goes to CAB, no exceptions for emergencies.A standard change auto-approves once security review passes.A failed security review reopens the request at triage.

OUTBOUND COMMUNICATION

MESSAGECOLLABORATOR
Finance Security review passed
Scheduling Change approved by CAB
Finance Change approved by CAB

ASSUMPTIONS

  1. Risk rating redone by hand after each scope change IN QUEUE
  2. Finance re-checks the budget ASSUMED
  3. Emergency change routed as a standard change ASSUMED

VERIFICATION METRICS

Share of changes routed to CAB 31%
Median days in assessment 6.4
Reopen rate after approval 9%

OPEN QUESTIONS

— none open —

RISK & COMPLIANCE — §14’S OWN REGION, READ OUT OF §10’S BOARDELEVEN FIELDS · FIVE OF THEM DERIVED, SIX OF THEM PROSE ON THE MODEL
NAME

Intake & Triage

BOUNDED CONTEXT CANVAS V5
github.com/ddd-crew/bounded-context-canvas · CC BY CR-2291

PURPOSE

Take a change request in through either channel and decide whether it is worth assessing.

STRATEGIC CLASSIFICATION

DOMAIN
SUPPORTING DomainClass, 2 of 3
BUSINESS MODEL
COST REDUCTION BusinessModel, 3 of 3
EVOLUTION
PRODUCT / RENTAL Evolution, 3 of 4

DOMAIN ROLES

GATEWAY CONTEXT DomainRole, 2 of 3

INBOUND COMMUNICATION

COLLABORATORMESSAGE
ServiceNow ServiceNow
Change Execution Audit trail
Change Execution Vendor activated in master data
Change Execution Whenever verification fails, reopen the request

UBIQUITOUS LANGUAGE

Words that mean something specific here

— no words marked here yet —

BUSINESS DECISIONS

— none written down —

OUTBOUND COMMUNICATION

MESSAGECOLLABORATOR

— nothing crosses here yet —

ASSUMPTIONS

  1. Two intake channels, one SLA clock IN QUEUE

VERIFICATION METRICS

— not measured —

OPEN QUESTIONS

Who triages on holidays?
INTAKE & TRIAGE — THE SAME ELEVEN FIELDS
NAME

Scheduling

BOUNDED CONTEXT CANVAS V5
github.com/ddd-crew/bounded-context-canvas · CC BY CR-2291

PURPOSE

Find a window that collides with nothing else.

STRATEGIC CLASSIFICATION

DOMAIN
GENERIC DomainClass, 1 of 3
BUSINESS MODEL
NOT RANKED BusinessModel, 0 of 3
EVOLUTION
COMMODITY Evolution, 4 of 4

DOMAIN ROLES

EXECUTION CONTEXT DomainRole, 3 of 3

INBOUND COMMUNICATION

COLLABORATORMESSAGE
Risk & Compliance Change approved by CAB

UBIQUITOUS LANGUAGE

Words that mean something specific here

— no words marked here yet —

BUSINESS DECISIONS

— none written down —

OUTBOUND COMMUNICATION

MESSAGECOLLABORATOR
Change Execution Freeze calendar
Vendor Master Data Window scheduled
Change Execution Whenever a window is set, freeze conflicting changes

ASSUMPTIONS

  1. Windows collide with month-end close IN QUEUE

VERIFICATION METRICS

— not measured —

OPEN QUESTIONS

— none open —

SCHEDULING — THE SAME ELEVEN FIELDS
NAME

ServiceNow

BOUNDED CONTEXT CANVAS V5
github.com/ddd-crew/bounded-context-canvas · CC BY CR-2291

PURPOSE

— not written yet —

STRATEGIC CLASSIFICATION

DOMAIN
NOT RANKED DomainClass, 0 of 3
BUSINESS MODEL
NOT RANKED BusinessModel, 0 of 3
EVOLUTION
NOT RANKED Evolution, 0 of 4

DOMAIN ROLES

NOT RANKED DomainRole, 0 of 3

INBOUND COMMUNICATION

COLLABORATORMESSAGE

— nothing crosses here yet —

UBIQUITOUS LANGUAGE

Words that mean something specific here

— no words marked here yet —

BUSINESS DECISIONS

— none written down —

OUTBOUND COMMUNICATION

MESSAGECOLLABORATOR
Intake & Triage ServiceNow

ASSUMPTIONS

— none recorded —

VERIFICATION METRICS

— not measured —

OPEN QUESTIONS

— none open —

SERVICENOW — THE SAME ELEVEN FIELDS
Intake & Triage carries the open questions Risk does not; Scheduling has no business model, so that axis draws §19’s unset chip; ServiceNow sits outside our boundary and has no strategic rank at all.
Rules
  • Faithful to the canvas Same eleven fields, same reading order, same v5 attribution. Only the drawing changes: square cells, hairline rules, condensed headings.
  • Messages keep their hue Events orange, commands blue, queries green — the canvas inherits the board’s grammar rather than inventing a second one.
  • Assumptions and questions round-trip Whatever sits in Assumptions and Open Questions here is the same object as the dashed sticky and the question sticky on the board.