Defining a Persona

After some small research I realized it really depends on your own goals – what exactly you want to know about the user. Below are some of my thoughts how to define a persona, but they are rather “recommendations” than a solid template:

Defining a Persona

A persona represents a group of users who exhibit similar behavioral patterns in their use of technology or products, customer service preferences, lifestyle choices, and the like.

A persona details should list relevant to your business [or to your software] items.  One of the ways defining them is to conduct users interviews on the customer side (among potential end users), and starting from 30 interviews we can create a definition of our persona. Other thought how it can be done is through anonymous online surveys.

There are some details we may find about a persona, split on two main categories:

1. Personal Profile

1.     Age range (or broader: demographics)
2.     Location (or broader: cultural background)
3.     General likes/dislikes (list at least several items for each)
4.     Typical day off-work: Common everyday tasks and computer usage (describe)


2. Professional Expertise (these are still very general items. We may ask people to answer very specific question)

1.     Goals/needs
2.     Typical work day: Common everyday tasks, timing, and software usage
3.     [Type of industry of your business] software experience (describe: what, why, how, how long, likes/dislikes)
5.     Experience with a specific software of your interest (what product, why, how many years, likes/dislikes)
6.     Experience of use of operation system (MS Windows, version, years)
7.     MS Office experience

So, basically we should have a list of questions to ask users. 

After asking certain amount of people we can build a bigger picture, i.e. a persona.


Comments

Post a Comment

Popular posts from this blog

Using Trello and Confluence to manage UX design project. Part 2

Image
This is part Two. Part One can be found here . Term definitions. Brainstorming board. Activity board. Let me give you an overview of the items we refer to, deal with, and vetting all days long. Below are my simple definitions. UX Brief – a living document, a single and comprehensive point of reference of the design project. User Story – a short requirement or request from the end user. Later will be converted into task flow performed by this user to reach the goal. Acceptance Criteria – a set of conditions/statements, or a checklist, which defines the user story’s Pass/Fail . Feature – a functional part of the application, which combines several user stories. User stories are written to provide a complete support to this feature in terms of tasks performed by the user, while keeping in mind the user’s goal. Epic – a large logical group of multiple features in complex application. Brainstorm – a collaborative session involving product owners (PMs) and UX designers...
Read more

How do I use InVision

Image
Team lead asked me to write what InVision products do I use, how I use them, what are pros and cons. I wrote it today, and really think it will be helpful to share my thoughts with wider audience. So, below is the adaptation of what I provided to the engineering management in one fintech company.  I use InVision to share my hi-fi designs and specs, which I create in Sketch desktop application. This is my primary and every day usage of InVision, and about 90% of all usecases of all InVision products combined.  I sync designs via the plugin in Sketch made by Invision, called Craft .  When they are in InVision, we call those designs prototypes .  It works, but I often experience slowness. Sometimes sync process is failing, and I have to try it again. In Sketch I select one or more artboards, then initiate sync, which sends the artboard to InVision cloud. I have to be logged in Craft plugin with my InVision credentials. Almost every day, especially when I design intens...
Read more

Using Trello and Confluence to manage UX design project. Part 1

Image
This is part One. Part Two is here . Introduction. “ Describe your design process ”. It’s a typical interview question for UX designer position. User-centered design process indeed has defined set of steps. In theory. On the practice though, the adherence to these steps depends on many factors, such as communication and execution skills, practical experience, ability to influence people, being leader and influencer, and at what level your organization is a design driven org. So many businesses are not ready to adopt the design practice, and to place the design before the development. Or simply there is not time or budget to go through all steps. Here in Herbalife the UX Design team accepted Norman Nielsen group philosophy:   Empathize – Define –Ideate – Prototype – Test – Implement .  However the   interpretation of the practical tasks can differ dramatically in different organizations. Here what we currently do: Design Thinking and Agile Any project...
Read more