[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-572346-105":53,"doc-detail-572346-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","cheat-sheet-for-event-storming-big-picture-workshop-practical-steps","Cheat Sheet for Event-Storming Big Picture Workshop - Practical Steps","","Pragmatic cheat sheet for conducting event-storming workshops, focused on the “Big Picture” level and outlining preparation, wall and materials requirements, and a whiteboard legend to avoid confusion. It provides a step-by-step sequence of domain events, hot spots, enforcing a timeline, pivotal elements, actors, systems, storytelling with narrative switching, and capturing opportunities and future candidates. It also covers how to extend into design-level event storming with commands and aggregates.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/cheat-sheet-for-event-storming-big-picture-workshop-practical-steps/572346/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/cheat-sheet-for-event-storming-big-picture-workshop-practical-steps/572346.png","ImageObject",442,249,{"name":88,"@type":89},"Taylor Morgan","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-19","2026-10-13",true,{"@type":98,"interactionType":99,"userInteractionCount":73},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What are the location requirements for a Big Picture event-storming workshop?","Question",{"text":108,"@type":109},"Use a sufficiently long wall (about 5m) or at least 3 Metaplan walls next to each other. Bring assorted super-sticky Post-its, plus fruit and drinks, and clear chairs/tables away so participants can stand and discuss while moving around.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What should you do during the “Hot Spots” step?",{"text":113,"@type":109},"Capture pressing questions, inconsistencies, and how an event occurs before/during/after the IT system usage. Express the event with a past-tense verb and keep the ordering chronological, involving relevant domain experts.",{"name":115,"@type":106,"acceptedAnswer":116},"How can you extend the approach to a design-level event storming?",{"text":117,"@type":109},"Continue using the relevant stickies, especially for Commands and Aggregates. Commands are in present tense and imperative and can originate from user, system, domain events, or unspecified sources, while Aggregates follow the DDD notion of important domain business objects.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},572346,1792430350,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":73,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":76,"language":135,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":61,"update_tm":139,"read_time":9},1099523885336,"https://ap-avatar.wpscdn.com/davatar_276721f389ce27ea32af1340a28f341c","Cheat Sheet for Event-Storming Big Picture Workshop  \nThe following document describes a pragmatic “cheat sheet” for event-storming workshops. The information refers to the (highly recommended) book by the event-storming \"inventor\" Alberto Brandolini: Brandolini, A. (2015) . Introducing EventStorming. Leanpub. [https://leanpub.com/introduc](https://leanpub.com/introduc)ing eventstorming  \nRequirements on the location  \n• Sufficiently long wall (5m) or at least 3 Metaplan walls next to each other  \n• Assorted Post-Its (see below)– “super sticky” preferred  \n• Fruit and drinks  \n• Chairs and tables cleared away if possible-participants need (a) space to move around, and should (b) not be able to sit down directly (at least not in front of the event storming wall) . Discussions should take place while standing.  \nLegend  \nThe legend should be written to a whiteboard. Just one sticky type at a time, otherwise you confuse people. The following sequence describes the usual steps for a “Big Picture” workshop.  \n1. Domain Events  \nItem added to cart  \n2. Hot Spots  \nHow is the tax determined?  \n• Event before / during / after use of the IT system  \n• Verb in the past tense  \n• Relevant to domain experts  \n• Chronological order!  \n• Pressing questions  \n• Inconsistencies  \n• Don’t look for them – just note them if you consider them important!  \n3. Enforcing timeline  \nOrder the domain events so that they signify a sequential flow of events.  \n4.  \nPivotal Elements  \n• The few most significant events in the flow Often  \n•  \nthe events with the experts interested  \nhighest number of domain  \n5.  \nActors  \n•  \ncan be concrete people or roles  \n•  \nevent  \nsomething like “angry customer” may help  \n6.  \nSystems  \n• IT  \nsystem outside our own control  \ncan belong to another company ([e.g. credit](e.g. credit) card system)  \n•  \n•  \ncan also be internal, but outside  \nscope of our  \nproject  \n7. Tell the story (narrator) Let the teams tell the story. Switch at pivotal elements.  \n8.  \nOpportunities  \n•  \n•  \nMark ideas that may be beyond your scope right now Candidates for future developments and releases  \nCustomer  \nPartner Management System  \nWe could use AI to do this!  \nCheat Sheet for Design-Level Workshop  \nSometimes it makes sense to continue into the design level with the event storming approach. Those relevant stickies to be used there.  \n1. Commands  \n• Can come from user, system, domain event, or unspecified  \n• Can be directed at a system or aggregate  \n• Present tense, imperative  \n2. Aggregates  \nProduct  \n• Aggregate as in the DDD sense  \n• “Important domain business object”  \n• don’t try to be “final” in naming – that can come later","cbCaioSMScweNPf2","https://ap.wps.com/l/cbCaioSMScweNPf2","pdf",232837,"English","# Cheat Sheet for Event-Storming Big Picture Workshop\n## Requirements on the location\n## Legend and workshop sequence\n### Domain Events\n### Hot Spots\n### Enforcing timeline\n### Pivotal Elements\n### Actors\n### Systems\n### Tell the story (narrator)\n### Opportunities\n# Cheat Sheet for Design-Level Workshop\n## Commands\n## Aggregates","[{\"question\":\"What are the location requirements for a Big Picture event-storming workshop?\",\"answer\":\"Use a sufficiently long wall (about 5m) or at least 3 Metaplan walls next to each other. Bring assorted super-sticky Post-its, plus fruit and drinks, and clear chairs/tables away so participants can stand and discuss while moving around.\"},{\"question\":\"What should you do during the “Hot Spots” step?\",\"answer\":\"Capture pressing questions, inconsistencies, and how an event occurs before/during/after the IT system usage. Express the event with a past-tense verb and keep the ordering chronological, involving relevant domain experts.\"},{\"question\":\"How can you extend the approach to a design-level event storming?\",\"answer\":\"Continue using the relevant stickies, especially for Commands and Aggregates. Commands are in present tense and imperative and can originate from user, system, domain events, or unspecified sources, while Aggregates follow the DDD notion of important domain business objects.\"}]","Cheat Sheet for Event-Storming Big Picture Workshop - Practical Steps | PDF",1791926867]