What to consider when creating a “Persona” for a product?

What to consider when creating a “Persona” for a product?

Possible answers (9)

. We should write down all the prejudices that our users are prone to. If necessary, each Persona in our product can have its own "set" of prejudices.
. We should write down objects familiar to our users that we could refer to in the future.
. We should write down Ideas and objects the user wants to associate himself with. This includes everything from political and social views, continuing to professional achievements, and so on.
. We should write down all the ideological and moral-ethical values that our users adhere to. Besides, we should also write down those values the user does not believe in but publicly agrees and supports (). This is especially true for a B2B product (not a mass product).
. We should write down the main arguments that our “Persona” uses to rationalize a certain action/purchase. We then use this information to support users’ points of view ().
. We should write down all user concerns associated with a product category such as ours. Understanding what can cause the user emotional discomfort will allow us to build more comfortable communication (texts, calls, images).
. We should understand how the user relates to the publicity of his actions. This understanding will allow us to create interesting options for the product and give us additional leverage to nudge the user to some action.
. We need to understand and write down how our users assess their competence. Such item in "Persona" is not suitable for mass products, but it may be well suitable for the B2B sector. The narrower the niche of the product, the more relevant this item is.
We should also write down all those stereotypes and prejudices our audience is prone to , , .

Related questions

How useful you found this?
Not useful
1
2
3
4
5
6
7
8
9
10
Not useful
Very useful
Thank you for your contribution!
previous bias
next bias
keepsimple logo
picLog In
My ProfileSettingsLog Out

UX CORE GUIDE

arrow downHow to use

UXCG is a free tool that helps teams detect cognitive bias-related UX problems across all product stages, whether you're prototyping, testing, or improving a live product

How to use UXCG

  1. Choose your product stage below;
  2. Find your question (either manually or through search);
  3. Read possible answers.

Each answer explains how cognitive biases relate to your specific situation. Since you understand your context best, you can apply the insights directly. While the tool doesn't provide ready solutions due to each case's uniqueness, it reveals new perspectives backed by cognitive science.

Label description
Questions related to in-house team members cooperation (product, development teams and others).
Questions related to product development stage (from concept to first public release).
Questions related to sales, marketing funnels, prospects and leads communication, and overall product packaging.
Questions related to user interaction with actual product and its features.
Questions related to product analytical data analysis.
search icon
Select your product stage
#10.

Why do users complain about the quality of our support?

#30.

What common mistakes do we make when dealing with product analytics?

#41.

What should we do if our colleagues’ stubbornness is hurting teamwork?

#43.

What to consider when planning product releases?

#45.

What to do if our team members do not share their opinion?

#50.

How to deal with an incompetent colleague/manager?

#59.

What should we consider when referencing political, social, or economic events in our messages?

#61.

What should we do if our team wastes too much time on minor details?

Be Kind. Do Good.