Latest / 5 Minute UX / How To Create User Profiles With Stakeholders
Transcript
- 0:08This lesson is How To Create User Profiles With Stakeholders.
- 0:11Let's get started.
- 0:19We begin by grounding our work in the initial definitions that
- 0:22emerge from the collective knowledge of business
- 0:24stakeholders and project team members. This shared
- 0:26understanding provides a crucial starting point for identifying
- 0:29the potential types of users who might interact with the site.
- 0:31You must also identify specific company personnel who have
- 0:34direct contact with relevant user types, such as customers,
- 0:36because their frontline insights are invaluable. These
- 0:39individuals help us move beyond assumptions and tap into real-
- 0:41world interactions that shape user behavior. Establishing a
- 0:44clear statement of project goals is equally critical, as it
- 0:47serves as the firm basis for prioritization later in the
- 0:49process. Without these defined objectives, it becomes difficult
- 0:52to determine which user attributes truly matter for the
- 0:54success of the project. We rely on this clarity to ensure that
- 0:57our subsequent research efforts align directly with the
- 0:59overarching aims of the initiative. This alignment
- 1:01prevents scope creep and keeps the team focused on what
- 1:04actually drives value. By securing these prerequisites, we
- 1:06create a stable foundation for the collaborative work that
- 1:09follows. The definitions, stakeholder access, and goal
- 1:11statements we establish now will guide every decision we make in
- 1:14defining user segments. Once these elements are in place, we
- 1:16can confidently move forward to identify the specific categories
- 1:19of user attributes that will define our profiles. This
- 1:21preparation ensures that our eventual user groups are both
- 1:24realistic and strategically relevant to the project's needs.
- 1:32You start by generating a comprehensive list of attributes
- 1:35that define the different users of the site. This involves
- 1:38identifying three main categories of user attributes:
- 1:40demographics, experience, and organizational factors.
- 1:43Demographics cover age, sex, family status, income level, and
- 1:45region, providing a basic snapshot of who the users are.
- 1:48Experience attributes delve deeper into education level,
- 1:51technical savvy, subject matter expertise, and frequency of
- 1:54usage. You need to know if a user is a frequent visitor or a
- 1:56one-off user. This distinction matters because technical
- 1:59familiarity often dictates how they navigate your interface.
- 2:02Organizational attributes capture company size,
- 2:04department, job type, tenure, and work patterns like remote
- 2:07work. Consider company culture variations, such as expectations
- 2:10for remote versus in-person work. These factors shape the
- 2:13context in which users interact with the product daily. These
- 2:15attributes feed into your screener for recruiting and
- 2:18logistics planning later. They determine which user groups to
- 2:21represent and the number of users to include in testing. By
- 2:24capturing these details now, you build a foundation for
- 2:26validating initial definitions through stakeholder dialogue.
- 2:35Now that you have generated your initial list of demographic,
- 2:37experience, and organizational attributes, the real work begins
- 2:40with validation. You must discuss these generated
- 2:42attributes with stakeholders who have direct contact with users
- 2:45to expand and validate them. This dialogue is critical
- 2:47because it prevents the common pitfall of relying solely on
- 2:49initial definitions without stakeholder validation. When you
- 2:51bring together business stakeholders and project team
- 2:54members, you tap into collective knowledge that reveals nuances
- 2:56your initial list might have missed. As you engage in this
- 2:58conversation, listen for how these attributes actually
- 3:01manifest in real-world interactions. You might discover
- 3:03that technical savvy varies significantly between
- 3:05departments, or that remote work patterns influence usage
- 3:07frequency more than you anticipated. Expanding on the
- 3:09attributes based on this dialogue ensures your
- 3:11definitions are grounded in reality rather than assumption.
- 3:13It transforms a static list into a dynamic understanding of who
- 3:16these users truly are and how they operate within their
- 3:18specific contexts. Once the attributes are validated, you
- 3:20need to apply prioritization techniques to segment user
- 3:23groups based on impact on goals and behavior. Prioritize
- 3:25attributes by identifying those with the greatest influence on
- 3:27how and why users interact with the site. You are looking for
- 3:30the characteristics that fundamentally drive decision-
- 3:32making and task completion, not just surface-level details.
- 3:34Focus prioritization on attributes that have the largest
- 3:36impact on a user’s goals or behavior, because these are the
- 3:39levers that will shape the design. This step requires you
- 3:41to dig down to the roots of needs and goals to ensure
- 3:43understanding. If an attribute doesn’t change how a user
- 3:45approaches a task or what they hope to achieve, it likely
- 3:48doesn’t belong at the top of your hierarchy. By ranking
- 3:50attributes by their level of importance, you create a clear
- 3:52hierarchy that guides your subsequent modeling efforts.
- 3:54This hierarchy becomes the foundation for defining distinct
- 3:57user groups that matter most to the project’s success. The
- 3:59result of this prioritization is a refined set of criteria that
- 4:02directly informs your research strategy. This information feeds
- 4:04into your screener for recruiting and logistics,
- 4:06determining which user groups to represent and the number of
- 4:09users to include in each group for testing. By anchoring your
- 4:11segments in validated, high- impact attributes, you ensure
- 4:13that your research efforts are focused and efficient. This
- 4:16structured approach allows you to move confidently toward
- 4:18modeling these specific groups for your design work.
- 4:26Take that hierarchy of prioritized attributes and use
- 4:28it to define distinct user groups for your research. You
- 4:31aren't just listing traits anymore; you're building models
- 4:33of the specific people who will interact with your product. This
- 4:36step transforms abstract data into concrete segments that
- 4:39guide your design efforts. Now, look at those segments and
- 4:41decide which ones matter most for your upcoming testing. You
- 4:44need to identify the specific user groups that will be the
- 4:46focus of subsequent research and design efforts. Don't try to
- 4:49recruit everyone at once. Pick the groups whose behavior aligns
- 4:52most closely with your project goals. Once you've chosen your
- 4:55segments, translate them into screener criteria for recruiting
- 4:57and logistics planning. Think about how you'll verify a
- 5:00candidate's technical savvy or organizational role during the
- 5:03interview phase. These criteria ensure you're talking to the
- 5:05right people, not just anyone who fits a vague description.
- 5:08Finally, determine the number of users to include in each group
- 5:11for testing based on these segments. Balance your resources
- 5:13against the diversity of your audience. This planning prevents
- 5:16recruitment bottlenecks and keeps your study manageable.
- 5:18You've moved from broad stakeholder knowledge to precise
- 5:21recruiting targets. Now, take these screener criteria and
- 5:23start inviting participants, knowing exactly who needs to be
- 5:26in the room.
- 5:30Welcome to The Take. I'm joined by a fellow practitioner and
- 5:33together we're going to dig into How To Create User Profiles With
- 5:36Stakeholders — what it means in practice and what's worth
- 5:39remembering.
- 5:41[HOST] The part about validating attributes with frontline staff
- 5:44really stuck with me. [LEARNER] I totally agree. We usually skip
- 5:48that step to save time. [HOST] Skipping it's risky because
- 5:51assumptions rot the foundation. [LEARNER] True, but getting
- 5:54those busy people to talk is hard. [HOST] It requires framing
- 5:58the conversation around their specific pain points. [LEARNER]
- 6:01That makes sense. They care about solving problems, not
- 6:04filling forms. [HOST] Exactly. You trade their time for
- 6:07insights that save weeks later. [LEARNER] What about
- 6:10prioritizing those attributes once we've them? [HOST] That's
- 6:13where most teams get stuck in analysis paralysis. [LEARNER] I
- 6:17feel that. We end up listing every possible trait. [HOST] You
- 6:20have to cut anything that doesn't change user behavior.
- 6:23[LEARNER] Right. If age doesn't affect navigation, drop it.
- 6:27[HOST] I've seen AI tools help sort those low-impact attributes
- 6:30quickly. [LEARNER] Really? I haven't tried that yet. [HOST]
- 6:33It flags outliers so you can focus on the core drivers.
- 6:36[LEARNER] That could save us hours of debating trivial
- 6:39details. [HOST] Just remember the AI needs clean input data to
- 6:43start with. [LEARNER] Good point. Garbage in still means
- 6:46garbage out here. [HOST] So we validate first, then let the
- 6:49tool help us prioritize. [LEARNER] I like that workflow.
- 6:52It keeps the human insight central. [HOST] It balances
- 6:56speed with the nuance we need for good design.