November 18, 2022
4 min

Create a user research plan with these steps

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. 

Share this article
Author
Optimal
Workshop

Related articles

View all blog articles
Learn more
1 min read

Dive deeper into participant responses with segments

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
Learn more
1 min read

Unmoderated usability testing: a checklist

In-person moderated user testing is a valuable part of any research project. Meaning you can see first-hand how your users interact with your prototypes and products. But in-person isn’t always a viable option. What to do if your project needs user testing but it’s just not possible to get in front of your users personally? 

Let’s talk unmoderated user testing. This approach sidesteps the need to meet your participants face-to-face as it’s done entirely remotely, over the internet. By it’s very nature there are also considerable benefits to unmoderated user testing.

What is unmoderated user testing? 💻👀

In the most basic sense, unmoderated user testing removes the ‘moderated’ part of the equation. Instead of having a facilitator guide participants through the test, participants complete the testing activity by themselves and in their own time. For the most part, everything else stays the same.

The key differences are:

  • You can’t ask follow-up questions
  • You can’t use low-fidelity prototypes
  • You can’t support participants (beyond the initial instructions you send them).

Is unmoderated user testing right for your research project?

By nature, unmoderated user research does not include any direct interaction between the researcher and the study participants. This is really the biggest benefit and also the biggest drawback. 

Benefits of unmoderated usability testing 👩🏻💻

  • Speed and turnaround  - As there is no need to schedule meetings with each participant, unmoderated testing is usually much faster to initiate and complete. Depending on the study, it may be possible to launch a study and receive results in just a few hours.
  • Size of study (participant numbers) - Unmoderated user testing also allows you to collect feedback from dozens or even hundreds of users at the same time.
  • Location (local and/or international) -Testing online removes reliance on participants being physically present for the testing which broadens the ability to make contact with participants within your country or across the globe. 

If you’d like to know more about the benefits of unmoderated usability testing, take a look at our article five reasons you should consider unmoderated user testing.

Limitations of unmoderated usability testing 🚧

  • Early-prototype testing is difficult without a moderator to explain and help participants recover from errors or limitations of the prototype.
  • Participant behavior - Without a moderator, participants tend to be less engaged and behave less realistically in tasks that depend on imagination, decision-making, or emotional responses.
  • Inability to ask follow-up questions - by not being in the testing with the participant, the facilitator can’t ask further questions to get a deeper understanding of the participant’s reasoning. As you can’t rely on human judgment through a moderator being in the room with the participants and the ability to adjust the test in the moment, unmoderated usability testing needs thorough up front planning.

Because of these limitations unmoderated usability testing usually works best for evaluating live websites and apps or highly functional prototypes.  It’s great for testing activities that don’t require a lot of imagination or emotion from participants. Such as testing functionality or answering direct queries to do with your product.

What’s involved when setting up unmoderated usability testing? 🤔💭

  1. Define testing goals

With any usability testing, it pays to define your goals before getting underway with setting up the software. What do you want to know from the participants? Goals vary from test to test. Understanding your goals upfront will help you to make the correct tool choice.


  1. Define your demographic

With a clear understanding of your goal, now it’s time to consider which participants are right for your study. Think about who they are, their demographic, and where they live. Are they new users or existing? Are they experts or novices?

  1. Selecting testing software

As unmoderated studies, are done remotely, the software used to faciliate the study plays a key role in ensuring you get useful results. Without a facilitator, the software must guide the participants through the session and record what happens. Take the time to test software and select one that is right for your study.

  1. Write your own tasks and questions

Think through your goals and what you want to achieve from the testing. Many of the unmoderated testing services include study templates with generic example tasks. Remember they are templates, and your tasks and questions should be specific to your particular study. Any task instructions guiding the participants should be clear and directive.

  1. Trial session

You’ve done all of the upfront work, now it’s time to test that it works, the software does what you expect and the instructions you have written can be followed. Doing a test run is crucial, especially with unmoderated usability testing, as there won’t be a facilitator in the testing to fix any problems.

  1. Recruit participants

Having defined your target audience and demographic, now is the time to recruit participants. Ensuring you have some control over the recruitment process is important, either through screening questions or recruiting your own. There are services that  recruit from a pool of willing participants. Thiscan be a great way to get a wide range of users.

  1. Analyze results

You are likely to accumulate a lot of data from your unmoderated testing. You’ll need a way to organize and analyze the data to derive insights that are valuable. Depending on the type of usability testing you do will vary the type of results. Quantitative testing gives data-driven results and direct answers. Whereas qualitative testing through audio or video recordings of participants’ actions or comments will need time to analyze and look at behavioral observations. 

Wrap Up 🌯

Unmoderated usability testing can be a good option for your study. It may not be right for all of your studies all of the time. While it can be quick to implement and often cheaper than moderated usability testing, it still requires time and planning to ensure you get the data insights you are looking for. Following a checklist can be a great way to ensure you approach your research methodically.

Learn more
1 min read

User research and agile squadification at Trade Me

Hi, I’m Martin. I work as a UX researcher at Trade Me having left Optimal Experience (Optimal Workshop's sister company) last year. For those of you who don’t know, Trade Me is New Zealand’s largest online auction site that also lists real estate to buy and rent, cars to buy, jobs listings, travel accommodation and quite a few other things besides. Over three quarters of the population are members and about three quarters of the Internet traffic for New Zealand sites goes to the sites we run.

Leaving a medium-sized consultancy and joining Trade Me has been a big change in many ways, but in others not so much, as I hadn’t expected to find myself operating in a small team of in-house consultants. The approach the team is taking is proving to be pretty effective, so I thought I’d share some of the details of the way we work with the readers of Optimal Workshop’s blog. Let me explain what I mean…

What agile at Trade Me looks like

Over the last year or so, Trade Me has moved all of its development teams over to Agile following a model pioneered by Spotify. All of the software engineering parts of the business have been ‘squadified’. These people produce the websites & apps or provide and support the infrastructure that makes everything possible.Across Squads, there are common job roles in ‘Chapters’ (like designers or testers) and because people are not easy to force into boxes, and why should they be, there are interest groups called ‘Guilds’.The squads are self-organizing, running their own processes and procedures to get to where they need to. In practice, this means they use as many or as few of the Kanban, Scrum, and Rapid tools they find useful. Over time, we’ve seen that squads tend to follow similar practices as they learn from each other.

How our UX team fits in

Our UX team of three sits outside the squads, but we work with them and with the product owners across the business.How does this work? It might seem counter-intuitive to have UX outside of the tightly-integrated, highly-focused squads, sometimes working with product owners working on stuff that might have little to do with what’s being currently developed in the squads. This comes down to the way Trade Me divides down the UX responsibilities within the organization. Within each squad there is a designer. He or she is responsible for how that feature or app looks, and, more importantly, how it acts — interaction design as well as visual design.Then what do we do, if we are the UX team?

We represent the voice of Trade Me’s users

By conducting research with Trade Me’s users we can validate the squads’ day-to-day decisions, and help frame decisions on future plans. We do this by wearing two hats. Wearing the pointy hats of structured, detailed researchers, we look into long-term trends: the detailed behaviours and goals of our different audiences. We’ve conducted lots of one-on-one interviews with hundreds of people, including top sellers, motor parts buyers, and job seekers, as well as running surveys, focus groups and user testing sessions of future-looking prototypes. For example, we recently spent time with a number of buyers and sellers, seeking to understand their motivations and getting under their skin to find out how they perceive Trade Me.

This kind of research enables Trade Me to anticipate and respond to changes in user perception and satisfaction.Swapping hats to an agile beanie (and stretching the metaphor to breaking point), we react to the medium-term, short-term and very short-term needs of the squads testing their ideas, near-finished work and finished work with users, as well as sometimes simply answering questions and providing opinion, based upon our research. Sometimes this means that we can be testing something in the afternoon having only heard we are needed in the morning. This might sound impossible to accommodate, but the pace of change at Trade Me is such that stuff is getting deployed pretty much every day, many of which affects our users directly. It’s our job to ensure that we support our colleagues to do the very best we can for our users.

How our ‘drop everything’ approach works in practice

Screen Shot 2014-07-11 at 10.00.21 am

We recently conducted five or six rounds (no one can quite remember, we did it so quickly) of testing of our new iPhone application (pictured above) — sometimes testing more than one version at a time. The development team would receive our feedback face-to-face, make changes and we’d be testing the next version of the app the same or the next day. It’s only by doing this that we can ensure that Trade Me members will see positive changes happening daily rather than monthly.

How we prioritize what needs to get done

To help us try to decide what we should be doing at any one time we have some simple rules to prioritise:

  • Core product over other business elements
  • Finish something over start something new
  • Committed work over non-committed work
  • Strategic priorities over non-strategic priorities
  • Responsive support over less time-critical work
  • Where our input is crucial over where our input is a bonus

Applying these rules to any situation makes the decision whether to jump in and help pretty easy.At any one time, each of us in the UX team will have one or more long-term projects, some medium-term projects, and either some short-term projects or the capacity for some short-term projects (usually achieved by putting aside a long-term project for a moment).

We manage our time and projects on Trello, where we can see at a glance what’s happening this and next week, and what we’ve caught sniff of in the wind that might be coming up, or definitely is coming up.On the whole, both we and the squads favour fast response, bulleted list, email ‘reports’ for any short-term requests for user testing.  We get a report out within four hours of testing (usually well within that). After all, the squads are working in short sprints, and our involvement is often at the sharp end where delays are not welcome. Most people aren’t going to read past the management summary anyway, so why not just write that, unless you have to?

How we share our knowledge with the organization

Even though we mainly keep our reporting brief, we want the knowledge we’ve gained from working with each squad or on each product to be available to everyone. So we maintain a wiki that contains summaries of what we did for each piece of work, why we did it and what we found. Detailed reports, if there are any, are attached. We also send all reports out to staff who’ve subscribed to the UX interest email group.

Finally, we send out a monthly email, which looks across a bunch of research we’ve conducted, both short and long-term, and draws conclusions from which our colleagues can learn. All of these latter activities contribute to one of our key objectives: making Trade Me an even more user-centred organization than it is.I’ve been with Trade Me for about six months and we’re constantly refining our UX practices, but so far it seems to be working very well.Right, I’d better go – I’ve just been told I’m user testing something pretty big tomorrow and I need to write a test script!

Seeing is believing

Explore our tools and see how Optimal makes gathering insights simple, powerful, and impactful.