- External reference: https://designcode.io/ux-design-handbook-user-personas
- External reference: https://www.nngroup.com/articles/persona/
To me, a persona help guessing the answer to the hard question of “what does it do to use the product?”. See quale. It is a kind of controlled question substitution. The idea is to help developers have empathy towards those characters.
A user persona is the creation of an imaginary character based on what we think is a typical end-user of our app. The description of the persona must include personal details, goals, and concerns of the character. Very similar to the work that screenwriters do when they are creating characters for their screenplays.
There is no specific list of the details we can add to a persona, but make sure that the persona you are creating is as realistic as possible
essential you need to consider when working with personas and writing the context is the everyday things
things we sometimes fail to notice
we must design products around people, rather than teaching people how to use products
persona is a fictional, yet realistic, description of a typical or target user of the product. A persona is an archetype instead of an actual living human, but personas should be described as if they were real people.
description should be thorough, including details about the persona’s needs, concerns, and goals, as well as background information such as age, gender, behaviors, and occupation
focus on a singular individual—or a small set of individuals, if using multiple personas—fosters empathy for the specific users we are designing for, and helps us break away from the attempt to design for everyone
Personas work because designers and developers have the same tendency as all other people to be captivated more by concrete instances than by abstractions and generalizations