Latest / 5 Minute UX / Write Personas from a Third-Party Perspective
Transcript
- 0:08This lesson is Write Personas from a Third-Party Perspective.
- 0:11Let's get started.
- 0:18Persona biographies belong in the third person, not in the
- 0:21user’s distinct voice. That shift matters because it strips
- 0:23away the performance of a fictional character and keeps
- 0:25the focus on the actual design problem. For designers who are
- 0:28just getting started, this recommendation is specific and
- 0:30deliberate. It prevents the early confusion of adopting
- 0:33distinct fictional voices, which can quickly muddy the analytical
- 0:35clarity of the work. When you write in the third person, the
- 0:38persona remains a descriptive document rather than a script.
- 0:41You are describing a typical target user to help the project
- 0:43team empathize with their needs. This approach keeps the
- 0:45narrative grounded in observable behaviors and research data. It
- 0:48allows stakeholders to see the user as a real person with
- 0:51specific goals, rather than a character acting out a role. The
- 0:53goal is to create a clear, reliable reference point for
- 0:55design decisions. By avoiding the complexity of first-person
- 0:58writing, you maintain the analytical distance needed to
- 1:00evaluate usability and business requirements. This sets a solid
- 1:03foundation before you explore more expressive styles later in
- 1:05your career.
- 1:12The reason third-person is the default starting point is that
- 1:14adopting distinct voices creates unnecessary complexity and
- 1:17confusion for novice practitioners. When you write in
- 1:19a user's voice, you are simultaneously crafting a
- 1:21character and executing a design task, which splits your focus
- 1:24precisely when it should be unified. The initial stage of
- 1:26your practice is about building reliable mental models, not
- 1:28performing a role. As experience expands, designers
- 1:31should naturally explore and find the style that fits them
- 1:33best and provides the most value. This progression is not a
- 1:35rule you must follow forever, but a natural evolution of your
- 1:38craft. The text does not mandate a permanent restriction on
- 1:40first-person writing, only that it is not the best starting
- 1:43point. You are not being punished for using the third
- 1:45person; you are protecting your clarity until the work feels
- 1:47intuitive. Once you have established that baseline, you
- 1:50can begin testing first-person drafts to see if they deepen
- 1:52your empathy or just add noise. The choice of perspective is a
- 1:55tool, not a commandment.
- 2:02You might wonder what makes a persona feel real to the people
- 2:05reading it. The answer lies in three specific content
- 2:07requirements that govern your writing. First, the information
- 2:10must be relevant and believable to the audience. If a
- 2:12stakeholder reads a detail that feels invented or disconnected
- 2:15from their reality, they stop trusting the document. Second,
- 2:18every detail must be derived from gathered research data. You
- 2:20are not guessing who the user is. Instead, you are translating
- 2:23specific findings from your studies into a cohesive
- 2:25narrative. Third, the content must be aligned with what is
- 2:28important to the client, brand, and project. This ensures the
- 2:31persona serves the immediate goals of the work rather than
- 2:33just describing a theoretical user. When you apply these
- 2:36three requirements together, you create a reference point that
- 2:39holds up under scrutiny. This alignment is what allows the
- 2:41persona to support design decisions later.
- 2:50Here is the spoken narration for Section 4. The persona is more
- 2:52than a profile; it is a document describing typical target users
- 2:55that helps project teams, stakeholders, and clients
- 2:57empathize with the people they serve. This empathy drives the
- 3:00actual work, because well- crafted, research-based personas
- 3:03act as go-to reference points for resolving questions or
- 3:05concerns related to design decisions, business
- 3:07requirements, visual design, or quality assurance. When a team
- 3:10debates a feature, the persona provides the anchor for that
- 3:12decision. However, not all personas serve the same purpose.
- 3:15You must distinguish between marketing-targeted personas,
- 3:18which model purchase motivations, and interactive
- 3:20personas, which are modeled toward usage behaviors. The
- 3:22guidance on third-party perspective applies specifically
- 3:25to the interactive personas focused in the UX design
- 3:27process. Since you are building for interaction, your persona
- 3:30must reflect how the user behaves with the interface, not
- 3:32just why they bought it. So, look at your current draft. Does
- 3:35it describe usage behaviors that a design team can reference when
- 3:38resolving a specific question about visual design or quality
- 3:40assurance? If it does, you have a functional reference point. If
- 3:43it only lists purchase motivations, it is a marketing
- 3:45persona, not a design tool. Check which one you have built,
- 3:48because the next step is to ensure it serves the specific
- 3:51decision-making needs of your project team.
- 3:59So, take the persona you just drafted and run it against the
- 4:01three content requirements. Ask yourself if every detail is
- 4:04relevant and believable to the audience, derived from gathered
- 4:07research data, and aligned with what is important to the client,
- 4:10brand, and project. If one of those pillars feels weak, the
- 4:13persona isn't ready to guide decisions yet. Next, test its
- 4:16utility in a real scenario. When a team debates a specific design
- 4:19decision or business requirement, does your persona
- 4:21act as the go-to reference point? If it doesn't immediately
- 4:24answer that question, it’s not functioning as a tool for
- 4:27empathy. It’s just a static document. A well-crafted persona
- 4:29resolves concerns related to visual design or quality
- 4:32assurance by grounding the discussion in the user’s actual
- 4:35behaviors. Finally, keep an eye on your own growth. This third-
- 4:38person approach is a starting point, not a permanent
- 4:40restriction. As your experience expands, you should naturally
- 4:43explore and find the style that fits you best. When you feel
- 4:46confident in the research and the structure, you can begin
- 4:49testing first-person perspectives to see if they
- 4:51provide more value for your specific project. Start with
- 4:54clarity, build on evidence, and let your voice evolve as your
- 4:57practice matures.
- 5:00Welcome to The Take. I'm joined by a fellow practitioner and
- 5:03together we're going to dig into Write Personas from a Third-
- 5:06Party Perspective — what it means in practice and what's
- 5:09worth remembering.
- 5:10[HOST] I’ve been wrestling with the idea that third-person is
- 5:14just a safety net for novices. [LEARNER] It feels less like a
- 5:17safety net and more like a constraint that actually
- 5:19clarifies the problem. [HOST] That’s a fair point. The lesson
- 5:23argues that adopting a distinct voice splits your focus between
- 5:26character and design task. [LEARNER] And that split is
- 5:29exactly where I lose the analytical thread in early
- 5:31sprints. [HOST] So when you strip away the performance,
- 5:34you’re left with observable behaviors. [LEARNER] Right. It
- 5:37forces you to describe the user as a reference point rather than
- 5:41a script. [HOST] But does that create a sterile document that
- 5:44stakeholders can’t connect with? [LEARNER] Not if the details are
- 5:47grounded in real research data. Believability comes from
- 5:50evidence, not voice. [HOST] Exactly. If a stakeholder sees
- 5:53an invented detail, they stop trusting the whole persona.
- 5:56[LEARNER] Which brings up the distinction between marketing
- 5:59and interactive personas. [HOST] Yes. Marketing models purchase
- 6:03motivations, while interactive personas model usage behaviors.
- 6:06[LEARNER] I’ve seen teams mix those up and end up with a
- 6:09profile that doesn’t help resolve design debates. [HOST]
- 6:12It’s useless for visual design decisions if it only lists why
- 6:15someone bought the product. [LEARNER] So the persona has to
- 6:18act as an anchor for specific usability questions. [HOST]
- 6:21Precisely. It needs to answer concerns about quality assurance
- 6:24or interface behavior. [LEARNER] Speaking of anchoring, how does
- 6:28AI fit into this drafting process? [HOST] It can help
- 6:30synthesize large amounts of research data into a coherent
- 6:33narrative quickly. [LEARNER] But it tends to hallucinate details
- 6:37that sound plausible but aren’t in the data. [HOST] That’s the
- 6:40danger. You have to verify every claim against your actual
- 6:43studies. [LEARNER] So AI accelerates the draft, but the
- 6:46human ensures the evidence is solid. [HOST] And that
- 6:49verification step is where the real value lies. [LEARNER] It
- 6:52keeps the persona from becoming just another generic profile.
- 6:55[HOST] Ultimately, the perspective is a tool, not a
- 6:58commandment. [LEARNER] And once you’re confident in the
- 7:01structure, you can experiment with first-person later. [HOST]
- 7:04But start with clarity, and let your voice evolve as your
- 7:07practice matures.