Latest / 5 Minute UX / Ranking User Attributes to Define User Groups
Transcript
- 0:08This lesson is Ranking User Attributes to Define User
- 0:10Groups. Let's get started.
- 0:18You start by gathering existing research and organizational
- 0:21documentation to compile a preliminary list of attributes
- 0:23that stakeholders frequently mention. This initial
- 0:25compilation grounds your work in real data rather than pure
- 0:28intuition, ensuring you capture the factors people actually use
- 0:30to describe potential users. You need to identify common
- 0:33attribute categories, beginning with demographics like age, sex,
- 0:35family status, income level, and region. These basic markers
- 0:38provide a foundational layer for understanding who your users are
- 0:40before you dive deeper into their behaviors. Next, you
- 0:43incorporate experience attributes, which include
- 0:45education level, technical savvy, subject matter expertise,
- 0:47and usage frequency. Frequency is particularly important, so
- 0:50you distinguish between one-off, occasional, and frequent users
- 0:52to understand how deeply they engage with the product. You
- 0:55also add organizational attributes such as company size,
- 0:57department, job type, tenure, and work patterns. Job type
- 0:59ranges from entry level to executive, while work patterns
- 1:02cover remote work versus travel, reflecting the reality of modern
- 1:04professional environments. This comprehensive list captures the
- 1:07full spectrum of user characteristics, from personal
- 1:09demographics to professional contexts. By absorbing this
- 1:11existing documentation, you create a robust starting point
- 1:14for defining the different users of the site. You now have a
- 1:16broad collection of potential attributes to review and refine
- 1:19in the next phase. We’ll expand this list by discussing it with
- 1:21internal personnel who have direct contact with users,
- 1:24ensuring the attributes reflect actual business knowledge.
- 1:32Take that preliminary list of demographics and experience
- 1:34attributes to people who actually talk to your users
- 1:37every single day. You need to review those initial categories
- 1:39with internal personnel like customer service representatives
- 1:42or sales staff who have direct contact with the relevant user
- 1:44types. They will spot nuances in organizational attributes or
- 1:47cultural variations that you simply cannot see from behind a
- 1:49design screen. This collaborative discussion expands
- 1:52your attribute list based on collective business knowledge
- 1:54rather than relying solely on UX designer intuition. It grounds
- 1:57the data in real-world interactions, ensuring your
- 1:59attributes reflect actual user contexts instead of theoretical
- 2:01assumptions. By bringing in this frontline perspective, you
- 2:04recover from the common pitfall of intuition-based attribute
- 2:07selection. The goal is to describe the process of
- 2:09expanding attribute lists through stakeholder discussion
- 2:11so you capture the full picture. Their insights fill the gaps
- 2:14between your initial research and the messy reality of daily
- 2:16user behavior. You are building a foundation that is robust,
- 2:19verified, and deeply connected to how the business actually
- 2:21operates. Once you have this expanded, grounded list, you are
- 2:24ready to evaluate which attributes truly influence user
- 2:26goals.
- 2:33Now that you have gathered and expanded your attribute list
- 2:35through stakeholder input, you need to prioritize those
- 2:37attributes by influence. This step is critical because you
- 2:39cannot design for everyone at once, so you must identify which
- 2:41factors actually drive how and why different user groups use
- 2:44the site. You are looking for the attributes that have the
- 2:46greatest influence on user behavior, filtering out the low-
- 2:48impact data that clutters your understanding. Think about the
- 2:50project objectives you established earlier in the
- 2:52process. You should use those established project objectives
- 2:55to drive your prioritization choices, ensuring alignment with
- 2:57business strategy. If an attribute does not impact a
- 2:59user’s goals or behavior in a way that supports those
- 3:01strategic goals, it likely belongs lower on the list or
- 3:03gets cut entirely. This prevents the common pitfall of relying
- 3:05solely on UX designer intuition for attribute importance,
- 3:07grounding your decisions in real business needs instead.
- 3:09Consider a company providing online trading tools for stocks,
- 3:12options, and futures. Their strategy might prioritize
- 3:14engaging non-professionals trading on their own,
- 3:16specifically to encourage them to try new product types like
- 3:18options and futures. In this scenario, you would prioritize
- 3:20attributes that help identify those non-professionals, such as
- 3:23their level of technical savvy or their frequency of usage.
- 3:25Demographics like age or income might matter less than their
- 3:27experience with financial products and their willingness
- 3:29to take risks. You are applying project objectives to filter
- 3:31attributes based on their impact on user goals and behavior. This
- 3:34creates a prioritized hierarchy of user attributes that reflects
- 3:36what truly matters for the current project. By focusing on
- 3:38the attributes that influence decision-making, you ensure that
- 3:41the groups you define are actionable and relevant. This
- 3:43hierarchy becomes the foundation for the next phase of your work.
- 3:45With this prioritized list in hand, you are ready to define
- 3:48and segment user groups for research and design focus. You
- 3:50will use these high-influence attributes to create initial
- 3:52models or representations of user types. These segments will
- 3:54guide your subsequent research efforts, ensuring you are
- 3:56studying the right people for the right reasons. The
- 3:58transition from a broad list to a focused hierarchy sharpens
- 4:00your entire design process.
- 4:07You now have a prioritized hierarchy of user attributes,
- 4:09which means you’re ready to define and model specific user
- 4:12groups. This step transforms abstract data into concrete
- 4:14segments that will anchor your subsequent research and design
- 4:16efforts. You’re no longer guessing who your users are;
- 4:19you’re building initial representations of user types
- 4:21based on what actually drives their behavior. These models
- 4:23guide future work by ensuring every design decision aligns
- 4:26with the goals of the people who matter most. Take that online
- 4:28trading platform example. Instead of creating generic
- 4:30personas, you segment for non- professionals trading on their
- 4:33own because your strategy prioritizes encouraging them to
- 4:35try options and futures. You create these initial models to
- 4:37focus your research efforts on the groups that support
- 4:40strategic goals. This prevents you from relying solely on UX
- 4:42designer intuition, grounding your segments in collective
- 4:44business knowledge instead. The output is a clear set of defined
- 4:47user groups, ready for deep exploration. By applying
- 4:49project objectives to filter attributes based on their impact
- 4:52on user goals and behavior, you ensure your segments are
- 4:54actionable. You’ve moved from a broad list of demographics and
- 4:56experience levels to targeted groups that drive value. Now,
- 4:59take these segmented groups and begin your next phase of
- 5:01research, confident that you’re focusing on the right people for
- 5:04the right reasons.
- 5:08Welcome to The Take. I'm joined by a fellow practitioner and
- 5:10together we're going to dig into Ranking User Attributes to
- 5:13Define User Groups — what it means in practice and what's
- 5:16worth remembering.
- 5:18[HOST] That trading example really highlighted how strategy
- 5:21dictates which attributes matter. [LEARNER] It forces you
- 5:24to ignore the noise that usually clutters our initial lists.
- 5:27[HOST] Exactly. We often default to demographics because they're
- 5:30easy to measure. [LEARNER] But age or income rarely explains
- 5:33why someone clicks a specific button. [HOST] Right. Behavior
- 5:36and intent are the actual drivers of design decisions.
- 5:39[LEARNER] I find the stakeholder interview phase the hardest part
- 5:42of this process. [HOST] Why is that. Do they resist sharing
- 5:45their internal knowledge. [LEARNER] They often defend
- 5:48their existing categories instead of questioning them.
- 5:51[HOST] You have to frame it as validating their expertise
- 5:54rather than correcting it. [LEARNER] That’s a good angle.
- 5:56It shifts the dynamic from critique to collaboration.
- 5:59[HOST] And now AI can help surface those hidden patterns
- 6:02faster than manual reviews. [LEARNER] Tools can cluster
- 6:05support tickets to reveal attributes we never thought to
- 6:08ask. [HOST] It turns anecdotal evidence into data-backed
- 6:10attribute prioritization. [LEARNER] Just make sure the AI
- 6:13doesn’t reinforce our existing biases. [HOST] Human oversight
- 6:16is still required to interpret what the clusters actually mean.
- 6:20[LEARNER] Agreed. The tool finds the signal, but we define the
- 6:23strategy.