Affinity mapping - an introduction

A great user experience (UX) is one of the largest drivers of growth and revenue through user satisfaction. However, when budgets get tight, or there is a squeeze on timelines, user research is one of the first things to go. Often at the cost of user satisfaction.  

‍

This short sighted view can mean project managers are preoccupied with achieving milestones and short term goals. And UX teams get stuck researching products they weren’t actually involved with developing. As a result no one has the space and understanding to really develop a product that speaks to users needs, desires and wants. There must  be a better way to produce a product that is user-driven.  Thankfully there is.

‍

What is user research and why should project managers care about it? 👨🏻💻

‍

User research is an important part of the product development process. Primarily, user research involves using different research methods to gather information about your end users. 

‍

Essentially it aims to create the best possible experience for your users by listening and learning directly from those that already or potentially will use your product. You might conduct interviews to help you understand a particular problem, carry out a tree test to identify bottlenecks or problems in your navigation, or do some usability testing to directly observe your users as they perform different tasks on your website or in your app. Or a combination of these to understand what users really want.

‍

To a project manager and team, this likely sounds fairly familiar, that any project can’t be managed in a silo. Regular check-ins and feedback are essential to making smart decisions. The same with UX research. It can make the whole process quicker and more efficient. By taking a step back, digging into your users’ minds, and gaining a fuller understanding of what they want upfront, it can curtail short-term views and decisions.

‍

Bringing more user research into your development process has major benefits for the team, and the ultimately the quality of that final product. There are three key benefits:

‍

1. Saves your development team time and effort. Ensuring the team is working on what users want, not wasting time on features that don’t measure up.
2. Gives your users a better experience by meeting their requirements.
3. Helps your team innovate quickly by understanding what users really want.

‍

As a project manager, making space and planning for user research can be one of the best ways to ensure the team is creating a product that truly is user-driven.

‍

How to bring research into your product development process 🤔

‍

There are a couple of ways you can bring UX research into your product development process. 

‍

1. Start with a dedicated research project.
2. Integrate UX research throughout the development project.

‍

It can be more difficult to integrate UX research throughout the process, as it means planning the project with various stages of research built in to check the development of features. But ultimately this approach is likely to turn out the best product. One that has been considered, checked and well thought out through the whole product development process. To help you on the way we have laid out 6 key steps to help you integrate UX research into your product development process.

‍

6 key steps to integrate UX research 👟

‍

Step 1: Define your research questions

‍

Take a step back, look at your product and define your research questions. 

‍

It may be tempting just to ask, ‘do users like our latest release?’ This however does not get to why or what your users like or don’t like. Try instead:

• What do our users really want from our product?
• Where are they currently struggling while using our website?
• How can we design a better product for our users?

‍

These questions help to form the basis of specific questions about your product and specific areas of research to explore which in turn help shape the type of research you undertake.

‍

Step 2: Create your research plan

‍

With a few key research questions to focus on, it’s time to create your research plan.

‍

A great research plan covers your project’s goals, scope, timing, and deliverables. It’s essential for keeping yourself organized but also for getting key stakeholder signoff.

‍

Step 3: Prepare any research logistics

‍

Every project plan requires attention to detail including a user research project. And with any good project there are a set of steps to help make sense of it.

‍

1. Method: Based on your questions, what is the best user research method to use? 
2. Schedule: When will the research take place? How long will it go on for? If this is ongoing research, plan how it will be implemented and how often.
3. Location: Where will the research take place? 
4. Resources: What resources do you need? This could be technical support or team members.
5. Participants: Define who you want to research. Who is eligible to take part in this research? How will you find the right people?
6. Data: How will you capture the research data? Where will it be stored? How will you analyze the data and create insights and reports that can be used?
7. Deliverables: What is the ultimate goal for your research project?

‍

Step 4: Decide which method will be used

‍

Many user research methods benefit from an observational style of testing. Particularly if you are looking into why users undertake a specific task or struggle.

‍

Typically, there are two approaches to testing:

‍

1. Moderated testing is when a moderator is present during the test to answer questions, guide the participant, or dig deeper with further questions.
2. Unmoderated testing is when a participant is left on their own to carry out the task. Often this is done remotely and with very specific instructions.Your key questions will determine which method will works best for your research.  Find our more about the differences.

‍

Step 5: Run your research session

‍

It’s time to gather insights and data. The questions you are asking will influence how you run your research sessions and the methods you’ve chosen. 

‍

If you are running surveys you will be asking users through a banner or invitation to fill out your survey. Unmoderated and very specific questions. Gathering qualitative data and analyzing patterns.

‍

If you’re using something qualitative like interviews or heat mapping, you’ll want to implement software and gather as much information as possible.

‍

Step 6: Prepare a research findings report and share with stakeholders

‍

Analyze your findings, interrogate your data and find those insights that dive into the way your users think. How do they love your product? But how do they also struggle?

‍

Pull together your findings and insights into an easy to understand report. And get socializing. Bring your key stakeholders together and share your findings. Bringing everyone across the findings together can bring everyone on the journey. And for the development process can mean decisions can be user-driven. 

‍

Wrap Up 🥙

‍

Part of any project, UX research should be essential to developing a product that is user-driven. Integrating user research into your development process can be challenging. But with planning and strategy it can be hugely beneficial to saving time and money in the long run. 

We all know that building a robust information architecture (IA) can make or break your product. And getting it right can rely on robust user research. Especially when it comes to creating human-centered, intuitive products that deliver outstanding user experiences.

‍

But what are the best methods to test your information architecture? To make sure that your focus is on building an information architecture that is truly based on what your users want, and need.

‍

What is user research? 🗣️🧑🏻💻

‍

With all the will in the world, your product (or website or mobile app) may work perfectly and be as intuitive as possible. But, if it is only built on information from your internal organizational perspective, it may not measure up in the eyes of your user. Often, organizations make major design decisions without fully considering their users. User research (UX) backs up decisions with data, helping to make sure that design decisions are strategic decisions. 

‍

Testing your information architecture can also help establish the structure for a better product from the ground up. And ultimately, the performance of your product. User experience research focuses your design on understanding your user expectations, behaviors, needs, and motivations. It is an essential part of creating, building, and maintaining great products. 

‍

Taking the time to understand your users through research can be incredibly rewarding with the insights and data-backed information that can alter your product for the better. But what are the key user research methods for your information architecture? Let’s take a look.

‍

Research methods for information architecture ⚒️

‍

There is more than one way to test your IA. And testing with one method is good, but with more than one is even better. And, of course, the more often you test, especially when there are major additions or changes, you can tweak and update your IA to improve and delight your user’s experience.

‍

Card Sorting 🃏

‍

Card sorting is a user research method that allows you to discover how users understand and categorize information. It’s particularly useful when you are starting the planning process of your information architecture or at any stage you notice issues or are making changes. Putting the power into your users’ hands and asking how they would intuitively sort the information. In a card sort, participants sort cards containing different items into labeled groups. You can use the results of a card sort to figure out how to group and label the information in a way that makes the most sense to your audience. 

‍

There are a number of techniques and methods that can be applied to a card sort. Take a look here if you’d like to know more.

‍

Card sorting has many applications. It’s as useful for figuring out how content should be grouped on a website or in an app as it is for figuring out how to arrange the items in a retail store.You can also run a card sort in person, using physical cards, or remotely with online tools such as OptimalSort.

‍

Tree Testing 🌲

‍

Taking a look at your information architecture from the other side can also be valuable. Tree testing is a usability method for evaluating the findability of topics on a product. Testing is done on a simplified text version of your site structure without the influence of navigation aids and visual design.

‍

Tree testing tells you how easily people can find information on your product and exactly where people get lost. Your users rely on your information architecture – how you label and organize your content – to get things done.

‍

Tree testing can answer questions like:

• Do my labels make sense to people?
• Is my content grouped logically to people?
• Can people find the information they want easily and quickly? If not, what’s stopping them?

‍

Treejack is our tree testing tool and is designed to make it easy to test your information architecture. Running a tree test isn’t actually that difficult, especially if you’re using the right tool. You’ll  learn how to set useful objectives, how to build your tree, write your tasks, recruit participants, and measure results.

‍

Combining information architecture research methods 🏗

‍

If you are wanting a fully rounded view of your information architecture, it can be useful to combine your research methods.

‍

Tree testing and card sorting, along with usability testing, can give you insights into your users and audience. How do they think? How do they find their way through your product? And how do they want to see things labeled, organized, and sorted? 

‍

If you want to get fully into the comparison of tree testing and card sorting, take a look at our article here, which compares the options and explains which is best and when. 

Are we exaggerating when we say that the way the researchers run and analyze user interviews hasn’t changed in 20 years? We don’t think so. When we talk to our customers to try and understand their current workflows, they look exactly the same as they did when we started this business 17 years ago: record, transcribe, analyze manually, create reports. See the problem?

‍

Despite  advances in technology across every industry, the fundamental process of conducting and analyzing user interviews has remained largely unchanged. While we've transformed how we design, develop, and deploy products, the way we understand our users is still trapped in workflows that would feel familiar to product, design and research teams from decades ago.

‍

The Same Old Interview Analysis Workflow 

‍

For most researchers, in the best case scenario, Interview analysis can take several hours over the span of multiple days. Yet in that same timeframe, in part thanks to new and emerging AI tools, an engineering team can design, build, test, and deploy new features. That just doesn't make sense.

‍

The problem isn't that researchers  lack tools. It's that they haven’t had the right ones. Most tools focus on transcription and storage, treating interviews like static documents rather than dynamic sources of intelligence. Testing with just 5 users can uncover 85% of usability problems, yet most teams struggle to complete even basic analysis in time to influence product decisions. Luckily, things are finally starting to change.

‍

When it comes to user research, three things are happening in the industry right now that are forcing a transformation:

‍

1. The rise of AI means UX research matters more than ever. With AI accelerating product development cycles, the cost of building the wrong thing has never been higher. Companies that invest in UX early cut development time by 33-50%, and with AI, that advantage compounds exponentially.
2. We're drowning in data and have fewer resources.  We’re seeing the need for UX research increase, while simultaneously UX research teams are more resource constrained than ever. Tasks like analyzing hours of video content to gather insights, just isn’t something teams have time for anymore. 
3. AI finally understands research. AI has evolved to a place where it can actually provide valuable insights. Not just transcription. Real research intelligence that recognizes patterns, emotions, and the gap between what users say and what they actually mean.

‍

A Dirty Little Research Secret + A Solution 

‍

We’re just going to say it; most user insights from interviews never make it past the recording stage. When it comes to talking to users, the vast majority of researchers in our audience talk about recruiting pain because the most commonly discussed challenge around interviews is usually finding enough participants who match their criteria. But on top of the challenge of finding the right people to talk to, there’s another challenge that’s even worse: finding time to analyze what users tell us. But, what if you had a tool where using AI, the moment you uploaded an interview video, key themes, pain points, and opportunities surfaced automatically? What if you could ask your interview footage questions and get back evidence-based answers with video citations?

‍

This isn't about replacing human expertise, it's about augmenting  it. AI-powered tools can process and categorize data within hours or days, significantly reducing workload. But more importantly, they can surface patterns and connections that human analysts might miss when rushing through analysis under deadline pressure. Thanks to AI, we're witnessing the beginning of a research renaissance and a big part of that is reimagining the way we do user interviews.

‍

Why AI for User Interviews is a Game Changer 

‍

When interview analysis accelerates from weeks to hours, everything changes.

‍

Product teams can validate ideas before building them. Design teams can test concepts in real-time. Engineering teams can prioritize features based on actual user need, not assumptions. Product, Design and Research teams who embrace AI to help with these workflows, will be surfacing insights, generating evidence-backed recommendations, and influencing product decisions at the speed of thought.

‍

We know that 32% of all customers would stop doing business with a brand they loved after one bad experience. Talking to your users more often makes it possible to prevent these experiences by acting on user feedback before problems become critical. When every user insight comes with video evidence, when every recommendation links to supporting clips, when every user story includes the actual user telling it, research stops being opinion and becomes impossible to ignore. When you can more easily gather, analyze and share the content from user interviews those real user voices start to get referenced in executive meetings. Product decisions begin to include user clips. Engineering sprints start to reference actual user needs. Marketing messages reflect real user voices and language.

The best product, design and research teams are already looking for tools that can support this transformation. They know that when interviews become intelligent, the entire organization becomes more user-centric. At Optimal, we're focused on improving the traditional user interviews workflow by incorporating revolutionary AI features into our tools. Stay tuned for exciting updates on how we're reimagining user interviews.