Menu Search
Jump to the content X X
SmashingConf London Avatar

We use ad-blockers as well, you know. We gotta keep those servers running though. Did you know that we publish useful books and run friendly conferences — crafted for pros like yourself? E.g. our upcoming SmashingConf London, dedicated to all things web performance.

A 5-Step Process For Conducting User Research

Imagine that this is what you know about me: I am a college-educated male between the ages of 35 and 45. I own a MacBook Pro and an iPhone 5, on which I browse the Internet via the Google Chrome browser. I tweet and blog publicly, where you can discover that I like chocolate and corgis. I’m married. I drive a Toyota Corolla. I have brown hair and brown eyes. My credit-card statement shows where I’ve booked my most recent hotel reservations and where I like to dine out. [Links checked February/09/2017]

If your financial services client provided you with this data, could you tell them why I’ve just decided to move my checking and savings accounts from it to a new bank? This scenario might seem implausible when laid out like this, but you’ve likely been in similar situations as an interactive designer, working with just demographics or website usage metrics.

Further Reading on SmashingMag: Link

We can discern plenty of valuable information about a customer from this data, based on what they do and when they do it. That data, however, doesn’t answer the question of why they do it, and how we can design more effective solutions to their problems through our clients’ websites, products and services. We need more context. User research helps to provide that context.

User research helps us to understand how other people live their lives, so that we can respond more effectively to their needs with informed and inspired design solutions. User research also helps us to avoid our own biases, because we frequently have to create design solutions for people who aren’t like us.

So, how does one do user research? Let me share with you a process we use at Frog5 to plan and conduct user research. It’s called the “research learning spiral.” The spiral was created by Erin Sanders, one of our senior interaction designers and design researchers. It has five distinct steps, which you go through when gathering information from people to fill a gap in your knowledge.

“The spiral is based on a process of learning and need-finding,” Sanders says. “It is built to be replicable and can fit into any part of the design process. It is used to help designers answer questions and overcome obstacles when trying to understand what direction to take when creating or moving a design forward.”

User Research
The research learning spiral is a five-step process for conducting user research, originated by Erin Sanders at Frog.

The first three steps of the spiral are about formulating and answering questions, so that you know what you need to learn during your research:

  1. Objectives
    These are the questions we are trying to answer. What do we need to know at this point in the design process? What are the knowledge gaps we need to fill?
  2. Hypotheses
    These are what we believe we already know. What are our team’s assumptions? What do we think we understand about our users, in terms of both their behaviors and our potential solutions to their needs?
  3. Methods
    These address how we plan to fill the gaps in our knowledge. Based on the time and people available, what methods should we select?

Once you’ve answered the questions above and factored them into a one-page research plan that you can present to stakeholders6, you can start gathering the knowledge you need through the selected research methods:

  1. Conduct
    Gather data through the methods we’ve selected.
  2. Synthesize
    Answer our research questions, and prove or disprove our hypotheses. Make sense of the data we’ve gathered to discover what opportunities and implications exist for our design efforts.

You already use this process when interacting with people, whether you are consciously conducting research or not. Imagine meeting a group of 12 clients who you have never worked with. You wonder if any of them has done user research before. You believe that only one or two of them have conducted as much user research as you and your team have. You decide to take a quick poll to get an answer to your question, asking everyone in the room to raise their hand if they’ve ever conducted user research. Five of them raise their hands. You ask them to share what types of user research they’ve conducted, jotting down notes on what they’ve done. You then factor this information into your project plan going forward.

In a matter of a few minutes, you’ve gone through the spiral to answer a single question. However, when you’re planning and conducting user research for an interactive project or product, each step you take through the spiral will require more time and energy, based on the depth and quantity of questions you need to answer. So, let’s take an in-depth spin through the research learning spiral. At each step of the spiral, I’ll share some of the activities and tools I use to aid my teams in managing the complexity of planning and conducting user research. I’ll also include a sample project to illustrate how those tools can support your team’s user research efforts.

Clustering Your Framing Research
I like to write my research-framing questions on sticky notes, so that I can better prioritize and cluster them. The most important questions are translated into my research objective and captured in my research plan.

1. Objectives: The Questions We Are Trying To Answer Link

Imagine that you’re in the middle of creating a next-generation program guide for TV viewers in Western Europe. Your team is debating whether to incorporate functionality for tablet and mobile users that would enable them to share brief clips from shows that they’re watching to social networks, along with their comments.

“Show clip sharing,” as the team calls it, sounds cool, but you aren’t exactly sure who this feature is for, or why users would want to use it.

Step back from the wireframing and coding, sit down with your team, and quickly discuss what you already know and understand about the product’s goal. To facilitate this discussion, ask your team to generate a series of framing questions to help them identify which gaps in knowledge they need to fill. They would write these questions down on sticky notes, one question per note, to be easily arranged and discussed.

These framing questions would take a “5 Ws and an H” structure, similar to the questions a reporter would need to answer when writing the lede of a newspaper story:

  • “Who?” questions help you to determine prospective audiences for your design work, defining their demographics and psychographics and your baseline recruiting criteria.
  • “What?” questions clarify what people might be doing, as well as what they’re using in your website, application or product.
  • “When?” questions help you to determine the points in time when people might use particular products or technologies, as well as daily routines and rhythms of behavior that might need to be explored.
  • “Where?” questions help you to determine contexts of use — physical locations where people perform certain tasks or use key technologies — as well as potential destinations on the Internet or devices that a user might want to access.
  • “Why?” questions help you to explain the underlying emotional and rational drivers of what a person is doing, and the root reasons for that behavior.
  • “How?” questions help you go into detail on what explicit actions or steps people take in order to perform tasks or reach their goals.

In less than an hour, you and your team can generate a variety of framing questions, such as:

  • “Who would share program clips?”
  • “How frequently would viewers share clips?”
  • “Why would people choose to share clips?”

Debate which questions need to be answered right away and which would be valuable to consider further down the road. “Now is your time to ask the more ‘out there’ questions,” says Lauren Serota, an associate creative director at Frog. “Why are people watching television in the first place? You can always narrow the focus of your questions before you start research… However, the exercise of going lateral and broad is good exercise for your brain and your team.”

When you have a good set of framing questions, you can prioritize and cluster the most important questions, translating them into research objectives. Note that research objectives are not questions. Rather, they are simple statements, such as: “Understand how people in Western Europe who watch at least 20 hours of TV a week choose to share their favorite TV moments.” These research objectives will put up guardrails around your research and appear in your one-page research plan.7

Don’t overreach in your objectives. The type of questions you want to answer, and how you phrase them as your research objective, will serve as the scope for your team’s research efforts. A tightly scoped research objective might focus on a specific set of tasks or goals for the users of a given product (“Determine how infrequent TV viewers in Germany decide which programs to record for later viewing”), while a more open-ended research objective might focus more on user attitudes and behaviors, independent of a particular product (“Discover how French students decide how to spend their free time”). You need to be able to reach that objective in the time frame you have alloted for the research.

Creating Design Hypotheses
In some projects, hypotheses may be expressed as written statements, which would then be taken into account when selecting methods. However, sometimes you’ll need to generate hypotheses in the form of design sketches, which would then be pulled into the research planning process and be used as stimuli in your design methods.

2. Hypotheses: What We Believe We Already Know Link

You’ve established the objectives of your research, and your head is already swimming with potential design solutions, which your team has discussed. Can’t you just go execute those ideas and ship them?

If you feel this way, you’re not alone. All designers have early ideas and assumptions about their product. Some clients may have initial hypotheses that they would like “tested” as well.

“Your hypotheses often constitute how you think and feel about the problem you’ve been asked to solve, and they fuel the early stages of work,” says Jon Freach, a design research director at Frog. Don’t be afraid to address these hypotheses and, when appropriate, integrate them into your research process to help you prove or disprove their merit. Here’s why:

  • Externalizing your hypotheses is important to becoming aware of and minimizing the influence of your team’s and client’s biases.
  • Being aware of your hypotheses will help you select the right methods to fulfill your research objective.
  • You can use your early hypotheses to help communicate what you’ve discovered through the research process. (“We believed that [insert hypothesis], but we discovered that [insert finding from research].”)

Generating research hypotheses is easy. Take your framing questions from when you formulated the objective and, as a team, spend five to eight minutes individually sketching answers to them, whether by writing out your ideas on sticky notes, sketching designs and so forth. For example, when thinking about the clip-sharing feature for your next-generation TV program guide, your team members would put their heads together and generate hypotheses such as these:

  • Attitude-related hypothesis
    “TV watchers who use social networks like to hear about their friends’ favorite TV shows.”
  • Behavior-related hypothesis
    “TV watchers only want to share clips from shows they watch most frequently.”
  • Feature-related hypothesis
    “TV watchers are more likely to share a highlight from a show if it’s popular with other viewers as well.”

3. Methods: How We Plan To Fill The Gaps In Our Knowledge Link

Once you have a defined research objective and a pile of design hypotheses, you’re ready to consider which research methods are most appropriate to achieving your objective. Usually, I’ll combine methods from more than one of the following categories to achieve my research objective. (People have written whole books about this subject. See the end of this article for further reading on user research methods and processes.)

Building a Foundation
Methods such as contextual inquiry, whereby you spend time with people where they live and work, help you build a strong foundational understanding of how they live and of potentially unmet needs.

Building a Foundation Link

Methods in this area could include surveys, observational or contextual interviews, and market and trend explorations. Use these methods when you don’t have a good understanding of the people you are designing for, whether they’re a niche community or a user segment whose behaviors shift rapidly. If you have unanswered questions about your user base — where they go, what they do and why — then you’ll probably have to draw upon methods from this area first.

Generating Inspiration and Ideas8
Methods such as card sorting can help you understand how people organize and prioritize different types of information that’s important to them — as well as help you generate new ideas and concepts that could prove critical in your interactive designs.

Generating Inspiration and Ideas Link

Methods in this area could include diary studies, card sorting, paper prototyping and other participatory design activities. Once I understand my audience’s expertise and beliefs well, I’m ready to delve deeper into what content, functionality or products would best meet their needs. This can be done by generating potential design solutions in close collaboration with research participants, as well as by receiving their feedback on early design hypotheses.

Specifically, we can do this by generating or co-creating sketches, collages, rough interface examples, diagrams and other types of stimuli, as well as by sorting and prioritizing information. These activities will help us understand how our audience views the world and what solutions we can create to fit that view (i.e. “mental models”). This helps to answer our “What,” “Where,” “When” and “How” framing questions. Feedback at this point is not meant to refine any tight design concepts or code prototypes. Instead, it opens up new possibilities.

Evaluating and Informing Design
Methods such as usability testing can help us refine and improve existing design ideas and website or application designs, as well as uncover gaps in knowledge that we may not have considered. While what’s shown above is a formal usability testing lab set-up, there are many ways to conduct similar tests9 with a wide range of tools, both on site and remotely.

Evaluating and Informing Design Link

Methods in this area could include usability testing, heuristic evaluations, cognitive walkthroughs and paper prototyping. Once we’ve identified the functionality or content that’s appropriate for a user, how do we present it to them in a manner that’s useful and delightful? I use methods in this area to refine design comps, simulations and code prototypes. This helps us to answer questions about how users would want to use a product or to perform a key task. This feedback is critical and, as part of an iterative design process, enables us to refine and advance concepts to better meet user needs.

Let’s go back to our hypothetical example, so that you can see how your research objective and hypotheses determine which methods your team will select. Take all of your hypotheses — I like to start with at least 100 hypotheses — and arrange them on a continuum:

Ranking of Research Hypotheses10
I like to write all of my research hypotheses on sticky notes, and cluster them to identify how they may be proved or disproved through different research methods.

On the left, place hypotheses related to who your users are, where they live and work, their goals, their needs and so forth. On the right, place hypotheses that have to do with explicit functionality or design solutions you want to test with users. In the center, place hypotheses related to the types of content or functionality that you think might be relevant to users. This point of this activity is not to create an absolute scale or arrangement of hypotheses that you’ve created so far. The point is for your team to cluster the hypotheses, finding important themes or affinities that will help you to select particular methods. Serota says:

“Choosing and refining your methods and approach is a design project within itself. It takes iteration, practice and time. Test things out on your friends and coworkers to see what works and the best way to ask open-ended questions.”

Back to our clip-sharing research effort. When your team looks at all of the hypotheses you’ve created to date, it will realize that using two research methods would be most valuable. The first method will be a participatory design activity, in which you’ll create with users a timeline of where and when they share their favorite TV moments with others. This will give your team foundational knowledge of situations in which clips might be shared, as well as generate opportunities for clip-sharing that you can discuss with users.

The second method will be an evaluative paper-prototyping activity, in which you will present higher-fidelity paper prototypes of ideas on how people can share TV clips. This method will help you address your hypotheses on what solutions make the most sense in sharing situations. (Using two methods is best because mixing and matching hypotheses across different categories within a research session could confuse research participants.)

Conducting the Research
You can conduct multiple methods when meeting with users. My preference is to conduct at least two different methods, moving from hearing people share stories about their lives to encouraging them to be creative in participatory activities.

4. Conduct: Gather Data Through The Methods We’ve Selected Link

The research plan is done, and you have laid out your early hypotheses on the table. Now you get to conduct the appropriate research methods. Your team will recruit eight users to meet with for one hour each over three evenings, which will allow you to speak with people when they’re most likely to be watching TV. Develop an interview guide and stimuli, and test draft versions of your activities on coworkers. Then, go into the field to conduct your research.

When you do this, it’s essential that you facilitate the research sessions properly, capturing and analyzing the notes, photos, videos and other materials that you collect as you go.

Serota also recommends thinking on your feet: “It’s all right to change course or switch something up in the field. You wouldn’t be learning if you didn’t have to shift at least a little bit.” Ask yourself, “Am I discovering what I need to learn in order to reach my objective? Or am I gathering information that I already know?” If you’re not gaining new knowledge, then one of the following is probably the reason why:

  • You’ve already answered your research questions but haven’t taken the time to formulate new questions and hypotheses in order to dig deeper (otherwise, you could stop conducting research and move immediately into synthesis).
  • The people who you believed were the target audience are, in fact, not. You’ll need to change the recruitment process (and the demographics or psychographics by which you selected them).
  • Your early design hypotheses are a poor fit. So, consider improving them or generating more.
  • The methods you’ve selected are not appropriate. So, adapt or change them.
  • You are spending all of your time in research sessions with users, rather than balancing research sessions with analysis of what you’ve discovered.
Conducting Research Synthesis
Our research teams prefer to externalize all of the data we’ve collected throughout the research process. This helps us to find fresh connections and patterns, which often lead to more powerful research findings.

5. Synthesis: Answer Our Research Questions, And Prove Or Disprove Our Hypotheses Link

Now that you’ve gathered research data, it’s time to capture the knowledge required to answer your research questions and to advance your design goals. “In synthesis, you’re trying to find meaning in your data,” says Serota. “This is often a messy process — and can mean reading between the lines and not taking a quote or something observed at face value. The why behind a piece of data is always more important than the what.”

The more time you have for synthesis, the more meaning you can extract from the research data. In the synthesis stage, regularly ask yourself and your team the following questions:

  • “What am I learning?”
  • “Does what I’ve learned change how we should frame the original research objective?”
  • “Did we prove or disprove our hypotheses?”
  • “Is there a pattern in the data that suggests new design considerations?”
  • “What are the implications of what I’m designing?”
  • “What outputs are most important for communicating what we’ve discovered?”
  • “Do I need to change what design activities I plan to do next?”
  • “What gaps in knowledge have I uncovered and might need to research at a later date?”

So, what did your team discover from your research into sharing TV clips? TV watchers do want to share clips from their favorite programs, but they are also just as likely to share clips from programs they don’t watch frequently if they find the clips humorous. They do want to share TV clips with friends in their social networks, but they don’t want to continually spam everyone in their Facebook or Twitter feed. They want to target family, close friends or individuals with certain clips that they, the user believes, would find particularly interesting.

Your team should assemble concise, actionable findings and revise its wireframes to reflect the necessary changes, based on the answers you’ve gathered. Now your team will have more confidence in the solution, and when your designs for the feature have been coded, you’ll take another spin through the research learning spiral to evaluate whether you got it right.

Further Reading On User-Research Practices And Methods Link

The spiral makes it clear that user research is not simply about card sorting, paper prototyping, usability studies and contextual interviews, per se. Those are just methods that researchers use to find answers to critical questions — answers that fuel their design efforts. Still, understanding what methods are available to you, and mastering those methods, can take some time. Below are some books and websites that will help you dive deeper into the user-research process and methods as part of your professional practice.

(al) (il)

Footnotes Link

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8
  9. 9
  10. 10
  11. 11
  12. 12
  13. 13
  14. 14

↑ Back to top Tweet itShare on Facebook

David Sherwin is Director of User Experience for at LinkedIn, as well as a Fellow at frog. He is the author of Creative Workshop: 80 Challenges to Sharpen Your Design Skills and Success by Design: The Essential Business Reference for Designers, both available from HOW Books.

  1. 1

    you know, the best way to define ux or to build for demographics is to get off your butt and just experience life. i mean if politicians lived a common life they would know what people need. no surveys and research could ever be better than experiencing something first hand. if your client is a diving shop, then become a customer, do the dive and document your way through it inuding feelings, financial concerns, emotions, thoughts, hesitant actions versus assertive actions… use your common sense and your EXPERIENCE. thats why it is called user experience. become a user having an experience. right?

    • 2

      Having a chat with the client/user goes a long way too, and sure, experiencing a product/service yourself is useful, but you’re only one person James… you can’t assume everyone experiences things the same as you.

      A very well thought through (and clearly practiced and researched) approach has been put forward here.

      Re: User Experience, this is why there are quotes around that state that you can’t design the user experience itself, you can only design FOR it.

  2. 3

    Tyler Lesperance

    September 23, 2013 1:50 pm

    Great article! My team is currently going through a rebirth and working on defining our discovery phase. I notice you have a dedicated research team at frog. Are they fully responsible for the discovery process? How long did it take to really nail down what works? I’m working with a team of < 10, what advice would you have for defining the discovery phases and processes?

    • 4

      Hello Tyler,

      Thanks for your comment.

      Our “research team” at frog is not limited to people with the title “researcher.” Our research practice is not a silo or fully responsible for discovery. We have a horizontal practice that cuts across all the different roles and disciplines, and so we’re sharing the process that I wrote about in this article with designers, technologists, strategists, project managers, and many other job functions, and those people may help lead projects.

      Discovery is also more than user research. It may include immersion in the client’s business objectives and needs, just as much as spending time with users or doing desk research to make sure you’re well informed about market trends. Build into your discovery process the appropriate time to understand what you DON’T know from the sources available to you, triangulating from that information to start plotting out what you can design with confidence and what you may need to research before or through the design process. This can take a week or two, but it’s well worth it for your team to be best informed.

      Also, I think for a smaller design studio, there may be a temptation to hire in for user research and try to build towards a specialist role over time. However, I got started in my user experience career at a smaller studio by partnering with experts and learning their processes and methods on client projects, where they helped mentor me and grow my skills. I was then able to establish processes that I felt fit best, based on having a few different perspectives on what approaches would work best. This approach may work well for you.

      Best, David

      • 5

        Hi David (and others),

        Thank you for this interesting conversation. I want to advocate for the inclusion of academic researchers in the discovery phase. I am a qualitative researcher in academia, but we are not all extremely slow and out of touch, among other complaints I hear from people in industry. Thanks to opportunities like the EPIC conference, and stellar speeches like the one Daniel Miller gave last week, these barriers are being somewhat broken down. But I do think we could benefit more from each other. We academics have a store of theoretical knowledge and deep understanding of consumer behavior and user experience. No, the theories we work with will not be exactly like the situations you find yourselves in, but the beauty of a good theory is that it should play out in many different situations. Just another thought for how to go about discovery.

  3. 6

    This is indeed an interesting article. I noticed that I have used your process (of course, without defining each step) and was able to uncovered some gaps that I needed to address.


    I have to agree with @Tyler Lesperance (comment 2). Only until I recalled my own experiences and frustrations was I able to really see through the process. Research data is fine, but nothing beats personal experience along with honesty.

    Have you ever been on a site where your friends or whatever would fuss about what is wrong with the site? For me, this is a treasure chest of good data. This is data from actual users and not fly-by-night users. I would have not known of this data if I wasn’t a member of the same site.

    I am not devaluing the merits of user research. My concern is the value of the site. Is the site what the developer wanted to express? Does the developer actually believe in the site as a commodity to serve actual users, or some mythical demographic he (or his boss) hopes to discover?

    Web users are a peculiar breed. They follow trends like kids following the popular cliques in school. The one thing that can hold true is the developer’s heart. The first step should be for the developer to apply his personal experience to the research learning spiral.

    • 7

      I agree that you need to factor your personal experience into the mix when you’re doing user research. What you see in others, along with what you know from your personal experience (and acknowledged biases!), will lead you to the right insights.

      I would caution any person doing this type of research, however, to not just look to what people SAY they want (which is one type of important information that we consider in the research process) but also look at what they DO (i.e. observing when what they say they want or need contradicts how they are using different sites, applications, products, etc). There is much to be discovered from seeing what falls into this gap, which is often surprising and leads to even stronger design solutions.

      • 8

        “…but also look at what they DO.”

        You are absolutely correct on this point. Many times I have found users simply not knowing how to operate a feature. Otherwise, they felt the feature was excellent. This is where the need for well-written instructions will prove more beneficial than upgrading a feature.

        As you say, it’s all about research data and how to put it to good use. Gathering the data is more or less public brainstorming. Analyzing the data is the critical exercise of the developer. I am understanding this is what you mean in Step 5 (Synthesize).

        • 9

          Tyler Lesperance

          September 25, 2013 8:57 am

          One thing that has stuck with me is that users don’t know what they do, so they can’t tell you. Meaning, if you were to ask a user “What is your typical process when doing this?” they won’t be able to remember every action they take, so they will fill in the gaps with what they think an ideal process would be, even if that’s what true to their experience. Observation of the process is definitely a very worthwhile activity. What I’ve included in user interviews is to describe a time when you had the best (or worst) experience doing X. These times are much more likely to be memorable to the user and they will also be describing points/processes that they loved/hated, which is also valuable data.

  4. 10

    I thought, having the scientific method been devised by Galilei in the 16th century, the news had reached everybody by now

  5. 11

    Great and detailed article! it definitely helps me a lot.

  6. 12

    Thank you for sharing; a very generous & useful primer on the key steps in the process.

  7. 13

    Ramiro Pereira de Magalhães

    January 30, 2014 10:08 am


    I loved the article. It’s indeed a very inspiring primer on the user research topic. Congratulations.

    What I missed though is what I think it might be a “sub-step” of the Conduct step: finding users. This is a rather complicated step since the real users might simply not be available. Recruiting such users is also an interesting problem that teams might tackle, since the appropriate “persona” migh be hard to find in a timely fashion. Reward the participants might also be an issue, because an inappropriate reward could produce the wrong motivations.

    Any thoughts on this “sub-step”?

  8. 14

    Can you detail how you’ve used co-creation? Specifically whether it was to create low or high fidelity prototypes or just conceptual ideas, at what point in the project lifecycle, and to what extent did the researcher/designer contribute?

    I’ve been wary of trying it since users can’t be expected to create a solution, and also there are many technical and business requirements and restrictions they’re not aware of.

    I have done something at a conceptual level that could be deemed co-creation, where I together with users, drawn a timeline of what they do in a travel booking process, then gone through that timeline with them and identified when they would want information about a certain service. This was very useful but I thought of it more as a mental model interview / exercise than co-creation.



  9. 15

    You should try project management tool! Its the same style as your Post-It layouts!

  10. 16

    matilda tarimo

    November 19, 2014 9:07 am

    I Thanks for sharing steps for conducting research, proceed to providing knowdge

  11. 17

    How is this any different from the scientific method?

  12. 18

    I find this conversation to be very interesting. Many thanks to all of you guys for all of the comments. I’m currently studying with a research team and I find this conversation helpful . Keep it up !!!


↑ Back to top