Creating PersonasThis is a featured page

It is easy to assemble a set of user characteristics and call it a persona, but it's not so easy to create personas that are truly effective tools for innovation, design, and communication. A good persona description is not a list of tasks or duties; it's a narrative that illuminates their skills, attitudes, environment, goals, and needs and desires.

Personas are synthesized from in-depth engagements with a relatively small number of real people that represent the larger community, and captured in a structured definition that includes behavior patterns, goals, skills, attitudes, and needs and desires. They may include a few reality-based personal details to bring the persona to life. Personas are always created within a context that defines the ‘environment of interest’. For example, a context may be something like ‘perceptions of vehicle safety’ or ‘drug therapy compliance’. This defines the focus of the specific in-depth engagements and, hence, the discovered behaviors, goals, and needs and desires of the personas being developed. There is no ‘global’ set of personas (like Meyers-Briggs is for personality traits) that can be used for all research efforts. Like traditional market segmentation, the more focused the context, the more accurate the personas. Personas are specific to a particular innovation, design, or communication effort.

For each context, there is a small set of personas, usually from 4 to 10, that adequately represents the universe of people of interest. Ideally, you should seek the minimum number of personas required to illustrate key goals and behavior patterns. There's no magic number, but if you're designing a product and you have a dozen personas, then you may be making distinctions that are not very important.

A structured process is used to move from a community of individuals to a set of persona descriptions. Details of this process are in Uncovering Tacit Knowledge and Elicitation Tools, but the basic activities undertaken to implement the process are:

  1. Elicit the knowledge and experience held by a knowledge community
  2. Capture the knowledge in way that enables analysis and synthesis
  3. Extract and organize the needs and desires of the community
  4. Synthesize this information and look for emergent patterns that identify personas
  5. Develop the persona definitions using dimensions of outcomes and experiences
  6. Create the Persona Adoption Models that capture the personas in software

Insight into the dynamics of the community comes from generalization – seeing the forest from the trees. Community Members inform our understanding of those who think and choose similarly. Inovo’s term for these groups are ‘Personas’. A Persona represents a state-of-mind for a consumer and is characterized by the cause of the behavior as opposed to the behavior itself. Personal analysis is the causal analog of ‘Psychographic’ analysis as used in Market Research.




laschmitt
laschmitt
Latest page update: made by laschmitt , Apr 29 2007, 10:48 AM EDT (about this update About This Update laschmitt Edited by laschmitt

178 words deleted

view changes

- complete history)
More Info: links to this page

Anonymous  (Get credit for your thread)


There are no threads for this page.  Be the first to start a new thread.

Related Content

  (what's this?Related ContentThanks to keyword tags, links to related pages and threads are added to the bottom of your pages. Up to 15 links are shown, determined by matching tags and by how recently the content was updated; keeping the most current at the top. Share your feedback on Wetpaint Central.)