[{"data":1,"prerenderedAt":72},["ShallowReactive",2],{"content-guides-eventstorming-invitations":3},{"markdown":4,"frontMatterAttributes":5,"bodyRaw":8,"contributorPaths":9,"menuType":11,"contentName":12,"slug":13,"readingTime":14,"menu":15,"nextDocItem":29,"previousDocItem":18},"\u003Ch1>Inviting the right people\u003C\u002Fh1>\n\u003Cp>Before anything else it's critical to find and get buy-in from a diverse set of domain experts from\nacross your organization. A domain expert is anyone with knowledge of the business domain that\nyou'll be EventStorming. Domain experts can reside anywhere in your organization and are independent\nfrom job role and title.\u003C\u002Fp>\n\u003Cblockquote>\n  \u003Cp>\n    To run a successful workshop, you'll need to have the right people on board: a mix of knowledge\n    and curiosity, but most of all you'll need \u003Cb>people that care about the problem.\u003C\u002Fb>\n  \u003C\u002Fp>\n  \u003Cdiv>\n    - Alberto Brandolini, \u003Ca href=\"https:\u002F\u002Fwww.eventstorming.com\u002Fbook\u002F\">EventStorming creator\u003C\u002Fa>\n  \u003C\u002Fdiv>\n\u003C\u002Fblockquote>\n\n\u003Cul>\n\u003Cli>Bringing people together from various departments (sales, marketing, product, engineering,\ncustomer support, etc) helps you to capture the entire end-to-end flow. Rarely does a single\nperson know \u003Cem>everything\u003C\u002Fem> across a workflow. Different people may know the start, middle, or end of\na business process. Together, the team will arrive at a shared understanding using their\ncollective knowledge.\u003C\u002Fli>\n\u003Cli>Different people will spot different potential issues or opportunities. Someone from engineering\nmay focus on technical constraints, while someone from UX may see usability issues. A broad set of\neyes helps identify more areas for improvement.\u003C\u002Fli>\n\u003Cli>Getting buy-in across the organization is crucial for driving change after EventStorming\nworkshops. Having representatives from various teams participate makes them feel ownership in the\nprocess and outcome. They can become advocates for implementing improvements.\u003C\u002Fli>\n\u003Cli>You want a balance of senior stakeholders who have authority and experience, as well as\non-the-ground staff who know low-level details. EventStorming helps to make connections between\nyour business and engineering.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>EventStorming should \u003Cem>not\u003C\u002Fem> be run by a single team or individual. An engineering or product team\nrunning EventStorming by themselves will miss the key benefits. Cross-team communication and\nunderstanding are the main benefits of EventStorming.\u003C\u002Fp>\n\u003Cp>The right mix of people leads to a richer picture of the current state, alignment on future vision,\nand shared commitment to executing on the ideas generated. Cross-functional collaboration is\ncritical.\u003C\u002Fp>\n",{"title":6,"order":7},"Step 1 - Invitations",10,"# Inviting the right people\n\nBefore anything else it's critical to find and get buy-in from a diverse set of domain experts from\nacross your organization. A domain expert is anyone with knowledge of the business domain that\nyou'll be EventStorming. Domain experts can reside anywhere in your organization and are independent\nfrom job role and title.\n\n\u003Cblockquote>\n  \u003Cp>\n    To run a successful workshop, you'll need to have the right people on board: a mix of knowledge\n    and curiosity, but most of all you'll need \u003Cb>people that care about the problem.\u003C\u002Fb>\n  \u003C\u002Fp>\n  \u003Cdiv>\n    - Alberto Brandolini, \u003Ca href=\"https:\u002F\u002Fwww.eventstorming.com\u002Fbook\u002F\">EventStorming creator\u003C\u002Fa>\n  \u003C\u002Fdiv>\n\u003C\u002Fblockquote>\n\n- Bringing people together from various departments (sales, marketing, product, engineering,\n  customer support, etc) helps you to capture the entire end-to-end flow. Rarely does a single\n  person know _everything_ across a workflow. Different people may know the start, middle, or end of\n  a business process. Together, the team will arrive at a shared understanding using their\n  collective knowledge.\n- Different people will spot different potential issues or opportunities. Someone from engineering\n  may focus on technical constraints, while someone from UX may see usability issues. A broad set of\n  eyes helps identify more areas for improvement.\n- Getting buy-in across the organization is crucial for driving change after EventStorming\n  workshops. Having representatives from various teams participate makes them feel ownership in the\n  process and outcome. They can become advocates for implementing improvements.\n- You want a balance of senior stakeholders who have authority and experience, as well as\n  on-the-ground staff who know low-level details. EventStorming helps to make connections between\n  your business and engineering.\n\nEventStorming should _not_ be run by a single team or individual. An engineering or product team\nrunning EventStorming by themselves will miss the key benefits. Cross-team communication and\nunderstanding are the main benefits of EventStorming.\n\nThe right mix of people leads to a richer picture of the current state, alignment on future vision,\nand shared commitment to executing on the ideas generated. Cross-functional collaboration is\ncritical.\n",[10],"content\u002Fcontributors\u002Fbrian-zambrano.json","LIST","EventStorming","\u002Fcontent\u002Fguides\u002Feventstorming\u002Finvitations","2 min",[16],{"title":12,"content":17},[18,26,29,35,41,47,54,60,66],{"title":19,"order":20,"youtubeVideoID":21,"time":22,"path":23,"id":24,"link":25},"Introduction",1,"FG4UOoEJvBc","5 min","introduction","introduction.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fintroduction",{"title":6,"order":7,"time":14,"path":27,"id":28,"link":13},"invitations","invitations.md",{"id":30,"title":31,"order":32,"time":14,"path":33,"link":34},"events.md","Step 2 - Crowdsource events",20,"events","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fevents",{"title":36,"order":37,"time":14,"path":38,"id":39,"link":40},"Step 3 - Sequence events",30,"timeline","timeline.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Ftimeline",{"title":42,"order":43,"time":14,"path":44,"id":45,"link":46},"Step 4 - People",40,"people","people.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fpeople",{"title":48,"order":49,"time":50,"path":51,"id":52,"link":53},"Step 5 - Hotspots",50,"1 min","hotspots","hotspots.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fhotspots",{"title":55,"order":56,"time":14,"path":57,"id":58,"link":59},"Step 6 - External systems",60,"systems","systems.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fsystems",{"title":61,"order":62,"time":50,"path":63,"id":64,"link":65},"Step 7 - Pivotal events",70,"boundaries","boundaries.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fboundaries",{"id":67,"title":68,"time":69,"path":70,"link":71},"learn-more.md","Learning more","4 min","learn-more","\u002Fcontent\u002Fguides\u002Feventstorming\u002Flearn-more",1792578865869]