[{"data":1,"prerenderedAt":72},["ShallowReactive",2],{"content-guides-eventstorming-boundaries":3},{"markdown":4,"frontMatterAttributes":5,"bodyRaw":8,"contributorPaths":9,"menuType":11,"contentName":12,"slug":13,"readingTime":14,"menu":15,"nextDocItem":66,"previousDocItem":57},"\u003Cp>At this stage there is more than enough information to identify "pivotal events" or "key events."\nThese events are where there is a significant change is the process. These are very important since\nthey represent the emergent of business capabilities, or a bounded context.\u003C\u002Fp>\n\u003Cp>There is no specific rules on how or where to find pivotal events. However, there are a few\ntechniques and clues.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Look for duplicate events. When a single event is written many times or with various language,\nsomething important is happening. In the example, "Payment completed" is an example that has many\nduplicates.\u003C\u002Fli>\n\u003Cli>Look for a handoff from one person to another. A handoff between people can show that there is a\nclear change is purpose or business outcome from the events. Look how a \u003Ccode>potential user\u003C\u002Fcode> changes\nto a \u003Ccode>known user\u003C\u002Fcode> in the example\u003C\u002Fli>\n\u003Cli>Identify changes in language. Do the words and ideas between two bounds feel like they are working\non the same thing? In the diagram, the "Payment verification" phase mixes payment concepts with\n"gift code." There may be another boundary here that needs exploration.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cimg src=\"\u002Fassets\u002Fexternal\u002Fguides\u002Feventstorming\u002Fassets\u002Fdiagrams\u002Fsticky-notes-pivotal-events.png\" alt=\"Identifying pivotal events is the first step in finding the elusive bounded context\">\u003C\u002Fp>\n",{"title":6,"order":7},"Step 7 - Pivotal events",70,"At this stage there is more than enough information to identify \"pivotal events\" or \"key events.\"\nThese events are where there is a significant change is the process. These are very important since\nthey represent the emergent of business capabilities, or a bounded context.\n\nThere is no specific rules on how or where to find pivotal events. However, there are a few\ntechniques and clues.\n\n- Look for duplicate events. When a single event is written many times or with various language,\n  something important is happening. In the example, \"Payment completed\" is an example that has many\n  duplicates.\n- Look for a handoff from one person to another. A handoff between people can show that there is a\n  clear change is purpose or business outcome from the events. Look how a `potential user` changes\n  to a `known user` in the example\n- Identify changes in language. Do the words and ideas between two bounds feel like they are working\n  on the same thing? In the diagram, the \"Payment verification\" phase mixes payment concepts with\n  \"gift code.\" There may be another boundary here that needs exploration.\n\n![Identifying pivotal events is the first step in finding the elusive bounded context](\u002Fassets\u002Fexternal\u002Fguides\u002Feventstorming\u002Fassets\u002Fdiagrams\u002Fsticky-notes-pivotal-events.png)\n",[10],"content\u002Fcontributors\u002Fbrian-zambrano.json","LIST","EventStorming","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fboundaries","1 min",[16],{"title":12,"content":17},[18,26,33,39,45,51,57,63,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":27,"order":28,"time":29,"path":30,"id":31,"link":32},"Step 1 - Invitations",10,"2 min","invitations","invitations.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Finvitations",{"id":34,"title":35,"order":36,"time":29,"path":37,"link":38},"events.md","Step 2 - Crowdsource events",20,"events","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fevents",{"title":40,"order":41,"time":29,"path":42,"id":43,"link":44},"Step 3 - Sequence events",30,"timeline","timeline.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Ftimeline",{"title":46,"order":47,"time":29,"path":48,"id":49,"link":50},"Step 4 - People",40,"people","people.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fpeople",{"title":52,"order":53,"time":14,"path":54,"id":55,"link":56},"Step 5 - Hotspots",50,"hotspots","hotspots.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fhotspots",{"title":58,"order":59,"time":29,"path":60,"id":61,"link":62},"Step 6 - External systems",60,"systems","systems.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fsystems",{"title":6,"order":7,"time":14,"path":64,"id":65,"link":13},"boundaries","boundaries.md",{"id":67,"title":68,"time":69,"path":70,"link":71},"learn-more.md","Learning more","4 min","learn-more","\u002Fcontent\u002Fguides\u002Feventstorming\u002Flearn-more",1792665264594]