[{"data":1,"prerenderedAt":72},["ShallowReactive",2],{"content-guides-eventstorming-timeline":3},{"markdown":4,"frontMatterAttributes":5,"bodyRaw":8,"contributorPaths":9,"menuType":11,"contentName":12,"slug":13,"readingTime":14,"menu":15,"nextDocItem":41,"previousDocItem":32},"\u003Cp>Once people have created enough events it's time to sequence them. Sequencing is nothing more than\ntalking through the order that the events occur relative to one another. While this process sounds\nit should spur many conversations and debate.\u003C\u002Fp>\n\u003Cp>During this stage there will be duplicate events that are written similarly, or completely\ndifferent. The group needs to discuss the language used in the events and agree upon words or\nphrases, what events are duplicates, and where events live along the timeline.\u003C\u002Fp>\n\u003Cp>In the example below there are four different events that relate to a credit card payment being made\nand accepted. They all have the same theme, but use different language. It also may make sense to\nconsolidate multiple events with one event that represent some amount of complexity. It could also\nmake sense to take a stack of events that you may think are the same thing, and split them up into\nmultiple events using slightly different language.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"\u002Fassets\u002Fexternal\u002Fguides\u002Feventstorming\u002Fassets\u002Fdiagrams\u002Fsticky-notes-sequence.png\" alt=\"Orange sticky notes represent domain events\">\u003C\u002Fp>\n\u003Cp>There are no absolute rules with EventStorming and sequencing! The most important part of the\nprocess is that domain experts explore, learn, and understand together.\u003C\u002Fp>\n\u003Cp>A question that will undoubtedly come up is how to handle parallel flows or logical branches. "We do\n\u003Cem>this\u003C\u002Fem> in some cases, but it depends on \u003Cem>that\u003C\u002Fem>." "This event happens when this other thing fails,\nand it doesn't happen often, but it's really important." Sometimes people may call this the "sad\npath" meaning something that happens during an error. A simple way of dealing with this is to put\nthe parallel events above or below the "happy path" flow.\u003C\u002Fp>\n\u003Cp>In this example imagine a duplicate email is detected during the new user flow. A duplicate email\ncould trigger a notification being sent to the user along with a security scan. Similarly, the\nsequence started with \u003Ccode>Gift code rejected\u003C\u002Fcode> coming after \u003Ccode>Gift code redeemed\u003C\u002Fcode>. Moving\n\u003Ccode>Gift code rejected\u003C\u002Fcode> above \u003Ccode>Gift code redeemed\u003C\u002Fcode> is a simple way to not lose detail and explore what,\nif anything, happens when an invalid gift code is entered.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"\u002Fassets\u002Fexternal\u002Fguides\u002Feventstorming\u002Fassets\u002Fdiagrams\u002Fsticky-notes-sad-path.png\" alt=\"Handling parallel or sad paths\">\u003C\u002Fp>\n\u003Cp>During a Big Picture sessions it's often sufficient to capture just the big events and not worry too\nmuch about all of the different permutations and paths. Many details will start to show up as you\nget into more depth in Process and Detail level EventStorming sessions.\u003C\u002Fp>\n",{"title":6,"order":7},"Step 3 - Sequence events",30,"Once people have created enough events it's time to sequence them. Sequencing is nothing more than\ntalking through the order that the events occur relative to one another. While this process sounds\nit should spur many conversations and debate.\n\nDuring this stage there will be duplicate events that are written similarly, or completely\ndifferent. The group needs to discuss the language used in the events and agree upon words or\nphrases, what events are duplicates, and where events live along the timeline.\n\nIn the example below there are four different events that relate to a credit card payment being made\nand accepted. They all have the same theme, but use different language. It also may make sense to\nconsolidate multiple events with one event that represent some amount of complexity. It could also\nmake sense to take a stack of events that you may think are the same thing, and split them up into\nmultiple events using slightly different language.\n\n![Orange sticky notes represent domain events](\u002Fassets\u002Fexternal\u002Fguides\u002Feventstorming\u002Fassets\u002Fdiagrams\u002Fsticky-notes-sequence.png)\n\nThere are no absolute rules with EventStorming and sequencing! The most important part of the\nprocess is that domain experts explore, learn, and understand together.\n\nA question that will undoubtedly come up is how to handle parallel flows or logical branches. \"We do\n_this_ in some cases, but it depends on _that_.\" \"This event happens when this other thing fails,\nand it doesn't happen often, but it's really important.\" Sometimes people may call this the \"sad\npath\" meaning something that happens during an error. A simple way of dealing with this is to put\nthe parallel events above or below the \"happy path\" flow.\n\nIn this example imagine a duplicate email is detected during the new user flow. A duplicate email\ncould trigger a notification being sent to the user along with a security scan. Similarly, the\nsequence started with `Gift code rejected` coming after `Gift code redeemed`. Moving\n`Gift code rejected` above `Gift code redeemed` is a simple way to not lose detail and explore what,\nif anything, happens when an invalid gift code is entered.\n\n![Handling parallel or sad paths](\u002Fassets\u002Fexternal\u002Fguides\u002Feventstorming\u002Fassets\u002Fdiagrams\u002Fsticky-notes-sad-path.png)\n\nDuring a Big Picture sessions it's often sufficient to capture just the big events and not worry too\nmuch about all of the different permutations and paths. Many details will start to show up as you\nget into more depth in Process and Detail level EventStorming sessions.\n",[10],"content\u002Fcontributors\u002Fbrian-zambrano.json","LIST","EventStorming","\u002Fcontent\u002Fguides\u002Feventstorming\u002Ftimeline","2 min",[16],{"title":12,"content":17},[18,26,32,38,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":27,"order":28,"time":14,"path":29,"id":30,"link":31},"Step 1 - Invitations",10,"invitations","invitations.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Finvitations",{"id":33,"title":34,"order":35,"time":14,"path":36,"link":37},"events.md","Step 2 - Crowdsource events",20,"events","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fevents",{"title":6,"order":7,"time":14,"path":39,"id":40,"link":13},"timeline","timeline.md",{"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",1792578865919]