Managing stakeholders through persona

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 30: Line 30:
 
*The fewer the better, representing the target audience  
 
*The fewer the better, representing the target audience  
  
−
An important part of defining a persona is to remember only to include the information, that is relevant in relation to the given project. The information should be kept short and to the point, to ensure that they most important points stand out. A key rule is that the text amount should be kept to a one eye span, so that the information easily can be captured (Lidwell et al., 2010). When forming one or several personas, it’s important to do the correct research for the foundation of the persona. The information needed for the person can be through achieved through both qualitative or quantitative data in form of interviews, observations, focus groups, demographics or questionaries.  
+
An important part of defining a persona is to remember only to include the information, that is relevant in relation to the given project. The information should be kept short and to the point, to ensure that they most important points stand out. A key rule is that the text amount should be kept to a one eye span, so that the information easily can be captured (Lidwell et al., 2010). When forming one or several personas, it’s important to do the correct research for the foundation of the persona. The information needed for the person can be through achieved through both qualitative or quantitative data in form of interviews, observations, focus groups, demographics or questionaries (Fuglerud et al., 2020).  
  
 
''Here I will add information about the time it takes and resource demand.'' Takes a long time approx. 1 month (Lidwell et al., 2010) and resources have to be invested (Adlin & Pruitt, 2010).Furthermore it’s important to remember that a persona is created for a specific project, so it’s not supposed to be reused for other projects (Fuglerud et al., 2020).
 
''Here I will add information about the time it takes and resource demand.'' Takes a long time approx. 1 month (Lidwell et al., 2010) and resources have to be invested (Adlin & Pruitt, 2010).Furthermore it’s important to remember that a persona is created for a specific project, so it’s not supposed to be reused for other projects (Fuglerud et al., 2020).

Revision as of 10:26, 19 February 2023

Contents

Introduction/Summary

In 1983 Allan Cooper was the first to implement the use of Personas in a Software Development project and popularized in his book “The Inmates Are Running the Asylum: Why High Tech Products Drive Us Crazy and How to Restore the Sanity”. The project participants quickly saw the benefits of using the “Personas” and naturally began referring to them during their project work as a reference to the users (The Cooper Journal: The Origin of Personas, n.d.). The method “Personas” is mainly used in design projects and the project participants together create a fictive profile to represent the users/stakeholder. This helps to ensure a user centric perspective and to humanize the design process when doing design projects. However, the method can also be applied to project management, helping managing the many stakeholders and ease the communication when using personas as a boundary object (Martin & Hanington, 2012). This article will first describe the idea behind the personas tool/method and how it can contribute to project management, then a guide of how to apply it in projects and finally the limitations involved when using personas.

The following text is a draft and I have in the article added references and bulletpoint that are yet to be written in italics.

The idea Behind Personas

But what is a persona and what are the benefits of using them?

A persona is usually a one page description of a fictive character including a:

  • A bio with basic information such as: name, age, education and occupation.
  • Illustration of how the person could look. Often a stock photo of sketch, to avoid any connection to a real identity person.
  • A quote summarizing some of the main points about the persona, for an easy reference.
  • More in depth description about life situation, goals and behaviour (Martin & Hanington, 2012).

Here I will more describing text about the benefits of using personas. I have from two different sources defined the most important points to include.

Points from (Martin & Hanington, 2012)

  • Create useful design targets
  • Behaviour pattern amongst user groups
  • Easy communication of users and Presuvissum reference when communicating research summaries to clients.


Points from (Lidwell et al., 2010)

  • Creating archetypal users representing a subpopulation of users
  • The should be created early in the project.
  • The fewer the better, representing the target audience

An important part of defining a persona is to remember only to include the information, that is relevant in relation to the given project. The information should be kept short and to the point, to ensure that they most important points stand out. A key rule is that the text amount should be kept to a one eye span, so that the information easily can be captured (Lidwell et al., 2010). When forming one or several personas, it’s important to do the correct research for the foundation of the persona. The information needed for the person can be through achieved through both qualitative or quantitative data in form of interviews, observations, focus groups, demographics or questionaries (Fuglerud et al., 2020).

Here I will add information about the time it takes and resource demand. Takes a long time approx. 1 month (Lidwell et al., 2010) and resources have to be invested (Adlin & Pruitt, 2010).Furthermore it’s important to remember that a persona is created for a specific project, so it’s not supposed to be reused for other projects (Fuglerud et al., 2020).


How to apply the use of personas within project management

Here I will write about how it will be applied to project management and the benefits of it. The following point have been defined, but needs to be explained further.

  • Help making better decisions (Adlin & Pruitt, 2010).
  • Ease the communication (Martin & Hanington, 2012).
  • Representative for absent stakeholders in a project (Woods et al., 2017).
  • Ensure that requirements are prioritized to specific needs of the most high value users (Martin & Hanington, 2012).

More literature on this topic is still being research.


Application of Personas

In this section I will describe in depth how to use personas. How to apply the use of personas can be divided into five stages, according to the book “The essential persona lifecycle” (Adlin & Pruitt, 2010). These stages will be explained in depth in the following paragraph.

  • Phase 1: in this phase the main focus is to form the team that is creating the personas and start the initial collecting of data and research for the persona.
  • Phase 2:
  • Phase 3:
  • Phase 4:
  • Phase: 5

Use affinity diagram to sort the data in the beginning (Martin & Hanington, 2012)


Limitations when using personas

The following paragraph is still to be written. But material to discuss has been found. https://findit.dtu.dk/en/catalog/5d80e410d9001d19d5298010 How is the information collected. Questions about the authenticy of the data? How much do people care about this (Fuglerud et al., 2020). Personas follow the concept that it’s better to understand on typical user, rather than designing for a general user that you don’t understand. Personas are used as a stand in for the typical user. But what about the atypical user. But when making such generic user descriptions, there is a change that you might miss out on important points. Users with disabilitys are not considered. There is a risk that personas might draw away attention from the actual users and that designers then might forget to also include them in the design project. (Fuglerud et al., 2020).Takes many years to master the tool and isn’t always beneficial the first time it’s used (The Cooper Journal: The Origin of Personas, n.d.).


Bibliography

Retrieved from "http://wiki.doing-projects.org/index.php?title=Managing_stakeholders_through_persona&oldid=127452"
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox