Arkiv

Arkiv for november, 2007

En dialog om personas og pseudonymer

29 november, 2007 Lene Nielsen Ingen kommentarer

Thomas Tim Jensen spørger:

Hej Lene
Dine blog-indlæg her om personas er yderst interessante, og jeg havde derfor lyst til at læse mere på snitker.eu/frupersonas, som du linker til. Men access denied, desværre.

Jeg arbejder med personas i mit arbejde som kommunikationskonsulent – og jeg har længe intuitivt set en parallel mellem personas og pseudonymer.

Personas og pseudonymer har jo den afgørende forskel, at en persona er en fiktiv modtager, hvor et pseudonym er en fiktiv afsender. Spørgsmålet, som jeg ikke har tænkt igennem for alvor, er imidlertid, om ikke begge, altså persona og pseudonym, kan reduceres tilbage til samme udgangspunkt, og om ikke dette udgangspunkt så kan kaste værdifuldt nyt lys frem over såvel persona og pseudonym?

Og så et direkte spørgsmål til dig: Er en persona en repræsentant for eller en inkarnation af målgruppen?

Tak for indsigt i din blog.

Med venlig hilsen
Thomas

Lene svarer:

Hej Thomas
Jeg har aldrig hørt om pseudonymer som metode. Kan du ikke forklare lidt mere om hvad det er? Har du en henvisning?

Du spørger: Og så et direkte spørgsmål til dig: Er en persona en repræsentant for eller en inkarnation af målgruppen?

Hverken eller. Det kommer an på hvordan du ser på begrebet målgruppe.
Jeg plejer at sige at personas er noget helt andet end målgrupper. Personas skal altid forstås sammen med det “domæne” som er aktuelt for designet eller problematikken. Det betyder at man kan have et sæt af personas, indenfor et givent “domæne” og et andet sæt hvis “domænet” ændrer sig – selvom målgruppen er den samme. Et eksempel – en bank har f.eks en målgruppe der er økonomisk velstillede personer ml 30 og 60. Hvis banken skal lave personas til alm. bankvirksomhed, regningsbetaling mm. så har de et sæt personas. Hvis de skal lave personas til pensionsområdet, så vil personas sættet se helt anderledes ud.

Nå det blev vist lidt langt. Men jeg håber, at det giver svar på dit spørgsmål.
Lene

Thomas replicerer:

Kære Lene

Tusind tak for dit svar ovre på min profil angående spørgsmålene om personas.

Fiktive greb
Jeg har primært mødt personas i forhold til webtekster. Her er min ret intuitive tilgang til personas er helt klart filosofisk og litteraturteoretisk orienteret – og dette er også grunden til, at jeg inddrager pseudonymer i mine overvejelser over personas. Personas og pseudonymer har jo det til fælles, at de er fiktive greb i forhold til tekstens modtager (persona) eller dens afsender (pseudonym).Pseudonymer som kommunikativ metode
Et velkendt eksempel på pseudonymer som kommunikativ metode er jo Søren Kierkegaard, der tager et helt galleri af pseudonymer i brug i sin “indirekte Meddelelse” – og disse pseudonymer anvender Kierkegaard netop for på én gang at komme nærmere sine læsere og at skabe afstand til sine læsere, så de ved selvvirksomhed kan tilegne sig teksten.Pseudonym som litterær inkarnation
I den forstand kan Kierkegaards pseudonymer vel se som litterære inkarnationer af Kierkegaard, selvom pseudonymitetsproblematikken sagtens også kunne beskrives anderledes, afhængigt af ens metodik i Kierkegaard-fortolkningen.Personas – fiktion på modtagersiden
Personas ser jeg som en meget interessant metode inden for usability, webdesign og webtekster – fordi vi ligesom med pseodonymerne på afsendersiden arbejder med fiktion, abstrakter eller konstruktioner – blot på modtagersiden. Der er dog også den krølle på ordet “persona”, at det jo er latin og betyder “maske” – nemlig maske i et skuespil – altså maske for afsenderen, ikke modtageren. En lidt uheldig sproglig krølle i denne sammenhæng. Men det er jo blot konvention.Domæne eller livsverden skal medforstås
Jeg er også med på, når du siger, at personas hverken er inkarnationer eller repræsentatanter for målgruppen – idet du berettiget spiller begrebet om målgruppe op mod begrebet om “domæner” – eller livsverdener, om man vil. Nemlig de domæner eller livsverdener (det enkelte individs subjektive verden af normer og værdier, som sætter mennesket i stand til at færdes og handle i sociale fællesskaber – Habermas). I den forstand er en persona meget mere end målgruppen. En persona skal rumme de gennemgående træk ved den livsverden eller det domæne, som mågruppen befinder sig i – enig.

Behov for yderligere refleksion
Dit svar, Lene, har været uhyre tankevækkende – og jeg ser et helt klart behov for at reflektere problemet om fiktive afsendere og fiktive modtagere langt dybere igennem. Man kunne i den forbindelse sagtens drage spørgsmål om chat-profiler, avatarer, Second Life, og spil-deltageres navne og deslige ind i denne refleksion – for også her bliver fiktionen en afgørende faktor i forståelsen. Fiktion som en af vor tids væsentligste kræfter i online universer. Persona eller maske som identitetsskabende og identitetsbærende kraft i en online tidsalder.

M.v.h.
Thomas

Lene svarer tilbage

Jeg har tænkt meget over dit svar som nu også ligger på min blog. Og du har en spændende pointe – den fiktive afsender. Og jeg ser absolut muligheder i at forfølge den. Mange virksomheder har brug for at se sig selv ikke bare som en entydig afsender, men som flere forskellige afsendere. Især på Corporate sites kan jeg se en virkelig styrke i at virksomheden tænker på sig selv som flere fiktive afsendere. Jeg kan forestille mig en afsender, der er ganske anderledes når det drejer sig om at tiltrække medarbejdere end når det drejer sig om at beskrive produkter f.eks. Og virksomheden vil måske lettere få øje på forskellighederne ved at blive opfattet som forskellige fiktive afsendere.

Categories: Personas Tags:

Personas – Communication or Process?

21 november, 2007 Lene Nielsen Ingen kommentarer

Paper published at the 7th Danish HCI Research Symposium.

ABSTRACT

Personas is viewed as a method for communicating user data to all members of the design team and customers, but maybe it should rather be viewed as a process method that ensures a user centered design process.

1. INTRODUCTION

Personas are fictitious descriptions of users based on field data. Personas encourage a user-centered design process. When design solutions are discussed the persona is inserted into various scenarios that form the point of departure for design decisions. The design of the personas method varies. Cooper [1], with the introduction of the goal-directed method, emphasizes detailed user descriptions (precision), while Pruitt and Grudin [12] focus on accuracy through relations to field data.

The precise persona approach sees the advantages of the method as its ability to focus design and its ability to end discussions in its capacity of being a communication tool, [1], [2], [3]. The accurate approach [4], [11], [10] focuses on a strict relationship between data and what is communicated in the personas description. Focus areas in the descriptions are: computer skills, market size and influence, activities a typical day or week in the user’s life, the persona’s fears and aspirations. Added are strategic and tactical reflections. Both view the method as a communication tool for data.

2. COMMUNICATION OR PROCESS

The question of seeing a method as a communication tool implies a communication model of sender, message, media, and receiver [6]. In the personas method this can be seen in the attitude towards how the personas are created and communicated; someone translates the data into personas descriptions that are communicated to the design team via campaigns, e.g. slideshows, posters, emails, mugs [12] or as [11] puts it: “information about your complete personas is sent off into your organization”. This sender receiver model obscures one of the biggest challenges in the personas methods: how to get buy-in for using the method from the whole organization. Rather than seeing the methods as a communication tool, it could be viewed as a process tool – a movement, or a designed sequence of changes, towards a user centered design involving all parties in the design process.

3. TEN STEPS – A PROCESS MODEL

From a practical and a research perspective I propose a model that views the personas method as a process. In the following I will go through the model from a process perspective.

3.1 Step 1: Finding the Users

The initial step is to get hold of as much knowledge of the users as possible. The data can originate from several sources: interviews, observations, second hand information, questionnaires, reports, cultural probes etc.

3.2 Step 2: Building a Hypothesis

Working with the personas method is focusing on users in a certain project context or domain and building a hypothesis of how the context might influence what constitutes a persona and the number of personas.

This is illustrated in the following example. A project for a national Danish authority concerning redesign of a web portal for business reports to different governmental authorities. The national authority had a tradition for dividing Danish businesses into categories of size and trades. When using the personas method this division of businesses did not make sense. The domain is not business size or trade, but reporting. What mattered is how big the company is – big companies have dedicated staff to do the reporting, small companies have staff where reporting is a minor part of their job. Another factor is whether the person who reports is employed within the company or is a consultant [9].

3.3 Step 3: Verification

In the step ‘Verification’ the focus is on finding data that supports the initial patterns and at the same time supports the personas descriptions and the scenario writing e.g. what are the users values? What are their attitudes towards the system/site? The personas method is fundamentally a qualitative method and as such it requires several phases of looking at the result from both a partial and total perspective. In ‘Verification’ the partial result is tested to see if it obtains meaning in comparison with the overall result [5]. From a process perspective this test can be facilitated by involved members of the design project.

3.4 Step 4: Finding Patterns

Finding patterns is a categorization of the data into meaningful patterns that can support the personas descriptions. From a process perspective it is of importance to show the categorization to other team members, project partners etc.

In the above mentioned case we conducted a workshop with project partners and report suppliers in order to get their approval of the findings and patterns. This gave them not only an understanding of the underlying data and their comments to the interpretations, but provided also their support of the method.

3.5 Step 5: Constructing Personas

This step is not only a description of users, but includes an awareness of the final goal of the method; to create design solutions that takes the needs of the persona as starting point [7]. The fifth step might enhance buy-in. Pruitt and Adlin [11] address a “you” – the author of personas descriptions – in their book, when writing about this step. The personas method should rather be perceived as a collective process where everybody should understand how the descriptions came about and what they can be used for. If different team members are allowed to be part of the writing process they feel ownership of the personas. Afterwards the descriptions can be rewritten by a single person to ensure homogeneity in writing and presentation.

3.6 Step 6: Defining Situations

This step is a preparation for the scenarios. Here the situations in which the persona will use the system/site are described. Again it is a step where inclusion of partners can prove valuable for the process of adapting the method.

3.7 Step 7: Validation and Buy-in

To ensure that all participants agree on the descriptions and the situations two strategies can be followed. 1: ask everybody their opinion. 2: let them participate in the process. Having a process view helps create sessions where as many stakeholders as possible can be involved in the developing the personas and in using them for design.

3.8 Step 8: Dissemination of Knowledge

If the personas are not disseminated to participants they are not worth anything. It is not only the personas that needs to be distributes to everybody, but also the data – the foundation document [11], [4].

3.9 Step 9: Creating Scenarios

The personas method proves valuable when a persona enters a scenario. Teaching designers to think in persona-focused scenarios is part of the process. If they are not taught, the method might not be used by the individuals during the design phase where personas advocates are long gone.

3.10 Step 10: Ongoing Development

Lastly information on the personas should be updated [8]. It is crucial that not everybody is able to change the information, but knows whom to contact. I recommend having a personas ambassador who looks into the descriptions and who project participants can contact if they find irregularities in the descriptions. It is also the ambassador’s duty to let the personas die when they have outlived their purpose [11].

4. CONCLUSION

This project model is a proposal. The insistence on a process view in the method seems to clear some of the problems reported in communicating the method to designers [8]. To refine the process and to test it further studies are needed.

5. REFERENCES

[1] Cooper, A. The Inmates Are Running the Asylum. SAMS, Indianapolis, 1999.

[2] Goodwin, K. Perfecting your Personas. www.cooper.com, 2001.

[3] Goodwin, K., Getting from Research to Personas. www.cooper.com, 2002.

[4] Grudin, J. and J. Pruitt. Personas, Participatory Design and Product Development. In PDA 2002, Malmoe, 2002.

[5] Kvale, S. InterView. Hans Reitzel, København, 1997.

[6] McQuail, D. Audience Analysis. Sage, London, 1997.

[7] Nielsen, L. Engaging Personas and Narrative Scenarios, PhD Series. Samfundslitteratur, Copenhagen, 2004.

[8] Nielsen, L. Then the picture comes in your mind of what you have seen on TV. In The 5th DHCIR Symposium, Copenhagen, 2005.

[9] Nielsen, L., E. Landbo, and A. Vorre Hansen. Personas for Virk.dk – beskrivelser af personas, orbitter og deres tilknyttede data. Snitker & Co, 2007.

[10] Olsen, G., Making Personas More Powerful. www.boxesandarrows.com, 2004.

[11] Pruitt, J. and T. Adlin. The Persona Lifecycle. The Morgan Kaufmann Series in Interactive Technologies. San Francisco, 2006.

[12] Pruitt, J. and J. Grudin, Personas: Practice and Theory. www.research.microsoft.com, 2003.

Categories: In English, Personas Tags:

Hvad skal personaen hedde?

14 november, 2007 Lene Nielsen Ingen kommentarer

Jeg fandt dette sted hos Afdelingen for Navneforskning, hvor man kan se de mest populære navne i ti år fra 1900 til 2005. Det er godt inspiration til navngivning.

Categories: Personas Tags:

Persona and Scenario Practitioner Inquiry

8 november, 2007 Lene Nielsen 2 kommentarer
Nick Trendov wrote:
Lene,
as a story teller I appreciate your persona descriptions highly.
I have used stories, personas and scenarios for over 15 years in business and will teach an advanced Analytics and Scenario Analysis for Competitive Advantage at the University of Toronto in early 2008.

My contribution to the topic is the ability to link stories and numbers via personas with this simple mantra–

Tell a story twice and a process is documented, three times and software is written, four times and brand value is created, five times and a measure or KPI is built.

Any suggestions to persona or scenario links would be appreciated, especially any work that may be related to the ability to deliver knowledge or training in a highly accelerated manner.

My goal for the class is to use my persona and scenario experience to deliver knowledge and tools to the class on the same topic very, very quickly.

Good luck with your work!

Answer:

Your approach is very interesting. I have recently started to cooperate with Zentropa Interactive, a branch of the Danish Film company Zentropa, to add more expertise on storytelling to my personas courses. A year ago I did a survey on personas and scenario articles on the net. More have come since then, but you can find the list of articles here.

I am not sure you will find what you are looking for as most articles are from a IT perspective. The one who has written most extensively about scenarios in IT is John Carroll, maybe you will find some of his works useful. He does not have the personas perspective though.

Categories: In English, Personas Tags:

How can Personas be useful for developers??

3 november, 2007 Lene Nielsen Ingen kommentarer

Christina Braz asks:

I have just finished to read your article about personas on the Web. Although I agree with your statements I still have a question in my mind: How do Personas can be useful for developers?? You provide personas in order to developers start to develop an application. I am in the process of developing personas for a new security application and I have heard from someone else a quotation from one of our developers: “I don’t care about personas at all. I simply don’t use it.”

Christina Braz | Senior Software Engineer, UXD Team |

Answer: Most developers are not involved in the decision about using the personas and do not know how to use them. To put personas posters on the wall or quotes on mugs are just not enough.

In my experience what do help is to let the developers experience the strength of method when a persona description is put in action in a scenario. I do scenario workshops with the developers. In the workshop they learn to use the personas and they experience how thinking about personas gives them new insights for system demands and requirement specifications. Finally we talk about how they can move from the scenario descriptions to e.g. use cases or how they can use personas in their use cases.
So the short answer is Training and experiencing clear the way.

Categories: In English, Personas Tags: