Projects/Usability/HIG/Persona: Difference between revisions

From KDE TechBase
< Projects‎ | Usability‎ | HIG
(Created page with "__NOTOC__ == Purpose == A ''persona'' is a representation of a fictitious user that includes a concise summary of characteristics of the user, their experience, goals and ta...")
 
No edit summary
Line 7: Line 7:
The advantage of persona is a common understanding over the development team and the abstraction or dissociation from the own point of view. In contrast to the alternatives lead user(s), panel of real users or sociological milieus
The advantage of persona is a common understanding over the development team and the abstraction or dissociation from the own point of view. In contrast to the alternatives lead user(s), panel of real users or sociological milieus


== Examples ==
== Guidelines ==


== Guidelines ==
== Best Practice ==
http://techbase.kde.org/Projects/Usability/Principles/KDE4_Personas


[[Category:Usability]][[Category:Structure]][[Category:Task_Flow]]
[[Category:Usability]][[Category:Structure]][[Category:Task_Flow]]

Revision as of 16:07, 27 January 2014


Purpose

A persona is a representation of a fictitious user that includes a concise summary of characteristics of the user, their experience, goals and tasks, pain points, and environmental conditions. Personas describe the target users, giving a clear picture of how they're likely to use the system, and what they’ll expect from it.

The advantage of persona is a common understanding over the development team and the abstraction or dissociation from the own point of view. In contrast to the alternatives lead user(s), panel of real users or sociological milieus

Guidelines

Best Practice

http://techbase.kde.org/Projects/Usability/Principles/KDE4_Personas