[{"data":1,"prerenderedAt":72},["ShallowReactive",2],{"content-guides-eventstorming-people":3},{"markdown":4,"frontMatterAttributes":5,"bodyRaw":8,"contributorPaths":9,"menuType":11,"contentName":12,"slug":13,"readingTime":14,"menu":15,"nextDocItem":47,"previousDocItem":38},"\u003Cp>After an initial sequence of events it's time to start adding people. You may see "people" called\ndifferent things in different EventStorming resources such as:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Actors\u003C\u002Fli>\n\u003Cli>Agents\u003C\u002Fli>\n\u003Cli>Personas\u003C\u002Fli>\n\u003Cli>Users\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The idea is the same: think through who is the target of a given event. This may or may not be the\nsame person who creates the event. Another way to think about it is who the event serves. Yet\nanother trick is to use a movie as an analogy. In any scene, there is a central character who is the\nstar. Sometimes there are multiple characters central to a particular scene.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"\u002Fassets\u002Fexternal\u002Fguides\u002Feventstorming\u002Fassets\u002Fdiagrams\u002Fsticky-notes-people.png\" alt=\"Adding people into the EventStorming board\">\u003C\u002Fp>\n\u003Cp>In this phase, add actors when they show up or change, not at every event. In the user sign up\nexample, your inclination may be to think that the only person involved is a \u003Ccode>customer\u003C\u002Fcode> or \u003Ccode>user\u003C\u002Fcode>.\nThink about adding an adjective in front of people. What type of \u003Ccode>user\u003C\u002Fcode> is involved in these events?\u003C\u002Fp>\n\u003Cp>In this example a \u003Ccode>potential user\u003C\u002Fcode> is the central character from the start of the process until they\nenter credit card information. The reason for this is that we don't know anything about the user\nexcept for perhaps their username and email address. They haven't signed up or made any commitment\nto sign up for our service. For those reasons, they are a \u003Ccode>potential user\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>You can follow this logic to the end when they finally become a \u003Ccode>full user\u003C\u002Fcode>. For technical teams,\nthink (just for a moment) of how to implement this. Would a \u003Ccode>potential user\u003C\u002Fcode> and \u003Ccode>known user\u003C\u002Fcode> have\nthe exact same attributes? Would you treat them the same in your code? If you implemented a single\n\u003Ccode>User\u003C\u002Fcode> object in your code, think about all of the optional attributes you'd need to add in order to\nrepresent a \u003Ccode>User\u003C\u002Fcode> across the entire timeline. People often don't get specific enough.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Warning!\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Don't go too far down this path of thinking of implementation at this stage. But, systems thinking\ncan help you add more specificity to the people involved in the timeline. Ultimately more\nspecificity will help you to understand and identify boundaries.\u003C\u002Fp>\n",{"title":6,"order":7},"Step 4 - People",40,"After an initial sequence of events it's time to start adding people. You may see \"people\" called\ndifferent things in different EventStorming resources such as:\n\n- Actors\n- Agents\n- Personas\n- Users\n\nThe idea is the same: think through who is the target of a given event. This may or may not be the\nsame person who creates the event. Another way to think about it is who the event serves. Yet\nanother trick is to use a movie as an analogy. In any scene, there is a central character who is the\nstar. Sometimes there are multiple characters central to a particular scene.\n\n![Adding people into the EventStorming board](\u002Fassets\u002Fexternal\u002Fguides\u002Feventstorming\u002Fassets\u002Fdiagrams\u002Fsticky-notes-people.png)\n\nIn this phase, add actors when they show up or change, not at every event. In the user sign up\nexample, your inclination may be to think that the only person involved is a `customer` or `user`.\nThink about adding an adjective in front of people. What type of `user` is involved in these events?\n\nIn this example a `potential user` is the central character from the start of the process until they\nenter credit card information. The reason for this is that we don't know anything about the user\nexcept for perhaps their username and email address. They haven't signed up or made any commitment\nto sign up for our service. For those reasons, they are a `potential user`.\n\nYou can follow this logic to the end when they finally become a `full user`. For technical teams,\nthink (just for a moment) of how to implement this. Would a `potential user` and `known user` have\nthe exact same attributes? Would you treat them the same in your code? If you implemented a single\n`User` object in your code, think about all of the optional attributes you'd need to add in order to\nrepresent a `User` across the entire timeline. People often don't get specific enough.\n\n\u003Cstrong>Warning!\u003C\u002Fstrong>\n\nDon't go too far down this path of thinking of implementation at this stage. But, systems thinking\ncan help you add more specificity to the people involved in the timeline. Ultimately more\nspecificity will help you to understand and identify boundaries.\n",[10],"content\u002Fcontributors\u002Fbrian-zambrano.json","LIST","EventStorming","\u002Fcontent\u002Fguides\u002Feventstorming\u002Fpeople","2 min",[16],{"title":12,"content":17},[18,26,32,38,44,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":39,"order":40,"time":14,"path":41,"id":42,"link":43},"Step 3 - Sequence events",30,"timeline","timeline.md","\u002Fcontent\u002Fguides\u002Feventstorming\u002Ftimeline",{"title":6,"order":7,"time":14,"path":45,"id":46,"link":13},"people","people.md",{"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",1792665264688]