Include Optional Content Based on Project Relevance

Apply the principle of inclusion to determine when education, salary, or demographics add value to a specific project. You will learn to filter optional data against client goals and research types to avoid bias and maintain relevance. Learning Objective: By the end of this lesson, learners will be able to evaluate optional persona elements against specific project constraints to determine their inclusion. Transcript The Principle of Inclusion Optional content in a persona is not added by default. It is included only when it varies from product to product, client to client, or project to project. This principle of inclusion prevents you from cluttering a profile with data that doesn’t serve the current goal. The decision to include specific data points depends directly on the type of user research performed. If your interviews didn’t capture salary data, you don’t have it, so you don’t add it. Similarly, inclusion depends on the type of product, application, or service being developed. A financial app requires different details than a social media platform. Finally, constraints such as time and resources act as the final determinants for adding optional data. You must weigh the value of extra detail against the effort required to gather and maintain it. This ensures every element you include earns its place in the profile. Key Points: Optional content is not added by default; it is included only when it varies from product to product, client to client, or project to project The decision to include specific data points depends on the type of user research performed Inclusion depends on the type of product, application, or service being developed Constraints such as time and resources are final determinants for adding optional data Baseline vs. Optional Elements You already build the core of every persona before adding anything else. That core is the least common denominator, the six pieces that make a user relatable: a photo, a name, age, location, occupation, and a biography. This baseline ensures the persona functions as a reference point for the team, grounding empathy in concrete details before any optional data is considered. Once that foundation is set, you evaluate optional elements against specific project constraints. These include Education Level, Salary or Salary Range, Demographics, Quotes or Testimonials, and Priority Level. Each serves a distinct purpose, such as Education Level, which provides insight into habits, purchasing behaviors, and brand perceptions. A person with a high school diploma may have substantially different brand perceptions than one with a master’s degree, so including this data changes how the audience interprets the persona. Similarly, Quotes or Testimonials provide explicit insights into how the persona thinks and feels, creating a direct connection for the reader. This isn’t just about filling space; it’s about ensuring the persona resonates with the specific stakeholders involved. If the project doesn’t rely on these nuances, the optional elements remain excluded, keeping the profile focused and relevant to the work at hand. Key Points: The baseline 'least common denominator' consists of six standard pieces: Photo, Name, Age, Location, Occupation, and Biography Optional elements include Education Level, Salary or Salary Range, Demographics, Quotes or Testimonials, and Priority Level Education Level provides insight into habits, purchasing behaviors, and brand perceptions Quotes or Testimonials provide explicit insights into how the persona thinks and feels, creating a connection for the reader Evaluating Relevance and Bias Ground this in a specific scenario: you are bui