Madsen, Sabine ; Nielsen, Lene. / Using Storytelling to Reflect on IT Projects. I: Journal of Information Technology Theory and Application (JITTA). 2006 ; vol. 7, nr. 4, s. 35-47
Nielsen, Lene ; BÃ¸dker, Mads. / To do or not to do : Usability in open source development. I: Interfaces. 2007 ; vol. 71, summer. s. 10-11
BÃ¸dker, Mads ; Nielsen, Lene ; Ã˜rngreen, Rikke. / Enabling user centered design processes in open source communities. I: Usability and internationalization. Berlin : HCII / Springer Verlag, 2007. s. 10-18 (Lecture Notes in Computer Science; 4559).
Nielsen, Lene ; Chavan, Sameer. / Differences in task description in the think aloud test. I: Usability and internationalization. Berlin : HCII / Springer Verlag, 2007. s. 174-180 (Lecture Notes in Computer Science; 4559).
The end goal of using personas is to, so to speak, let the persona enter a scenario and this way explore the interactions and design through the eyes of the persona.Scenarios do not possess a single definition and in the literature a wide range of different scenarios are mentioned. They serve different purposes and are to be used at different points in the design process. Sabine Madsen and I have tried to get an overview of the different kinds of scenarios, mentioned in the current literature.
In my experience the biggest challenge is between problem scenarios (springboard stories, point of pain stories) and idea generating scenarios (context scenarios, key scenarios). I often find the describing the present problems in a scenario disturbs the idea generation and the possibility to clean the slate. This prevents knowledge that the problems and challenges might not be with the system, but in the context. Or that an IT system might not be the answers to the problem, – (e.g. writing a proper manual, as I have encountered in connection to a system). Problem scenarios are really good at pointing to problems with the present system and creates space for creating solutions to these problems.
An interesting pod cast on how personas can be useful to the open source community behind TYPO3. Mette BjÃ¸dstrup shows Kasper SkÃ¥rhÃ¸j, who is one of the core developers, the process behind the personas and Kasper tells how he can relate to the descriptions. Down load at:
This article was first published at HCI Vistas
I recently hosted a personas workshop aimed at innovation within dairy products. It was with some nervousness I went into a process that is quite far from IT, web design, mobile software, and the familiar boundaries of technology. Interestingly the personas method seems to function in other settings as well and â€“ more interestingly with methods from a more traditional field of innovation.
The aim of the workshop was to innovate on products or invent completely new products. The participants were a mixed crowd: engineers, anthropologists, a product designer, a chef, concept developers, and project managers. Continue reading
Thomas Tim Jensen spÃ¸rger:
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
Jeg har aldrig hÃ¸rt om pseudonymer som metode. Kan du ikke forklare lidt mere om hvad det er? Har du en henvisning? Continue reading
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.
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, with the introduction of the goal-directed method, emphasizes detailed user descriptions (precision), while Pruitt and Grudin 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, , , . The accurate approach , ,  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. Continue reading