Why Understanding Users Has Never Been Easier...or Harder

Our exciting new feature, segments, saves time by allowing you to create and save groups of participant responses based on various filters. Think of it as your magic wand to effortlessly organize and scrutinize the wealth of data and insight you collect in your studies. Even more exciting is that the segments are available in all our quantitative study tools, including Optimal Sort, Treejack, Chalkmark, and Questions.

‍

What exactly are segments?

‍

In a nutshell, segments let you effortlessly create and save groups of participants' results based on various filters, saving you and the team time and ensuring you are all on the same page. 

A segment represents a demographic within the participants who completed your study. These segments can then be applied to your study results, allowing you to easily view and analyze the results of that specific demographic and spot the hidden trends.

‍

What filters can I use?

‍

Put simply, you've got a treasure trove of participant data, and you need to be able to slice and dice it in various ways. Segmenting your data will help you dissect and explore your results for deeper and more accurate results.

‍

Question responses: Using a screener survey or pre - or post-study questions with pre-set answers (like multi-choice), you can segment your results based on their responses.

‍

URL tag: If you identify participants using a unique identifier such as a URL tag, you can select these to create segments.

‍

Tree test tasks, card sort categories created, first click test and survey responses: Depending on your study type, you can create a segment to categorize participants based on their response in the study. 

‍

Time taken: You can select the time taken filter to view data from those who completed your study in a short space of time. This may highlight some time wasters who speed through and probably haven’t provided you with high-quality responses. On the other hand, it can provide insight into A/B tests for example, it could show you if it’s taking participants of a tree test longer to find a destination in one tree or another.

‍

With this feature, you can save and apply multiple segments to your results, using a combination of AND/OR logic when creating conditions. This means you can get super granular insights from your participants and uncover those gems that might have otherwise remained hidden.

‍

When should you use segments?

‍

This feature is your go-to when you have results from two or more participant segments. For example, imagine you're running a study involving both teachers and students. You could focus on a segment that gave a specific answer to a particular task, question, or card sort. It allows you to drill down into the nitty-gritty of your data and gain more understanding of your customers.

‍

How segments help you to unlock data magic 💫

‍

Let's explore how you can harness the power of segments:

‍

Save time: Create and save segments to ensure everyone on your team is on the same page. With segments, there's no room for costly data interpretation mishaps as everyone is singing from the same hymn book.

‍

Surface hidden trends: Identifying hidden trends or patterns within your study is much easier.  With segments,  you can zoom in on specific demographics and make insightful, data-driven decisions with confidence.

‍

Organized chaos: No more data overload! With segments, you can organize participant data into meaningful groups, unleashing clarity and efficiency.

‍

How to create a segment

‍

Ready to take segments for a spin?  To create a new segment or edit an existing one, go to  Results > Participants > Segments. Select the ‘Create segment’ button and select the filters you want to use. You can add multiple conditions, and save the segment.  To select a segment to apply to your results, click on ‘All included participants’ and select your segment from the drop-down menu.  This option will apply to all your results in your study. 

‍

We can't wait to see the exciting discoveries you'll make with this powerful tool. Get segmenting, and let us know what you think! 

‍

Help articles
‍

How to add a group tag in a study URL for participants
‍
How to integrate with a participant recruitment panel

‍

Product, design and research teams today are drowning in user data while starving for user understanding. Never before have teams had such access to user information, analytics dashboards, heatmaps, session recordings, survey responses, social media sentiment, support tickets, and endless behavioral data points. Yet despite this volume of data, teams consistently build features users don't want and miss needs hiding in plain sight.

‍

It’s a true paradox for product, design and research teams: more information has made genuine understanding more elusive. 

‍

Because with  all this data, teams feel informed. They can say with confidence: "Users spend 3.2 minutes on this page," "42% abandon at this step," "Power users click here." But what this data doesn't tell you is Why. 

‍

The Difference between Data and Insight

‍

Data tells you what happened. Understanding tells you why it matters.

‍

Here’s a good example of this: Your analytics show that 60% of users abandon a new feature after first use. You know they're leaving. You can see where they click before they go. You have their demographic data and behavioral patterns.

‍

But you don't know:

‍

• Were they confused or simply uninterested?
• Did it solve their problem too slowly or not at all?
• Would they return if one thing changed, or is the entire approach wrong?
• Are they your target users or the wrong segment entirely?

‍

One team sees "60% abandonment" and adds onboarding tooltips. Another talks to users and discovers the feature solves the wrong problem entirely. Same data, completely different understanding.

‍

Modern tools make it dangerously easy to mistake observation for comprehension, but some aspects of user experience exist beyond measurement:

‍

• Emotional context, like the frustration of trying to complete a task while handling a crying baby, or the anxiety of making a financial decision without confidence.
• The unspoken needs of users which can only be demonstrated through real interactions. Users develop workarounds without reporting bugs. They live with friction because they don't know better solutions exist.
• Cultural nuances that numbers don't capture, like how language choice resonates differently across cultures, or how trust signals vary by context.
• Data shows what users do within your current product. It doesn't reveal what they'd do if you solved their problems differently to help you identify new opportunities. 

‍

Why Human Empathy is More Important than Ever 

‍

The teams building truly user-centered products haven't abandoned data but they've learned to combine quantitative and qualitative insights. 

‍

• Combine analytics (what happens), user interviews (why it happens), and observation (context in which it happens).
• Understanding builds over time. A single study provides a snapshot; continuous engagement reveals the movie.
• Use data to form theories, research to validate them, and real-world live testing to confirm understanding.
• Different team members see different aspects. Engineers notice system issues, designers spot usability gaps, PMs identify market fit, researchers uncover needs.

‍

Adding AI into the mix also emphasizes the need for human validation. While AI can help significantly speed up workflows and can augment human expertise, it still requires oversight and review from real people. 

‍

AI can spot trends humans miss, processing millions of data points instantly but it can't understand human emotion, cultural context, or unspoken needs. It can summarize what users say but humans must interpret what they mean.

‍

Understanding users has never been easier from a data perspective. We have tools our predecessors could only dream of.  But understanding users has never been harder from an empathy perspective. The sheer volume of data available to us creates an illusion of knowledge that's more dangerous than ignorance.

‍

The teams succeeding aren't choosing between data and empathy, they're investing equally in both. They use analytics to spot patterns and conversations to understand meaning. They measure behavior and observe context. They quantify outcomes and qualify experiences.

‍

Because at the end of the day, you can track every click, measure every metric, and analyze every behavior, but until you understand why, you're just collecting data, not creating understanding.

‍

There’s not much a parent won’t do to ensure their child has the best chance of succeeding in life. Unsurprisingly, things are much the same in product development. Whether it’s a designer, manager, developer or copywriter, everyone wants to see the product reach its full potential.

‍

Key to a product’s success (even though it’s still not widely practiced) is UX research. Without research focused on learning user pain points and behaviors, development basically happens in the dark. Feeding direct insights from customers and users into the development of a product means teams can flick the light on and make more informed design decisions.

‍

While the benefits of user research are obvious to anyone working in the field, it can be a real challenge to convince others of just how important and useful it is. We thought we’d help.

‍

Define user research

‍

If you want to sell the importance of UX research within your organization, you’ve got to ensure stakeholders have a clear understanding of what user research is and what they stand to gain from backing it.

‍

In general, there are a few key things worth focusing on when you’re trying to explain the benefits of research:

‍

• More informed design decisions: Companies make major design decisions far too often without considering users. User research provides the data needed to make informed decisions.
• Less uncertainty and risk: Similarly, research reduces risk and uncertainty simply by giving companies more clarity around how a particular product or service is used.
• Retention and conversion benefits: Research means you’ll be more aligned with the needs of your customers and prospective customers.

‍

Use the language of the people you’re trying to convince. A capable UX research practice will almost always improve key business metrics, namely sales and retention.

‍

The early stages

‍

When embarking on a project, book in some time early in the process to answer questions, explain your research approach and what you hope to gain from it. Here are some of the key things to go over:

‍

• Your objectives: What are you trying to achieve? This is a good time to cover your research questions.
• Your research methods: Which methods will you be using to carry out your research? Cover the advantages of these methods and the information you’re likely to get from using them.
• Constraints: Do you see any major obstacles? Any issues with resources?
• Provide examples: Nothing shows the value of doing research quite like a case study. If you can’t find an example of research within your own organization, see what you can find online.

‍

Involve others in your research

‍

When trying to convince someone of the validity of what you’re doing, it’s often best to just show them. There are a couple of effective ways you can do this – at a team or individual level and at an organizational level.

‍

We’ll explain the best way to approach this below, but there’s another important reason to bring others into your research. UX research can’t exist in a vacuum – it thrives on integration and collaboration with other teams. Importantly, this also means working with other teams to define the problems they’re trying to solve and the scope of their projects. Once you’ve got an understanding of what they’re trying to achieve, you’ll be in a better position to help them through research.

‍

Educate others on what research is

‍

Education sessions (lunch-and-learns) are one of the best ways to get a particular team or group together and run through the what and why of user research. You can work with them to work out what they’d like to see from you, and how you can help each other.

‍

Tailor what you’re saying to different teams, especially if you’re talking to people with vastly different skill sets. For example, developers and designers are likely to see entirely different value in research.

‍

Collect user insights across the organization

‍

Putting together a comprehensive internal repository focused specifically on user research is another excellent way to grow awareness. It can also help to quantify things that may otherwise fall by the wayside. For example, you can measure the magnitude of certain pain points or observe patterns in feature requests. Using a platform like Notion or Confluence (or even Google Drive if you don’t want a dedicated platform), log all of your study notes, insights and research information that you find useful.

‍

Whenever someone wants to learn more about research within the organization, they’ll be able to find everything easily.

‍

Bring stakeholders along to research sessions

‍

Getting a stakeholder along to a research session (usability tests and user interviews are great starting points) will help to show them the value that face-to-face sessions with users can provide.

‍

To really involve an observer in your UX research, assign them a specific role. Note taker, for example. With a short briefing on best-practices for note taking, they can get a feel for what’s like to do some of the work you do.

‍

You may also want to consider bringing anyone who’s interested along to a research session, even if they’re just there to observe.

‍

Share your findings – consistently

‍

Research is about more than just testing a hypothesis, it’s important to actually take your research back to the people who can action the data.

‍

By sharing your research findings with teams and stakeholders regularly, your organization will start to build up an understanding of the value that ongoing research can provide, meaning getting approval to pursue research in future becomes easier. This is a bit of a chicken and egg situation, but it’s a practice that all researchers need to get into – especially those embedded in large teams or organizations.

‍

Anything else you think is worth mentioning? Let us know in the comments.

‍

Read more

‍

• Selling your design recommendations to clients and colleagues – Guest writer Jeff Tang outlines some of his techniques for presenting UX recommendations and answering objections.
• Quantifying the ROI of UX – Ashlea McKay delves into one of the toughest UX questions to answer: “What do we get for our money?”
• How to lead a UX team – With user-centered design growing in organizations around the world, we’ll need capable leaders to run UX teams.
• How do I explain what UX is? – Ashlea McKay covers how you can explain UX to people who may not necessarily have familiarity with the field.