meta data for this page
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
archetypes [2018/08/21 11:30] 127.0.0.1 external edit |
archetypes [2019/08/08 13:59] (current) lisa.illgen_concentrix.com Added Anchor Links |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| These descriptions of typical users are presented along with a back story that provides information as to how the user might interact with the IVR system. Archetypes may contain a photo, short biography and descriptions of tasks that the user might typically perform, along with the user's preferred channel for each task, e.g., IVR, web, etc. Biographies may be more or less detailed, but should mention such data as gender, age, education, familiarity with technology, and frequency with which they might use the IVR. Name each caller archetype with at least a first name, if not first and last. Some people create extremely detailed biographies for their archetypes; however, many UI designers believe that there is a point of diminishing returns as far as detailed biographies go. For example, it is useful to know that "Sarah" went to college and studied computer science, but it may not be that important which sorority she pledged. | These descriptions of typical users are presented along with a back story that provides information as to how the user might interact with the IVR system. Archetypes may contain a photo, short biography and descriptions of tasks that the user might typically perform, along with the user's preferred channel for each task, e.g., IVR, web, etc. Biographies may be more or less detailed, but should mention such data as gender, age, education, familiarity with technology, and frequency with which they might use the IVR. Name each caller archetype with at least a first name, if not first and last. Some people create extremely detailed biographies for their archetypes; however, many UI designers believe that there is a point of diminishing returns as far as detailed biographies go. For example, it is useful to know that "Sarah" went to college and studied computer science, but it may not be that important which sorority she pledged. | ||
| - | While some people might argue that this exercise is unnecessary, especially when timelines are short (and you may find yourself in the position of having to convince your customers of its worth), you will find that it is a useful tool throughout the design process. As you are creating sample calls, you can craft specific scenarios in which to find your different archetype callers. This will let you explore how these callers would interact with the system, and helps you to maintain their perspective. Once the sample phase is over, it is common to continue designing with these caller archetypes in mind. As you write prompts, you may find yourself and your customers thinking of particular archetypes and how they would react to a given situation or prompt. To summarize, the following are claimed benefits of persona in User Centred Design (UCD) (Adlin & Pruitt, 2010): | + | While some people might argue that this exercise is unnecessary, especially when timelines are short (and you may find yourself in the position of having to convince your customers of its worth), you will find that it is a useful tool throughout the design process. As you are creating sample calls, you can craft specific scenarios in which to find your different archetype callers. This will let you explore how these callers would interact with the system, and helps you to maintain their perspective. Once the sample phase is over, it is common to continue designing with these caller archetypes in mind. As you write prompts, you may find yourself and your customers thinking of particular archetypes and how they would react to a given situation or prompt. To summarize, the following are claimed benefits of persona in User Centred Design (UCD) ([[references#adlin|Adlin & Pruitt, 2010]]): |
| * They force designers to make implicit assumptions explicit | * They force designers to make implicit assumptions explicit | ||
| Line 12: | Line 12: | ||
| For a little more information about the user of personas in UCD (including some criticisms of the method), see [[ http://en.wikipedia.org/wiki/Persona_%28user_experience%29| wikipedia]]. | For a little more information about the user of personas in UCD (including some criticisms of the method), see [[ http://en.wikipedia.org/wiki/Persona_%28user_experience%29| wikipedia]]. | ||
| - | For detailed guidance on building and using archetypes, see Adlin & Pruitt (2010). | + | For detailed guidance on building and using archetypes, see [[references#adlin|Adlin & Pruitt]] (2010). |
| ==== References ==== | ==== References ==== | ||
| Adlin, X., & Pruitt, J. (2010). The essential persona lifecycle: Your guide to building and using personas. Waltham, MA: Morgan Kaufmann. | Adlin, X., & Pruitt, J. (2010). The essential persona lifecycle: Your guide to building and using personas. Waltham, MA: Morgan Kaufmann. | ||