How do you ensure that user personas in your projects avoid unintended stereotyping, especially in a globalized market?

764 viewscircle icon2 Comments
Sort by:
Director of Product in Finance (non-banking)a month ago

When creating Personas, it is crucial to remember that they should be representative 'enough' of a certain kind or category of Users. Which means they should capture the critical parameters which are significant to call out the unique needs and wants of that kind or category. They should be the top layer in terms of the uniqueness of that group. And it is crucial to avoid any unintentional labelling or fixation to box that group into a certain description. This will ensure that there is no stereotyping involved. Hence you may choose to have layers of parameters used to describe that Persona or Person Groups. The foundational layer could be the most unique parameters or attributes of that group. Then the layer above could be more broader attributes. Then the top-most layer could be the most broad and open for any contextual cues to cater to the global audience and markets.

Director of Product Management8 months ago

My strategy is to 1) base personas on research, 2) focus on user motivations, challenges, and observed behaviors, and 3) revisit personas on an ongoing basis to validate they're still accurate. I know some persona approaches will advocate to include demographic details, but my experience personally is you get more accuracy and insights by interviewing a type of user based on their role and goals, across verticals and across geographies, than you do by focusing on race, age, and other surface level attributes.

Content you might like

Waterfall13%

Prototype18%

Rapid Application Development7%

Agile Scrum45%

Agile Kanban8%

Dynamic System Development1%

Lean Software Development2%

Other .. please add it down2%

View Results

0-10%28%

11-20%26%

21-30%20%

31-40%9%

41-50%6%

51-60%4%

61-70%2%

Over 71%2%

View Results