[{"data":1,"prerenderedAt":74},["ShallowReactive",2],{"help-article-event-storming":3},{"data":4},{"title":5,"excerpt":6,"content":7,"help_category":8,"seo":11},"Event Storming on a Whiteboard","Map a system flow by dragging real PD Models and analytics events onto a m18t whiteboard as entity nodes, then formalize the gaps in PD and the Events Manager.","\u003Cp>\u003Cstrong>What you'll learn\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>What event storming is and why a \u003Ca href=\"\u002Fhelp\u002Fwhiteboards-overview\">whiteboard\u003C\u002Fa> is a good place to do it.\u003C\u002Fli>\n\u003Cli>How to drag \u003Ca href=\"\u002Fhelp\u002Fthe-product-development-concept\">PD models\u003C\u002Fa> and \u003Ca href=\"\u002Fhelp\u002Fthe-analytics-event-registry\">analytics events\u003C\u002Fa> onto a board and connect them.\u003C\u002Fli>\n\u003Cli>How a loose board feeds the more formal structure in PD and the \u003Ca href=\"\u002Fhelp\u002Fthe-analytics-event-registry\">Events Manager\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2>What event storming is\u003C\u002Fh2>\n\u003Cp>Event storming is a way to map how a system behaves by laying out the events that happen and the data they touch — "user submits checkout" → which models change, what fires next. It's normally done with sticky notes on a wall. The weakness of the wall is that the stickies are just words; they don't connect to anything real.\u003C\u002Fp>\n\u003Cp>On a m18t \u003Ca href=\"\u002Fhelp\u002Fwhiteboards-overview\">whiteboard\u003C\u002Fa> you can do the same exercise but with \u003Cstrong>live records\u003C\u002Fstrong>. Drag your real \u003Ca href=\"\u002Fhelp\u002Fthe-product-development-concept\">PD Models\u003C\u002Fa> and your real \u003Ca href=\"\u002Fhelp\u002Fthe-analytics-event-registry\">analytics events\u003C\u002Fa> onto the canvas as \u003Ca href=\"\u002Fhelp\u002Fentity-nodes-vs-stickies\">Entity Nodes\u003C\u002Fa>, wire them with edges, and you've mapped the flow against things that actually exist in your workspace — each node showing its current status and clickable through to the record.\u003C\u002Fp>\n\u003Cp>This is most useful when you're designing or reviewing a flow: you can see the data (Models) and the moments (Events) in one picture, and notice gaps — an event with no model behind it, a model nothing fires against.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>How to do it\u003C\u002Fh2>\n\u003Col>\n\u003Cli>Create or open a \u003Ca href=\"\u002Fhelp\u002Fwhiteboards-overview\">whiteboard\u003C\u002Fa> for the right \u003Ca href=\"\u002Fhelp\u002Fthe-brand-switcher\">brand\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Open the \u003Cstrong>Studio Entities\u003C\u002Fstrong> panel from the canvas toolbar (the orbit button).\u003C\u002Fli>\n\u003Cli>Filter to \u003Cstrong>Product Dev → Models\u003C\u002Fstrong> and drag the Models in your flow onto the canvas.\u003C\u002Fli>\n\u003Cli>Switch the filter to \u003Cstrong>Events\u003C\u002Fstrong> and drag the relevant \u003Ca href=\"\u002Fhelp\u002Fthe-analytics-event-registry\">analytics events\u003C\u002Fa> on too.\u003C\u002Fli>\n\u003Cli>Connect the nodes with edges to show the order of the flow — what triggers what, which event touches which model.\u003C\u002Fli>\n\u003Cli>Annotate with plain \u003Ca href=\"\u002Fhelp\u002Fentity-nodes-vs-stickies\">stickies, shapes, or text\u003C\u002Fa> where you need commentary the records don't carry.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The board autosaves as you go. Come back to it and the layout and the entity statuses are current.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>From a loose board to real structure\u003C\u002Fh2>\n\u003Cp>A board is for the messy, exploratory phase. It doesn't \u003Cem>create\u003C\u002Fem> PD or event records — you drag existing ones on. So the flow usually goes:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Sketch on a board\u003C\u002Fstrong> — drag on what exists, use stickies for what doesn't yet, find the gaps.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Formalize in PD\u003C\u002Fstrong> — for missing data, add the \u003Ca href=\"\u002Fhelp\u002Fyour-first-solution\">Models and Attributes\u003C\u002Fa> in the Product Manager tables.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Register events\u003C\u002Fstrong> — define new events in the \u003Ca href=\"\u002Fhelp\u002Fthe-analytics-event-registry\">Events Manager\u003C\u002Fa>; they're a PD entity, but authored there.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Re-map\u003C\u002Fstrong> — drag the now-real records back onto the board to confirm the flow holds.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Once the structure is real, the \u003Ca href=\"\u002Fhelp\u002Fthe-dependency-graph\">Event Flow tab\u003C\u002Fa> in PD's Visual Analysis gives you a generated view of how events connect to controllers and models — the formal counterpart to the board you sketched by hand.\u003C\u002Fp>\n\u003Cp>A beta note: events on a board are entity nodes you drag on, not something the board generates or instruments. Wiring an event to code is a separate step covered under \u003Ca href=\"\u002Fhelp\u002Fthe-analytics-event-registry\">the event registry\u003C\u002Fa>. The board is for mapping, not for emitting.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>FAQ\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Does dragging an event onto a board create or fire that event?\u003C\u002Fstrong>\nNo. Entity Nodes reference existing records. The board maps events; it doesn't define or emit them. Define events in the \u003Ca href=\"\u002Fhelp\u002Fthe-analytics-event-registry\">Events Manager\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Can I put both Models and Events on the same board?\u003C\u002Fstrong>\nYes — that's the point. Filter the Studio Entities panel to Models, drag them on, switch to Events, drag those on, and connect them.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What if a model or event doesn't exist yet?\u003C\u002Fstrong>\nUse a plain \u003Ca href=\"\u002Fhelp\u002Fentity-nodes-vs-stickies\">sticky or shape\u003C\u002Fa> as a placeholder, then create the real record in \u003Ca href=\"\u002Fhelp\u002Fyour-first-solution\">PD\u003C\u002Fa> or the \u003Ca href=\"\u002Fhelp\u002Fthe-analytics-event-registry\">Events Manager\u003C\u002Fa> and drag it on once it exists.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Is there an automatic version of this?\u003C\u002Fstrong>\nFor records you've already modeled, the \u003Ca href=\"\u002Fhelp\u002Fthe-dependency-graph\">Event Flow tab\u003C\u002Fa> in Visual Analysis renders events against their controllers and models. The whiteboard is the free-form, design-time version.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Why are my entities missing from the panel?\u003C\u002Fstrong>\nCheck the \u003Ca href=\"\u002Fhelp\u002Fthe-brand-switcher\">brand\u003C\u002Fa> — boards and the entities you can drag on are brand-scoped.\u003C\u002Fp>\n\u003Chr>\n\u003Cp>\u003Cstrong>What's next\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fthe-analytics-event-registry\">The Analytics Event Registry\u003C\u002Fa> — where events are defined.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fentity-nodes-vs-stickies\">Entity Nodes vs. Stickies\u003C\u002Fa> — the node types you'll combine.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fthe-dependency-graph\">The Dependency Graph\u003C\u002Fa> — the generated Event Flow view.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fyour-first-solution\">Your First Solution\u003C\u002Fa> — formalize the models you sketched.\u003C\u002Fli>\n\u003C\u002Ful>\n",{"slug":9,"title":10},"whiteboards-help","Whiteboards",{"meta_title":12,"meta_description":6,"keywords":13,"canonical_url":14,"og_title":12,"og_description":6,"og_image":15,"robots":16,"json_ld":17},"Event Storming on a Whiteboard | m18t Help","event storming, whiteboard, PD models, analytics events, entity nodes, flow mapping, event flow, studio entities, m18t","https:\u002F\u002Fm18t.com\u002Fhelp\u002Fevent-storming","https:\u002F\u002Fm18t.com\u002Fog-default.png","index, follow",{"@context":18,"@graph":19},"https:\u002F\u002Fschema.org",[20,33,58],{"@type":21,"headline":5,"description":6,"articleSection":10,"inLanguage":22,"datePublished":23,"dateModified":23,"image":15,"author":24,"publisher":28,"mainEntityOfPage":31},"Article","en","2026-06-25",{"@type":25,"name":26,"url":27},"Organization","m18t","https:\u002F\u002Fm18t.com",{"@type":25,"name":26,"url":27,"logo":29},{"@type":30,"url":15},"ImageObject",{"@type":32,"@id":14},"WebPage",{"@type":34,"mainEntity":35},"FAQPage",[36,42,46,50,54],{"@type":37,"name":38,"acceptedAnswer":39},"Question","Does dragging an event onto a board create or fire that event?",{"@type":40,"text":41},"Answer","No. Entity Nodes reference existing records. The board maps events; it doesn't define or emit them. Define events in the Events Manager.",{"@type":37,"name":43,"acceptedAnswer":44},"Can I put both Models and Events on the same board?",{"@type":40,"text":45},"Yes — that's the point. Filter the Studio Entities panel to Models, drag them on, switch to Events, drag those on, and connect them.",{"@type":37,"name":47,"acceptedAnswer":48},"What if a model or event doesn't exist yet?",{"@type":40,"text":49},"Use a plain sticky or shape as a placeholder, then create the real record in PD or the Events Manager and drag it on once it exists.",{"@type":37,"name":51,"acceptedAnswer":52},"Is there an automatic version of this?",{"@type":40,"text":53},"For records you've already modeled, the Event Flow tab in Visual Analysis renders events against their controllers and models. The whiteboard is the free-form, design-time version.",{"@type":37,"name":55,"acceptedAnswer":56},"Why are my entities missing from the panel?",{"@type":40,"text":57},"Check the brand — boards and the entities you can drag on are brand-scoped.",{"@type":59,"itemListElement":60},"BreadcrumbList",[61,65,69,72],{"@type":62,"position":63,"name":64,"item":27},"ListItem",1,"Home",{"@type":62,"position":66,"name":67,"item":68},2,"Help","https:\u002F\u002Fm18t.com\u002Fhelp",{"@type":62,"position":70,"name":10,"item":71},3,"https:\u002F\u002Fm18t.com\u002Fhelp\u002Fcategories\u002Fwhiteboards-help",{"@type":62,"position":73,"name":5,"item":14},4,1786312171926]