Grouping users into representative roles or personas — a children's-book PM glossary puts it as sorting 'types of people into various roles.' A product team designs and prioritizes features against these personas rather than against individual users, which is the operational form of You Are Not Your User: the PM's own preferences don't set requirements, the persona's needs do. Personas sit upstream of Acceptance Criteria — once a persona's need is defined, acceptance criteria state what that persona should be able to do.
Из тем: The Product Operating Model