Latest / 5 Minute UX / Include Optional Content Based on Project Relevance
Transcript
- 0:07This lesson is Include Optional Content Based on Project
- 0:10Relevance. Let's get started.
- 0:17Optional content in a persona is not added by default. It is
- 0:20included only when it varies from product to product, client
- 0:23to client, or project to project. This principle of
- 0:25inclusion prevents you from cluttering a profile with data
- 0:28that doesn’t serve the current goal. The decision to include
- 0:31specific data points depends directly on the type of user
- 0:34research performed. If your interviews didn’t capture salary
- 0:37data, you don’t have it, so you don’t add it. Similarly,
- 0:39inclusion depends on the type of product, application, or service
- 0:43being developed. A financial app requires different details than
- 0:46a social media platform. Finally, constraints such as
- 0:48time and resources act as the final determinants for adding
- 0:51optional data. You must weigh the value of extra detail
- 0:54against the effort required to gather and maintain it. This
- 0:56ensures every element you include earns its place in the
- 0:59profile.
- 1:05You already build the core of every persona before adding
- 1:07anything else. That core is the least common denominator, the
- 1:10six pieces that make a user relatable: a photo, a name, age,
- 1:12location, occupation, and a biography. This baseline ensures
- 1:15the persona functions as a reference point for the team,
- 1:17grounding empathy in concrete details before any optional data
- 1:20is considered. Once that foundation is set, you evaluate
- 1:22optional elements against specific project constraints.
- 1:25These include Education Level, Salary or Salary Range,
- 1:27Demographics, Quotes or Testimonials, and Priority
- 1:29Level. Each serves a distinct purpose, such as Education
- 1:31Level, which provides insight into habits, purchasing
- 1:34behaviors, and brand perceptions. A person with a
- 1:36high school diploma may have substantially different brand
- 1:38perceptions than one with a master’s degree, so including
- 1:41this data changes how the audience interprets the persona.
- 1:43Similarly, Quotes or Testimonials provide explicit
- 1:45insights into how the persona thinks and feels, creating a
- 1:48direct connection for the reader. This isn’t just about
- 1:50filling space; it’s about ensuring the persona resonates
- 1:52with the specific stakeholders involved. If the project doesn’t
- 1:55rely on these nuances, the optional elements remain
- 1:57excluded, keeping the profile focused and relevant to the work
- 2:00at hand.
- 2:06Ground this in a specific scenario: you are building a
- 2:09persona for a marketing team targeting college-aged students.
- 2:11Demographics, which provide basic statistical metadata,
- 2:13become critical here because they offer additional insights
- 2:16into behaviors, needs, and expectations that a general
- 2:18biography might miss. In this context, the data is more
- 2:20important in marketing-focused scenarios, so you lean into it.
- 2:23But there is a strict constraint. You must use this
- 2:25demographic data in a way that avoids invoking bias in the
- 2:27personas. If you list age and income without context, you risk
- 2:30defining the user by a stereotype rather than a
- 2:32behavior. The goal is to apply the principle of inclusion to
- 2:34decide whether to add salary or demographics based on actual
- 2:37evidence, not assumptions. Age itself is a useful tool. It
- 2:39provides additional context on generational behaviors and
- 2:42expectations, helping you understand how a user might
- 2:44perceive a specific brand or interface. You are not just
- 2:46listing a number; you are mapping how that number shapes
- 2:49their digital habits. This turns a static fact into a dynamic
- 2:51insight about their needs. When you create multiple personas,
- 2:54you also assign a Priority Level. This identifies who the
- 2:56primary, secondary, or tertiary users are, ensuring the team
- 2:58focuses on the right audience first. By evaluating these
- 3:01elements against your project constraints, you ensure the
- 3:03persona serves the specific client goal. This careful
- 3:05evaluation prevents you from adding data that dilutes the
- 3:08core message, setting the stage for the specific scenario-based
- 3:10decisions that follow.
- 3:18So, when you're deciding what to add to your baseline, think
- 3:20about the specific project context. If your work involves
- 3:23purchasing behavior analysis, include Education Level. A
- 3:25person with a high school diploma often has different
- 3:28brand perceptions than one with a master's degree, so that
- 3:30distinction matters here. Now, ask yourself if the audience is
- 3:33marketing-focused. If so, Demographics can refine your
- 3:35behavioral insights, but you must check for bias to ensure
- 3:38the persona remains representative. Consider
- 3:40whether your primary goal is empathy and connection. In that
- 3:42case, pull direct Quotes or Testimonials from your user
- 3:45research to show how the persona thinks and feels. What about
- 3:48Salary or Salary Range? If resources are constrained, omit
- 3:50it unless it directly impacts the specific client goal. You
- 3:53have the baseline, you have the optional elements. Now, weigh
- 3:55each one against your specific project needs to decide what
- 3:58actually adds value.
- 4:05The most common error is adding optional data by default,
- 4:08treating education or salary as standard rather than varying
- 4:10them based on the specific product or client. This ignores
- 4:13the core principle that optional content is included only when it
- 4:16adds value to the unique project context. Another critical
- 4:19mistake is skipping the baseline. Before adding any
- 4:21optional layers, the persona must contain the six standard
- 4:23components: photo, name, age, location, occupation, and
- 4:26biography. Without this foundation, the profile lacks
- 4:28the relational depth needed to draw stakeholders in. You also
- 4:31risk including demographics without checking if they invoke
- 4:34bias in the persona profile. Statistical metadata can skew
- 4:36perceptions if applied carelessly, so you must verify
- 4:39that the data supports empathy rather than stereotyping.
- 4:41Finally, don't overlook time and resource constraints. Adding
- 4:44complex elements like salary ranges or detailed behavioral
- 4:47analysis requires research depth you may not have. If the budget
- 4:49is tight, stick to the essentials and let the baseline
- 4:52do the heavy lifting. When you sit down to build your next
- 4:54persona, start with those six pieces and only add what your
- 4:57specific client actually needs.
- 5:02Welcome to The Take. I'm joined by a fellow practitioner and
- 5:04together we're going to dig into Include Optional Content Based
- 5:07on Project Relevance — what it means in practice and what's
- 5:10worth remembering.
- 5:12[HOST] I keep coming back to that line about salary data.
- 5:15It’s not just optional, it’s often a trap if you don’t have
- 5:18the evidence. [LEARNER] Exactly. I’ve seen teams add salary
- 5:21ranges because they think it adds weight, but without
- 5:24interview backing, it’s just guessing. [HOST] It’s worse than
- 5:28guessing. It’s fabrication. You’re inventing a constraint
- 5:31that didn’t exist in the research. [LEARNER] Right. And
- 5:34that’s where the bias check gets tricky. How do you verify that a
- 5:37demographic stat isn’t just a stereotype in disguise? [HOST]
- 5:41You ask if the data changes the design decision. If it doesn’t,
- 5:44it’s noise. If it does, you need the behavioral context.
- 5:47[LEARNER] That’s a good filter. But what about AI? It’s so easy
- 5:50to generate plausible demographics now. [HOST] That’s
- 5:53the danger. AI makes the "default" option too accessible.
- 5:56It lowers the cost of including bad data. [LEARNER] So the
- 6:00principle of inclusion becomes harder, not easier. You have to
- 6:03fight the convenience of the tool. [HOST] Definitely. The
- 6:06baseline is still your anchor. Photo, name, age. If you skip
- 6:09that, the AI-generated extras have no soul. [LEARNER] I like
- 6:13that. The soul has to come from the specific client, not the
- 6:16model. [HOST] Yes. And that’s why we weigh the effort. If you
- 6:19can’t maintain the detail, don’t include it. [LEARNER] It’s about
- 6:23earning its place. Every single field. [HOST] Precisely. Keep it
- 6:26lean. Let the core do the work. [LEARNER] I’m gonna audit my
- 6:30current project. I bet I've three unnecessary fields. [HOST]
- 6:33Go for it. If it doesn’t serve the goal, cut it. [LEARNER]
- 6:36Thanks. That’s a much cleaner mindset. [HOST] It’s the only
- 6:39way to keep the persona useful.