Skip to content
Home » Google Career Certificates » Google UX Design Professional Certificate » Start the UX Design Process: Empathize, Define, and Ideate » Module 1: Empathizing with users and defining pain points

Module 1: Empathizing with users and defining pain points

Get ready to begin the design process for a new portfolio project: a mobile app! This part of the course will focus on empathizing with users, which is the first phase of the design process. You’ll think through the needs of your potential users to build empathy maps and create personas. These hands-on activities will help you understand user perspectives and pain points.

Learning Objectives

  • Develop plans to present portfolio work as part of an interview process
  • Research and practice responding to common interview questions
  • Demonstrate how to build rapport with interviewers
  • Define best practices for successful interviews
  • Prepare a UX portfolio website for job interviews
  • Complete an empathy exercise to understand users
  • Build an empathy map
  • Explain user pain points
  • Create personas

Introduction to Course 2


Video: Introduction to Course 2: Empathize, Define, and Ideate

Recap of Previous Learning:

  • UX Basics: Importance of user experience, tools and frameworks, design sprint process.
  • Career Prep: Portfolio building, personal branding, online presence development.

Instructor Background:

  • Emily is a UX researcher at Google with 10+ years of experience.
  • Works on Google Assistant, helping families improve communication.
  • Passionate about understanding how people learn and bringing user voices into product development.

What’s Next: Deep Dive into Empathy

  • Understanding Users: Learning how to empathize with users and anticipate their thoughts and feelings about your product.
  • Defining Problems: Creating effective problem statements to focus design solutions.
  • Ideation: Generating multiple ideas for addressing user needs.

Specific Topics to Explore:

  • Empathy maps
  • Pain points
  • Personas
  • User stories
  • Happy paths & edge cases
  • User journey maps
  • Problem statements
  • Hypothesis statements
  • Accessibility considerations

Hi there.
Welcome to the next course. I’m Emily, a UX researcher at Google,
and I’ll be your instructor. Before we get started, how about a quick
recap of what we’ve covered so far? We started with the basics.
You learned why user experience is so important in your role
as an entry-level UX designer. Then you were introduced to
common tools, frameworks, and platforms used in UX design, and we walked
through the steps of a design sprint. Before too long,
you were thinking like a designer and started developing your portfolio,
personal brand, and online profiles. Everything you’ve learned so far has given you a solid foundation
that we’ll continue to build upon. Over the next several videos, you’ll learn how empathy is key to creating
phenomenal experiences for our users. Every activity you do
will bring you closer to empathizing with your potential user. You’ll also learn how designers
predict what a user or group of users might think as
they interact with your product. And more importantly, you’ll be able to anticipate how users
might feel about the experience. Next, you’ll bring together
everything you know about your potential user to define
your problem statement. Then we’ll give you tools to ideate
solutions to address user problems. Before we dive deeper into what empathy
is and how it’s applied in UX design, you might want to know
a little bit more about me. I’ve been working in UX research for
more than 10 years. Right now, I work on the Google Assistant,
where I help families communicate and coordinate so they can focus on what
really matters: being together. I’ve always been interested in
understanding how people, and kids in particular, learn. I care about bringing user perspectives
into the product development life cycle, and being a UX researcher
lets me do just that. I’m so excited to share my passion for
creating great user experiences with you. Let’s get to it! Coming up, we’ll learn
how to empathize with users, build an empathy map,
understand user pain points, explore personas, write user stories,
identify happy paths and edge cases, discover the benefits of user journey
maps, write problem statements and hypothesis statements. And we’ll consider how accessibility
fits into all of this. So let’s get started!

Reading: Welcome to Course 2

Reading

Reading: Introduction to the first portfolio project

Reading

Reading: Choose your portfolio prompt

Reading

Learn about UX design portfolio


Video: Lisa – Create a UX design portfolio

Lisa’s Journey into UX Design

  • Starting Point: Traditional graphic design/branding background, no prior UX work experience.
  • Strategic Rebranding: Lisa identified her interest in visual design and positioned herself as a “visual designer” within the UX field.
  • Portfolio Makeover: She didn’t start from scratch, but focused on reframing her existing projects to emphasize UX-centric storytelling and problem-solving.
  • Faking it Till Making It: Despite lacking knowledge of common UX tools and software, Lisa landed a job at Google due to her:
    • Strong conceptual thinking
    • Curiosity and eagerness to learn.

Key Takeaway: It’s less about what skills you have initially and more about demonstrating your potential, passion, and ability to adapt when changing career paths.

I’m Lisa, I’m a visual
designer at Google. A visual designer at Google is a user experience designer that really focuses in on the creative expression
of a user experience. When I decided I wanted to get into user experience design, I had no experience. I didn’t have a
real first job yet. I had a very traditional
graphic design and branding portfolio. I had new projects from doing an internship for nine
months that I’d created. But then I decided that
I wanted to go into UX and I needed to
recreate that portfolio, having no work experience in UX, to still be a user
experience portfolio. When I was just applying
to user experience jobs, I knew I wanted to be
a visual designer. Even though at heart I was still unsure if I wanted
to call myself that, I knew it was important
to identify myself like that strategically
in the portfolio, so I said that I was
a visual designer. The actual portfolio in itself, I had to completely
redo the layout. I don’t need to
start from scratch, I don’t need to panic,
everything is there. I just need to reroute
the way that I am storytelling and bringing some
of these elements to life, so it does feel more like
a user experience project. I really focused in on the storytelling and the thinking like user experience designer. It was interesting because
when I got to Google, I felt, okay, I can
think like this. I just now need to catch
up on the day-to-day, the tools, the software, the things that most
people know going in, that somehow I faked
it till I made it. The funny part about
that is my team didn’t seem to care that I
didn’t know any of that. They were just happy
that I was curious, that I was hungry to learn, that I was anxious to get
started on a project. What really defined
how I got into the job was a curiosity to
learn, and to grow, and to project myself as a
ambitious visual designer.

Reading: Review: Explore UX design portfolios

Reading

Practice Quiz: Test your knowledge on UX portfolios

Typically, a UX designer at the beginning of their career is most likely to find entry-level work at what type of company? Select all that apply.

Why is it important for an entry-level designer to present their portfolio to potential employers? Select all that apply.

Video: Introduction to UX design portfolios

What is a UX Portfolio?

  • Not Just Pretty Pictures: It’s a curated showcase of your UX design work. Think of it as your professional highlight reel.
  • Purpose: Demonstrates your design skills, process, and problem-solving abilities to potential employers.
  • Modern Format: Portfolios are usually websites, making them easy to share and update.

Why a Portfolio is Crucial for UX

  • UX is a Visual Field: You need to show, not just tell, what you can do.
  • Standing Out: A strong portfolio helps you stand out in a competitive job market.
  • Website as a UX Skill: Even the design of your portfolio site demonstrates your understanding of user experience.

What’s Next

  • You’ll build your own portfolio website throughout this program as you complete projects.
  • You’ll explore examples of real-world portfolios to see how successful UX designers present themselves.

As we mentioned at the
beginning of the program, our goal is for you to
learn the skills you need to get a job as an
entry-level UX designer. But how do you demonstrate those skills during the
job application process? That’s where portfolios come in. In this video, you’ll
learn what a portfolio is and why UX designers use them. A portfolio is a collection
of work that you’ve created that shows your
skills in a certain area, like painting,
photography, or UX design. UX design is a creative field, so it’s important to show
hiring managers examples of your work and demonstrate the skills you can
bring to the job. In the past, portfolios
were usually a physical collection of work like a giant briefcase
full of drawings. But in today’s world, it’s more likely that your portfolio will
be on a website, which is much easier
to update and share. Next, you’ll build
your own website to showcase your
future portfolio. You don’t need to
know how to write code or have any
work to include yet. As you build your own projects
throughout this program, you’ll add them to
this new portfolio. Sound fun? It is. Creating a showcase of
your work and skills is a great way to start feeling like a part of the UX
design community. Keep in mind that the design of the website itself
is also important. Having a well-designed
website is another way to demonstrate that you understand the principles of UX design. You wouldn’t want
your website to have a bad user experience when you’re applying
for a job in UX. As you design the website, you want your portfolio to tell a story and grab the
user’s attention. This will help you stand out. After all, the user might be a recruiter or a client
interested in offering you a job. Next up, you’ll meet
entry-level UX designers, explore real-world
portfolios, and learn how those portfolios help lead
to jobs in UX design. Ready? Let’s get started.

Start a UX design portfolio


Video: Introduction to website builders

Why Website Builders Are Great

  • User-Friendly: No coding knowledge needed! They use WYSIWYG editors (What You See Is What You Get) for easy formatting.
  • Helpful Tools: Templates provide structure, and support teams can assist you as needed.

Popular Options (each has pros and cons):

  • Wix: Very beginner-friendly, lots of templates, some specifically for portfolios.
  • Squarespace: Known for beautiful visuals and strong blogging function. Offers flexibility for customization.
  • Webflow: Trendy styles, highly customizable, but requires some coding knowledge.

Additional Considerations

  • Personal Branding: Consider purchasing a custom domain name (your website address) for better professional presence.
  • Customization: Even with templates, you’ll personalize your site to reflect your unique style and skills.

Next Steps

  1. Explore each website builder in more detail (links will be provided)
  2. Choose the one that best suits your needs and interests.

What beneficial features do website builders offer UX designers when building a personalized online portfolio? Select all that apply.

Tutorials with guidance on how to add text and multimedia elements

Website builders offer user-friendly editing features, tutorials and even some templates so users do not need to start from scratch.

User-friendly editing features

These builders feature user-friendly WYSIWYG editors, offer tutorials and even some templates to start from. WYSIWYG is an acronym that means: what you see is what you get. Common website builders include Squarespace, Wix, and Webflow.

Hey, there. Now that you know
why you need a portfolio, let’s find out how to make one. Coming up, we’ll explain how to build a personalized
online portfolio, and we’ll help you choose the website builder that
works best for you. Building a website might
seem intimidating, but there are a lot
of tools to help you. Most website builders
are simple to use and don’t require any coding
or technical knowledge. Plus, they have a support
team on staff to help. Website builders often have tutorials to help you figure
out what layout to use, and how to add text,
sound, and images. These user-friendly
website builders feature WYSIWYG editors. WYSIWYG stands for What
You See Is What You Get. In other words, you can type, and make your text
bold or add italics as you would in a word
processing program like Google Docs
and Microsoft Word. All this might seem obvious, but Web-based WYSIWYG editors have only been around
for 10 years or so. Before website builders
were widely available, you had to create
everything in HTML and CSS, which are the coding languages used to build the internet. Fortunately, things
are a lot simpler now, so you don’t need to know any code to build an
impressive portfolio. If you do know how to code, or if you’d like the challenge and flexibility that you get
with coding, awesome. You can choose to build
a website from scratch, instead of using a
website builder. Just be sure to put your UX
design work front-and-center, and prioritize the
UX of the site. Remember, recruiters
and employers want to know about
your UX design work, not how good you are at coding. Now let’s check out some
common website builders used by UX designers
to build portfolios. There are lots of options
for website builders. But in this video, we’ll focus on three of the most popular: Wix, Squarespace, and Webflow. For this program, you can
choose any of the three. They all have benefits
and drawbacks. So choose the website builder
that works best for you. Don’t worry that your portfolio might look similar
to your classmates’. There are a variety
of templates to choose from on each
website builder. You’ll personalize your template to convey your unique style, communicate the value you bring to the UX design industry, and showcase your designs. Now, we’ll quickly review
each website builder. Then you can use the links
in the readings to learn more and decide which website
builder you’d like to use. The reading also has step-by-step instructions on
how to set up your website. Wix is easy to use, and a favorite with folks in all kinds of
creative industries. There are plenty of templates and even some templates
specifically for portfolios. Templates mean that you don’t have to start
from a blank slate, which makes it easy to achieve impressive
results in no time. Squarespace is also popular, especially with visual designers. Squarespace is best known
for its blog function, but it also has beautiful
website themes. There are a bunch of
templates to choose from, and it’s flexible to allow
for personalization. If you’re new to
website building, it’s definitely a great choice. Finally, Webflow is
a well-known option among UX designers for
its on-trend styles, and layouts, and high
level of customization. You do need some knowledge
of coding though. So if you’d like to practice
your coding skills, Webflow might be a
good choice for you. Each of these website
builders offer their own add-ons that
you can purchase. One option is a domain, or the address of your website. It’s better to have
your own domain name for personal branding. You’ll personalize your template to convey your own unique style, communicate the value you bring to the UX design industry, and showcase your designs. Okay, now you know why
website builders are helpful tools for building
your UX design portfolio. Take some time to
check out each tool so you fully understand
the options available. Then pick the one you want
to use based on your needs and your career interests. Next, we’ll cover
the best practices and essential features of a UX designer’s
portfolio. See you then.

Reading: Explore website builders for your portfolio

Reading

Reading: Plan your portfolio website

Reading

Video: Introduction to best practices for UX design portfolios

1. Define Your Personal Brand

  • Your portfolio is the first impression. Showcase your personality, unique skills, and design values.

2. Tell a Story

  • Engage your audience by structuring each project with a clear beginning (problem), middle (process), and end (solution).

3. Be Concise

  • Use minimal text. Highlight key design decisions and insights, letting your work speak for itself.

4. Simple Navigation

  • Make it easy for users to find your work, navigate between projects, and contact you.

5. Customize Your Site

  • Go beyond basic templates. Demonstrate your design skills and align the website with your brand.
  • Consider buying a custom domain for a professional look.

6. Showcase Diverse Projects

  • Aim for 3-6 projects to demonstrate the range of your skills and interests.

7. Feature Case Studies

  • Provide in-depth narratives of your design process:
    • Problem statement
    • Research
    • Iterations (sketches, wireframes)
    • Testing results
    • Final design
    • Lessons learned
  • Be mindful of NDAs (non-disclosure agreements)

8. Ensure Responsiveness

  • Your website MUST adapt well to different devices (desktop, mobile, etc.) for the best user experience.

9. Test Thoroughly

  • Check your site on various devices to catch any layout or functionality issues.

Key Points

  • Putting in the effort shows potential employers your dedication.
  • Build your portfolio incrementally as you learn and complete projects.
Identify best practices that can help you personalize your portfolio. Select all that apply.

Tell a story

By telling a story about your design process, you engage your audience and they learn about your personal approach to design. Establishing your personal brand, and going beyond the template are other best practices that can help personalize your portfolio.

Establish your personal brand

Your personal brand should clearly demonstrate who you are and what value you bring to an organization. Telling a story, and going beyond the template are other best practices that can help personalize your portfolio.

Go beyond the template

Customizing your website to align with your brand and story differentiates your portfolio from others. Establishing your personal brand, and telling a story are other best practices that can help personalize your portfolio.

In this video,
we’ll share best practices and highlight some essential
features of UX Design portfolios. Keep in mind there is no right
way to build your portfolio, every designer, recruiter and client has a different idea about what
should be featured in a portfolio. It’s most important to find a way to
make yourself stand out from the other designers. You’ll also want to express yourself
in a way that fits your job interests. For example, if you’re interested in
specializing in interaction, visual, or motion design, your portfolio
should showcase that type of work. Ready, let’s get started. Pro Tip Number 1,
establish your personal brand. Your personal brand is the way in which
your personality, unique skills and values as a designer intersect
with your public persona. We’ll learn more about branding later,
but the main thing to know is that your personal brand is the first
impression you make. Your personal brand should clearly
demonstrate who you are and what makes you interesting. Pro Tip Number 2, tell a story,
your website could easily turn into a list of links and photos, but
to engage your audience, you need to tell a story about your design
process with a beginning, middle and end. This might mean that you start with
an introduction of the design problem, then in the middle, show the process you
followed to complete the designs like user research, sketches and wireframes. Then end with an image of
the polished design and an endorsement from your client or
another person whose opinion you value. Pro Tip Number 3, be concise,
use minimal text to describe your work and highlight the key insights that
help inform your decisions. Let your work speak for itself, if you
need to explain your work in more detail, add links to other pages or PDFs. Pro Tip Number 4,
keep your navigation simple and intuitive, the navigation is the way users get
from page to page on a website. Users should be able to reach the home
page from any part of your site, and your navigation should lead them
from one project to the next. It should also be easy for users to navigate to the contact page
if they want to get in touch with you. Your contact page should include your
email address, a copy of your resume, and links to your professional
social media accounts. Pro Tip Number 5, go beyond the template,
although a website builder’s predesigned layouts make it easy to get
started, you need to go a step further, customize your website to align with your
brand and the story you want to tell. You should demonstrate your design skills
and provide a good user experience. For example, remove the text that
comes preloaded in the template and replace it with your own content. Also, register your own domain name so that your website’s address doesn’t
contain the name of the website builder. You can buy a domain directly
through website builders or through a third party service. Pro Tip Number 6, include a diversity
of projects, you should have three to six projects in your portfolio that
demonstrate the range of your skills. At the end of this program, you’ll have
created at least three projects, so you’ll be well on your way. Make sure each project shows a different
facet of your design talents. Pro Tip Number 7, feature case studies,
a case study leads the user through your design process
from the beginning to the end. Your portfolio should feature case
studies, not just mockups of design ideas. A case study answers these questions, what
was the problem you were trying to solve, what process did you follow,
where did you succeed or fail? What insights inform your design
decisions along the way, and what was the ultimate solution, and why
do you feel that solution was the best? When describing case studies,
you might want to include things like the project’s name and duration,
your role on the design team, including your personal
contributions to the project. The project’s goal,
the research that was conducted, the intended audience, any sketches or
wireframes, user testing results, the final design, and a conclusion
about what you learned in the process. You’ll learn more about each of these
elements as you continue through the program. One more thing to keep in mind about case
studies, be careful not to share any proprietary information or break
a nondisclosure agreement if you have one. A nondisclosure agreement is a contract
an employee might sign when working with a business in which they agree
not to share sensitive information like designs in the process
of being developed. Pro Tip Number 8,
make sure your website is responsive. Remember that responsive means
the onscreen appearance of the website adjusts based on the user’s device. So whether someone looks at your website
on the desktop computer or mobile phone, they’ll have a good experience. And finally, Pro Tip Number 9,
test your website, it’s important to test your website on different devices
to make sure it functions properly. For example,
you might need to move buttons around or adjust images to fit on
the mobile version of your site. You don’t want to lose a recruiter’s
interest because they decided to pull up your website on their phone
instead of their computer and found the text misaligned. Like we mentioned earlier, having
a portfolio with a great user experience will impress potential employers,
all right, that’s it. It’s a lot of work to build a design
portfolio that tells your story and connects with users,
that’s why we’re starting now. If you add new pieces to your
portfolio as you build them, you’ll be in much better shape
when it’s time to apply for jobs. To stay on track, schedule time to work
on your portfolio every week, we’ll remind you to add to your website as you
complete projects and learn new skills.

Reading: Start your online portfolio

Reading

Empathize with users


Video: Empathize with users

What is Empathy?

  • It’s more than just feeling sorry for someone (pity) or acknowledging their feelings (sympathy).
  • True empathy is about understanding and sharing a person’s experiences and emotions.

Why Empathy Matters in UX

  • Avoid Assumptions: We all make assumptions. Empathy helps us shed those and focus on what users actually need, not what we think they need.
  • Solving Real Problems: Understanding users deeply allows you to identify and address their genuine pain points instead of relying on your own guesses.
  • Better Experiences: Empathy-driven design leads to solutions that truly resonate with users, resulting in more satisfying experiences.

Fill in the blank: When you empathize with someone, you share their _____.

mental and emotional experiences

Approaching UX research with empathy makes it easier for you to solve the right problem.

Hi again. We’re ready
to dig into one of the most important parts
of the UX design process: empathizing with our users. In this video, we’ll
learn what empathy is and how it’s
applied in UX design. We’ll also discuss the
importance of understanding user needs, behaviors,
and motivations. The best thing designers
can do to create good user experiences
is empathize. Empathy is the ability to
understand someone else’s feelings or
thoughts in a situation. Empathizing with
potential users is important to every step of
the design thinking process. First, let’s explore what
we really mean by empathy. Sure, you have a definition. But when you think about
empathy in relation to similar words, like
pity and sympathy, the meaning can get a little
blurry. So let’s break it down. When you have pity for someone, you feel sorry for them. But pity usually has
condescending overtones. Think about it like this. Pitiful and pathetic
are synonyms. When you have
sympathy for someone, you acknowledge their feelings, but you keep yourself from
experiencing those feelings. Empathy goes beyond sympathy. When you empathize with someone, you share their mental and
emotional experiences. Empathy is at the core
of everything we do. Approaching UX
research with empathy makes it easier for you to
solve the right problem. Like anyone else, UX designers
make a lot of assumptions, but UX design is
not about solving problems we assume
users want solved. It’s about solving problems that users actually want solved. When we first meet someone, we may have a lot of
assumptions about who they are. As we get to know them though,
we may discover that our assumptions were
not so accurate. This is true in UX design, too. We might think we know who a
user is and what they need, but UX research reveals who they
really are and what they actually need, allowing us to better
empathize with the user.

Reading: Understand empathy in UX design

Video: Recruit interview participants

Understanding User Interviews

  • Importance: User interviews offer direct insights into how users think and feel, fostering empathy in the design process.
  • Recruitment: To find the right participants, start by determining your interview goals. This guides you in creating a representative sample that includes diverse user groups.
  • Methods: For this course, focus on:
    • Your personal network (friends, family, colleagues)
    • Professional networks (e.g., LinkedIn)
    • Online communities based on interests
  • Outreach: In your email invitations, include:
    • Introduction (who you are, the project)
    • Reason for contacting them
    • Interview logistics (location, date, time)
    • Explanation of consent (recording, etc.)
    • How to confirm their interest
    • Optional incentive (e.g., gift card)
  • Reminders: Send reminders before the interview to ensure participation.

Additional Notes:

  • In the real world, hiring a recruiting agency or using paid services can save time and broaden your participant pool, but these methods have budget considerations.
  • Screener surveys help filter potential interview candidates if you have a large pool.

Hey, there. At this point, you should have a
firm understanding of what it means to
empathize with users. To really understand how
users think and feel, you need to talk
to them directly. One way you can learn
from real people about their needs is by
conducting interviews. But how can you find and
recruit people to interview? In the next few videos, we’ll go over what you need to do to recruit participants, prepare for interviews, and conduct interviews.
Are you ready? Let’s get started with how to
recruit participants first. As you can probably imagine, recruiting participants
who are available to be interviewed takes
time and planning. When you’re on the job
in the real world, you might start with a
screener survey to help identify the best candidates to interview for
your research study. A screener survey or simply
screener, for short, is a detailed list of questions
that helps researchers determine if potential
participants meet the requirements
of the research study. For the purposes of this course, you aren’t required
to create a screener, but it is a good tool to be
familiar with for the future. Whether you use a
screener survey or just move straight
to recruiting, you should start with
one important step: determine the interview goals. To determine the goals
of the interview, ask yourself questions
like the following: What do you want to learn
from the interviews? Are there certain
user problems or pain points that you
need to empathize with? Are there any characteristics of users you want to interview? Why? How much information
should we have to ensure we get a comprehensive and balanced set of data? Write a clear list of goals to explain why you are conducting interviews, which will help
determine the characteristics of participants who will be
ideal for you to meet with. For example, imagine
you’re designing a weather app for the
project in this course. The goal of your
interviews during the empathize phase could be to understand emotions that people experience related to
unpredictable weather. Or imagine you’re
designing a shopping app. During interviews, you
may want to identify common user behaviors and experiences involved
in shopping online, like adding and removing
items from a cart. As you start recruiting, aim to form a
representative sample. A representative sample is a subset of the
target population that seeks to accurately reflect the characteristics
of the larger group. The participants in a representative
sample should include user groups that
have been commonly under-represented in
previous research. This lack of
representation is often the result of biases due to age, race, gender, or ability. Having a diverse pool of
participants to choose from will help you create great
experiences for all users. Once you’ve determined the
goals of your interviews, it’s time to continue
the recruitment process. To do this, we’ll explore how to search for potential
interview participants. In the real-world, there are lots of factors that determine how and where UXers find potential
interview participants. For example, finding people to interview can depend on
the company you work for, the type of product
you’re designing, time constraints
for the projects, the projects’ budgets, and the accessibility of the
people you want to interview. For the purpose of this course, you may be limited on who you can find to be part
of your study, so all of the methods we’re
going to discuss may not be an option for you at the
moment. That’s okay. To begin your search, start by creating a list of
who you know personally. You can also ask people from your professional circles, such as your current or
former colleagues, managers, or even
peers in this course. Once you’ve compiled a
list of people you know, move on to people
you don’t know. Perhaps the easiest
way to recruit interview participants
outside of your immediate network, is through social networks
or online platforms. We already mentioned
finding people to interview through your
social media profiles. You can also connect with potential interviewees via professional networking
sites like LinkedIn. Online groups based on personal interests are
another great resource. For example, if you’re
designing an app for musicians, you might find an online group about creating music through a Google search or on social media sites like
Facebook or Reddit. So you have quite a
few ideas for how to find people to interview for
your project in this course. I also want to share a couple
of ways that you might find interview participants in
the real world on the job. Keep in mind though that
these two methods are not expected for the
purposes of this course. One method you might use is a third-party research
recruiting agency. This means that the agency you hire finds people for
you to interview. Recruiting agencies are useful because they save you
time and can often reach a greater
diversity of users than you might be capable
of reaching on your own. However, please note,
for this course, you are not expected to hire a third-party
recruiting agency. Hiring a recruiting agency costs money, so you will likely only use this method if
you’re working on a project that has a
budget for this service. You and your team
may also choose to connect with research
participants through paid services like usertesting.com
or userinterviews.com. Hopefully, you now have
a decently-sized list of people you can ask to
participate in your interviews. You may decide to reach out to these participants based
on who’s available. Or if you are sending
a screener survey, you might select
the candidates who align best with your
interview goals. Either way, it’s likely
that a few candidates will stand out quickly
as ideal candidates. When you are ready, reach out to each prospective participant. The most common way to
do this is via email. Let’s explore what
you should include. Start with a greeting
that introduces yourself and the project, then briefly explain why you
are reaching out to them. Include logistics for the
interview, like location, date, and time. Next, explain the setup
for the interview. This is a good time to explain any parts of
the interview that you’ll need their consent for, like recording audio or video. Begin wrapping up your email
by letting the participant know how they should confirm their interview time if
they are interested. This can either be through
a link to schedule their interview or
through an email reply. If you have the budget, add an incentive
like a gift card. This always helps
sweeten the deal and makes participants
excited to interview. Finally, close the email with
a salutation and your name. After you confirm
people to interview, it’s a good idea to send
email reminders the week before the interview and the
night before the interview. This will help ensure that the people you’ve found actually show up for their interview.
And that’s a wrap. Finding great interview
participants takes true effort, but the great research you’ll conduct will make
it all worth it. In the next video, you’ll learn all about preparing for interviews. Good luck.

Reading: Determine research goals and questions

Reading

Reading: Find and recruit interview participants

Reading

Video: Prepare for user interviews

Before the Interview

  1. Script Your Questions: Develop a standard list of interview questions to ask every participant. This ensures consistency and helps gather comparable insights.
  2. Gather Your Supplies: Make sure you have everything you need:
    • Question list
    • Note-taking materials (paper/computer)
    • Recording equipment (if needed)
  3. Know Your Tech: Be comfortable with any online platforms or recording devices you’ll be using. Have a backup plan (like a phone number) in case of technical difficulties.
  4. Research Your Users: If participant information is available beforehand, review it to familiarize yourself with their backgrounds and previous product experience.
  5. Practice Makes Perfect: Rehearse asking your questions to ensure a smooth interview flow.

Key Takeaway: Thorough preparation sets you up to get the most valuable insights from your user interviews.

Hello, again. We’ve
just covered how to secure participants
for your interviews. Now, you need to prepare to actually conduct
those interviews. In this video, we’ll go
over what needs to happen, so you’re fully prepared
to ace each interview. Have you ever heard the quote, “Before anything else, preparation is the
key to success?” I’m positive that when inventor Alexander Graham Bell said those words in
the 19th century, he didn’t have UX
design in mind. However, this is great advice when approaching
a user interview. Whether you’re
conducting interviews in person or online, preparing ahead
of time helps you make the most of your
limited time together and learn as much as possible about the interviewee’s
unique perspectives. There are many ways to
prepare for your interview. First, script the
interview questions. It’s considered a
best practice to keep interview questions
consistent for every user, so this list of questions will be your guide
during the interview. Second, collect supplies
you’ll need for the interview, such as a printed list
of your questions, a computer or paper
and a pencil, and any recording
equipment you might need. If you’re using new equipment or technology during the interview, make sure you know how
it works in advance. For example, if you’re
conducting an interview online, you want to make sure
you are familiar with the platform you’ll
be using and check that the interviewee
has access to the technology before
your interview begins. A good UX designer also comes prepared with
a backup plan, in case problems with
technology occur. This could be as simple
as making sure you have a phone number to
contact the participant. Third, research the users. If the users you’re
preparing to interview provide their personal
information before the interview, be sure to take note of it. This information might include their name, demographic
information, relevant user experience with the product you are designing, or details about how they
found out about the interview. You can also review their
answers to a screener survey, if you administered one
before the interview. Lastly, practice. It’s always a good idea to practice delivering
the questions you’ll ask users before you
conduct a real interview. Doing so will help
you ensure that the interview runs
smoothly later on. Once you’ve done
all of these steps, you’re finally ready to meet with your
interview participants. I’ll meet you in the next video, where we’ll go
over the steps and best practices for conducting your interviews. See you there.

Video: Interviewing users

Step 1: Meet the Participant

  • Focus on Rapport: Put the participant at ease. Use friendly conversation, thank them for their time, and review any necessary legal details.
  • Gather Basic Info: Collect relevant details like name and demographics.
  • Reassure Them: Emphasize that there are no right or wrong answers.

Step 2: Conduct the Interview

  • Interview Etiquette: Speak clearly and remain professional.
  • Open-Ended Questions: Use “why” and “what” questions to get deeper insights rather than simple ‘yes’ or ‘no’ answers.
  • Follow-Up Questions: Dig deeper based on the participant’s initial responses.

Step 3: Take Notes

  • Capture Key Quotes: Highlight powerful statements that reflect user feelings.
  • Observe Non-Verbals: Document participants’ mood, expressions, and body language.
  • Recording (Optional): If you have permission, recording the interview can be helpful for later review.

Step 4: Wrap Up the Interview

  • Final Thoughts: Allow the participant to share any additional insights.
  • Show Gratitude: Thank them again for their time and contribution.
  • Provide Incentives: If promised, distribute any incentives for their participation.

Key Point: A successful interview combines good preparation, thoughtful questioning, and making the participant feel comfortable and valued.

Welcome back. Now that
your participants are scheduled and you’ve prepared
your interview materials, you’re finally ready to
conduct those interviews. In this video, we’ll review the four steps to
conducting user interviews. As I mentioned before, conducting interviews
with real people is a great way to learn
more about users’ needs. Like many other UX designers, I find this part of the design process
extremely exciting. For me, interacting
with users to identify pain points is like
connecting puzzle pieces. By the end of my interviews, what started off as stand-alone pain points
comes together to create a better understanding of what needs to happen to
improve the product. Let’s get started. The first step is to
meet the participant. Let’s face it. Meeting strangers can sometimes be awkward. You may not know what to expect or you don’t
know what to say. Your job as a UX
professional is to make your participants
feel relaxed and at ease. Here are some tips
on how to do this : Build a good rapport. This is all about establishing a professional, but
friendly interaction. You can use light
conversation to start, something like, how’s
your day going? You should also thank the
participant for coming. Thanking users is a part of
establishing a good rapport and can make them feel like their opinions and
time are valued. Take time to review
legal details that your interviewees need to know before the
interview starts. This can be a good
time to present any legal documents that require their consent to release
audio recordings. You could also have
your participants sign a verification
that they are above the age of 18 and don’t need permission from
a parent or guardian. Gather basic details
as you meet users. Remember to ask about any
details that are relevant to the interview like their name and
demographic information. Starting with questions that
are easy for the participant to answer can give them a
nice boost and confidence. Finally, let the
participant know that there are no right
or wrong answers. This way, they feel
comfortable and are not worried about giving
incorrect answers. Now you’re ready for
the second step of the interview process,
conducting the interview. Here are a couple of things to keep in mind as you conduct interviews: Follow
interview etiquette. Speak in a clear
and concise manner while asking questions. It’s important to
remain professional no matter how users
answer a question. While interviewing, also remember to ask
open-ended questions. Asking yes or no
questions doesn’t allow your participant to tell their honest thoughts
on your product. Instead, try asking questions that start with why or what. For example, if you
ask a question like, do you like online shopping? You’ll likely get one of
two responses, yes or no. Instead, ask an
open-ended question like, what do you like and dislike
about online shopping? Asking questions in this manner will give you a more in-depth understanding of
the users’ feelings like their likes and dislikes. You should also ask
follow-up questions based on how the participant answers the initial question. As you are conducting
interviews, remember to take notes, which is the third step of
conducting a user interview. Have you ever had a
great conversation with a friend only to struggle to remember
the specifics of the conversation later on? Maybe you remember how the conversation
started and ended, but everything in the
middle is a blur? This happens to all of us and user interviews
are no different. That’s why it’s helpful to take notes during the interview. In the UX world, researchers who work for
companies or on teams often have other members moderate or take notes
during the session. For now, you’ll have to fill both of these roles on your own. While taking notes, you’ll want to highlight
compelling quotes. These interesting quotes are great indicators about how
users really think and feel. They can be included in empathy maps and user
testimonies later on. Document observations
about participants. Sometimes what a
participant does is equally important
as what they say. Making notes on their mood,
expressions, body language, and behaviors will be important to consider when
creating empathy maps. Finally, consider
recording interviews. When you’re first
learning how to conduct research, recording is ideal. It can be helpful later when
you’re revisiting parts of an interview or taking additional notes after
the interview is over. Again, it’s best
practice to always ask your participants for
their permission to record them before
the interview begins. The fourth and final
step to conducting a user interview is to
wrap up the interview. Just like in a track race, when you’re nearing the
finish line of an interview, it’s important to end just as strongly as when you started. Wrapping up an interview without showing gratitude
to participants for joining the interview
can leave them feeling uncomfortable or wishing they had not agreed to participate. Instead, you want them to leave feeling like
their opinions were a valuable contribution to
your overall design process. To do this, wrap up the interview by giving
users a chance to share final thoughts about any items discussed
during the interview. Some participants
might open up about their opinions and reveal insights that they
didn’t share earlier. You might try asking
them if there are any new points
they want to add. Also, you should always thank the participant
again for their time. Tell them that you
appreciate them participating in your interview, and give them a warm goodbye. If you offered any incentives to your participants
to interview, now is the time to share
them. That’s a wrap. I hope learning
these steps helps approaching an interview
feel less intimidating. Following each of
these steps in order increases the likelihood that your interview
will run smoothly. In the next video, you’ll move on to creating an empathy map. Meet you there.

Reading: Conduct user interviews

Reading

Reading: Build empathy with users to inform research

Reading

Learn about empathy maps


Video: Empathy Maps

What is an Empathy Map?

  • A simple chart with four squares: Says, Does, Thinks, Feels.
  • It visually captures insights gained about a user, helping designers deeply understand their needs.

Types of Empathy Maps

  1. One-User Empathy Map
    • Based on an interview with a single user.
    • Uses direct quotes for accuracy.
  2. Aggregated Empathy Map
    • Combines feedback from multiple users with similar traits (a user segment).
    • Highlights common pain points and preferences.

How to Make an Empathy Map

  • Says: Direct quotes from user interviews reveal what they verbalize.
  • Does: Actions or behaviors shared in the interview, or observed during it.
  • Thinks: Inferred from the user’s expressions and responses, even if they don’t say it directly.
  • Feels: User’s emotional state, either directly asked or observed.

Example: Food Delivery App

  • Simone (one-user map): Wishes for accurate wait times.
  • Aggregated Map: Includes other users also desiring accurate times, live tracking, easy navigation, etc.

Key Points

  • Empathy maps should be created for different user segments (those who find the app easy vs. those who are frustrated).
  • This visualization tool aids designers in understanding user needs and designing solutions that truly address them.

Hi, and welcome back, I’m sure you’re
already starting to understand your users better as we continue through
this stage of the design process. One way that we can visualize empathy
is by creating an empathy map, an empathy map is an easily-understood
chart that explains everything designers have
learned about a type of user. An empathy map consists of four
squares which show what the user says, does, thinks, and feels. The word user goes in the middle
right where these squares intersect. Now you’re ready to fill in the squares, keep in mind there are two
types of empathy maps. One user empathy maps, where you record
feedback from a single user, and aggregated empathy maps, where you consolidate feedback
from a group of users. Let’s start by creating
a one user empathy map, and then we’ll move on to
an aggregated empathy map. Imagine you’re on a team building an app
that promises food delivery in 30 minutes or less, you interview users about
their experiences with food delivery. The top left of your empathy map includes
what the user says during the interview. When you do this, use direct quotes
if you can, for example, one user, Simone, has ordered food through
other delivery apps before. Simone might say something like, I wish food delivery apps provided more
accurate time estimates, we should write this direct quote from Simone in
the says square of our empathy map. Next, the bottom left square
focuses on what the user does. These could be actions or behaviors
the user shares in their responses, or even the user’s physical
actions during the interview. For example, Simone might share how they only order
delivery when eating at home alone. The top right square focuses on what
the user thinks, this includes things the user doesn’t actually say, but
that you can tell through observation. Facial expressions are a great way to
understand what a user is thinking, a furrowed brow might indicate that
Simone is skeptical about a 30 minutes or less guarantee. Finally, the bottom right square of the empathy map focuses
on what the user feels. You could directly ask Simone what
they’re feeling during the interview, so long as it’s done in an open ended way. For example, you might ask, how do you feel when you try to place
delivery orders through an app? After the interview, fill in the feels
square with these observations, and we’re done with Simone’s empathy map,
nice work. Next, you’ll learn how to
build aggregated empathy maps, now that you know how to build one
user empathy maps, it’s time to take what you’ve learned about a single
user and apply that to multiple users. Aggregated empathy maps represent
a visualization of everything designers know about an entire user segment or
group of similar users, not just one user. Aggregated empathy maps appear
exactly like one user empathy maps. Breaking down the information
we’ve learned about our user segment into four categories says,
does, thinks, and feels. The difference is that aggregated
empathy maps include information that is gathered from multiple users. Continuing with our example, let’s say
that the day you interviewed Simone, you also interviewed Miranda and Lewis. In the says square, Miranda mentioned something similar to
what Simone said about accurate estimates, but Lewis says, I wish I could
live track my food delivery. We’ll add that response below
Simone’s response in the says square. For does, something that both Miranda and
Lewis shared was that they order delivery on weeknights more often than weekends,
so we’ll add that to the does square. Now we’re on the thinks square,
during the interview, Lewis shares that it would be nice
if their favorite restaurants had a delivery option,
let’s add this to the thinks square. Next, Simone responded to the question, how do you feel when you try to place
a delivery order through an app? By expressing frustration with the lack
of direction in most food delivery apps, we’ll add this reply to
the feel square first. Lewis stated, feeling annoyed with
trying to navigate delivery apps, we’ll add that feedback last. And now we have a complete aggregated
empathy map that represents a full user segment. Creating an aggregated empathy map can
seem overwhelming, but keep in mind that you want it to represent an entire
user segment that you’ve interviewed. As you think about the ways to group your
user feedback, remember that each map should reflect a different user segment
with specific thoughts and needs. For example, if you find yourself
interviewing a few users who find the app easy to use and
have no real issues or complaints. That user segment would be represented by
a different aggregated empathy map than the users who were frustrated
when they tried to use the app.

Reading: Build an empathy map

Identify user pain points


Video: Identify user pain points

UX Design: Focused on Solving User Problems

  • UX designers are essentially problem-solvers. Their main goal is to find and address user pain points.
  • Pain points are any aspects of a product or experience that frustrate the user and prevent them from achieving their goals.
  • Understanding these pain points requires empathy – the ability to put yourself in the user’s shoes.

Types of Pain Points

  1. Financial: Issues surrounding cost or unexpected expenses.
  2. Product: Quality problems or usability issues with the product itself.
  3. Process: Difficulties the user has in navigating or completing tasks.
  4. Support: A lack of assistance or difficulties finding help when needed.

Why Empathy Matters

  • To identify pain points, designers need to:
    • Understand how users think and feel.
    • Consider diverse user needs and abilities.
    • Anticipate both known and unknown user needs.
  • Empathy maps help visualize what the user thinks, says, does, and feels – revealing pain points.
  • User personas offer even deeper insights into users, making problem identification easier.
What are pain points?

Any UX issues that frustrate the user and block the user from getting what they need.

Pain points are any UX issues that frustrate the user and block the user from getting what they need.

Welcome back. Earlier, you learned why empathizing
is so important. As a UX designer, empathizing is your
number one superpower because it helps you
spot user problems. Solving user problems is the
ultimate goal of UX design. But how do you even
know if a problem is really a problem?
Let’s jump right in. Think about New
Year’s resolutions. Most of us set goals at
the beginning of the year, but how many of us
keep those goals? Well, it turns out not many. Eighty percent of New
Year’s resolutions fail because they are not clear or we set
unrealistic expectations. UX designers face similar
challenges when setting goals. To make sure you are tackling
something you can impact, set clear and actionable goals by focusing on user problems. So, let’s identify those
user problems. By now one thing should
be pretty clear: UX design is all about the user. You’re always, always designing
for the user. But who is the user and
what are their struggles? To find out, you need to
be a bit of a mind reader. Okay, you don’t exactly
have to read minds, but you do need to
use your superpower: your ability to empathize. You need to do
research to get into the user’s head and understand
where they’re coming from. You also have to anticipate
both the needs that users know they have and the needs
they don’t know they have. That’s weird, right? How do users
not know what they need? Well, here’s an example. In the heyday of flip phones, customers might have thought they needed a longer battery life, a bigger interface, an
easier way to text. But they had no idea
they needed smartphones. Most of us didn’t even know
smartphones were possible. So when Apple introduced the first modernized
smartphone in 2007, we were dazzled by
all it could do. Having a smartphone
quickly turned into a need for so many of us. So if you narrow down
everything that a UX designer does
into a single role, that role would be
problem-solver, and solving user struggles or pain points is number
one on the list. Pain points are
any UX issues that frustrate the user and block the user from
getting what they need. Remember the Norman Door? If you expect a door to open, it should open.
If it doesn’t, that’s a user pain point. Or how about this one? Ever gone on a company’s website to find their customer
service info? You click tab after tab, scroll page after page, and you still can’t find it? That’s a user pain point. Most pain points fall into
one of four categories. Financial pain points are
user problems related to, you guessed it, money. If you’ve ever gotten lost
in an online article, only to be rudely
interrupted by a paywall, you know all about these. There are also
product pain points. These are usually quality
issues related to the product. Norman Doors fall
into this category. Next up, there are
process pain points. These are frustrations that stop the user going from
point A to point B. For example, have you
ever shopped online and struggled to get the item
you want to check out? That’s a process pain point, and that could mean the
business loses a customer. And finally, there are
support pain points. When users interact
with your product, they might have questions. If they can’t find answers
to their questions, they won’t feel supported. Customer service
information that’s hidden on a website falls
into this category. Remember when I said
designers need to read minds? Well, we also need
to read hearts. I think it’s safe to
say that we’ve all experienced these
kinds of pain points. We know how it feels. As a designer, you need to know how it feels for your user. In other words, you need to
have empathy for your user. Think back to the
door experiment. Opening the door may
not always be easy. What if our user is
in a wheelchair? What if they can’t
reach the knob? What if they don’t
have enough strength? You want to account
for all users. Let’s think back
to an empathy map. Empathy maps show us
what the user thinks, says, does, and feels. Empathy maps help us get
into the user’s mindset, allowing us to identify
their pain points. This is just the beginning. We really want to get
to know our users, and that’s why designers
create user personas. Let’s find out what
personas are all about.

Reading: Case studies: Products that address pain points

Reading

Practice Quiz: Test your knowledge on user pain points

Which of the following is an example of a pain point? Select all that apply.

How can an empathy map help UX designers understand a user’s perspective?

Which of the following is an example of a process pain point?

Most pain points fall into one of four categories: product, financial, process, or support.

Create personas


Video: Understand personas

What are Personas?

  • Fictional representations of typical users within your target audience.
  • Not invented, but carefully constructed based on thorough research.
  • Personas help define distinct user groups with their own needs, goals, and characteristics.

Why Personas Matter

  1. Empathy: Humanizing your users aids understanding and puts a relatable face on the data.
  2. Storytelling: Personas transform presentations, making them more persuasive and focused on user needs.
  3. Stress-Testing Designs: Having a diverse set of personas ensures that your design choices consider the needs of various user groups.

Example: Tsering Choedon

This persona represents the user group of environmental nonprofit founders in rural areas. Her bio, goals, and tech-savviness inform design decisions specifically tailored to her needs.

Key Takeaway: Personas are valuable UX tools because they foster empathy, improve communication with stakeholders, and help ensure designs work well for a wide range of real users.

Hey there! And welcome back. Now you know all about
user pain points. Next, let’s explore personas and why UX designers use them. In UX design, personas are
fictional users whose goals and characteristics
represent the needs of a larger group of users. Personas can help us identify patterns of behavior in users. These patterns might point to a common pain point that a
group of users experiences. While personas are fictional, we don’t make these
characters up from scratch, we build them based on research. You’ve got to do your
research if you want a set of personas that truly represent
your potential users. As you research,
you’ll form images in your head about
who your users are. These will become your personas. Let’s build a persona together. First, we’ll need
to figure out what user group our
persona represents. Imagine you’re designing
a fundraising app that connects nonprofits
with volunteers. You do some secondary
research and conduct phone interviews with a
diverse set of users. Let’s say during research, you discover that
single professionals in rural areas donate to environmental causes twice as often as single
professionals in big cities. You also discover that
big city singles are more likely to volunteer than single professionals
in rural areas. Based on this, one of
your user groups might be owners of environmental
nonprofits in rural areas. A user group is a set
of people who have similar interests,
goals, or concerns. Now that we’ve identified
a solid user group, let’s build a persona
to represent it. Ready? Meet Tsering Choedon,
founder of ourplanet.org. As we build the persona, we want to include her photo and a short biographical sketch. Include things like age,
occupation, hometown, marital status, and any other
demographic data points that might give us a better sense of who our user group is. So imagine that Tsering is 35, has a BA in English,
and lives in Bellevue, Nebraska with her wife
and two rescue dogs. After the biosketch
comes a bit about her professional goals
and day-to-day duties. As a founder of a nonprofit, Tsering probably fills
lots of roles like writing grants and talking
with city officials about exciting green initiatives. She also keeps residents
informed about how and where to
recycle their trash. After that, since you’re
designing an app, you might want to know how
comfortable Tsering is at navigating online
and working with tech. Let’s say she’s
not so tech savvy, but knows she has to
get her nonprofit online if she wants to
find more volunteers. Finally, you might want to
give her a catchphrase, something she says to inspire herself and her small
team every day. For Tsering that
might be something like gettin’ greener every day. And just like that, your
user group turns into a real person that the team
can build their app around. Keep in mind each
persona you create humanizes a user
group for your team. Tsering represents
only one persona. You want to build a persona to represent each key user group, and that will take time. Is it worth it to build
so many personas? The short answer? Absolutely. Now for the longer answer. Personas build empathy and
put a face to the user. They help humanize our users. They give stakeholders
a clearer idea of who their users really are and makes the user experience
more meaningful. Let’s do a little test. When I say to you, there are about 533,000 people over the age of 100
living in the world today, you’ll probably find it
mildly interesting for a second before promptly
forgetting the number. But if I tell you
about Mavis Hunter, a competitive runner who
only picked up the sport two years ago after
turning 100 years old, chances are she makes a
longer lasting impression. Why? She makes you feel
something the stats can’t. She feels like a real person. You want to help her continue
to do what she loves. That’s the power of personas. In addition, personas
tell stories. This is why personas
are key to turning an average stakeholder
presentation into a story telling experience. If your client is building
a new running app, Mavis helps make the case
for creating new features or expanding accessibilities
for senior citizen athletes. Okay, so personas build
empathy and tell stories. But why do you need a
whole set of personas? Well, one persona isn’t enough to tell all the sides
of a design story. As cool as Mavis is, you aren’t improving the
running app just for her. This is why you need
a set of personas. All user groups should
be vividly represented. This shows stakeholders
the diversity of their user groups, and it lets you test
features against them. This leads us to the third reason for why
personas are worth it. Personas stress-test designs. Let’s go back to the running app. What works for Mavis
might not work for Diane, a working mother of three
children under the age of five. What matters most
to Mavis isn’t the same as what matters
most to Diane. Mavis wants accessibility, while our working mom wants time. Personas make sure
we designers create something that benefits
a wide range of users. Now that you know
what a persona is, what personas do
for UX designers, and how to build a persona, let’s get to know how personas
help us tell a user story.

Reading: Learn more about personas

Reading

Module 1 review


Quiz: Module 1 challenge

You have been assigned to complete your first peer review assignment on a colleague’s design. How can you make sure your feedback is encouraging and supportive?

At the early stages of designing a new app, you conduct interviews with stakeholders. You ask them open-ended questions to understand what the true need of users is, instead of just assuming. Your goal is to understand their feelings and thoughts. What is the goal you are trying to accomplish with users?

You are conducting a research study to determine what users want to see in a new weather app you have an idea for. What can you do to talk to users directly in your study?

You are in the early stages of research on a user interface design project. Part of your research is analyzing completed research on this same topic. The previous research data only includes participants in their early twenties. Which type of bias does this represent?

You begin to recruit participants to interview. You have created a list of people you know who have agreed to be interviewed. You now need to recruit participants that you do not know. Where is the best way to find participants that you do not personally know? Select all that apply.

You are excited to conduct your first online user interview. What can you do ahead of time to ensure that the interview runs smoothly? Select all that apply.

You are excited to conduct your first interview for a UX design shopping research project you are working on. You have prepared open-ended questions to ask participants. Which of the following are examples of open-ended questions? Select all that apply.

After an interview with one of your participants, you decide to create a map that shows what the user says, does, thinks, and feels. What type of map did you create?

During an interview, an interviewee expresses frustration with a UX issue for a food delivery service app. What are they describing?

After completing research, you realize that you can group a set of people together because they share the same interests, goals and concerns. What is this group of people called?