Customer research methods: start with the question, and the method picks itself

Pick customer research methods by your question: interviews and observation explain why, surveys and analytics count how many. Plus a sequence for small teams.

Instant Expert EditorialPublished Updated 5 min read

Pick customer research methods by the question you need answered. Why something happens, or how people do a job, needs a qualitative method such as interviews. How many or how much needs a quantitative one such as a survey.

The methods fall into five groups: talking to people (interviews), watching them work (field visits, usability sessions), asking many people the same questions (surveys), measuring what they do (analytics, experiments) and reading records you already have (support tickets, sales notes, reviews).

One product idea can need four methods

Here is a made-up example. You are exploring software that fills last-minute cancellations at dental practices, with four open questions:

  1. How does the front desk handle a cancellation today?
  2. How often do cancellations leave a chair empty?
  3. Would the office manager, the dentist or a group owner decide to pay for a fix?
  4. Can a receptionist use your prototype during a busy morning?

The first and third call for interviews. The second is a counting question, and scheduling records answer it better than anyone's memory. The fourth needs you to watch someone use the prototype, ideally while the phone is ringing.

What each method is good and bad at

MethodGood forWeak at
InterviewsHow a job gets done, who decides, what people tried beforeHow common something is
Field visits and contextual inquirySeeing the real workflow, workarounds and interruptionsScale; they take time to arrange
Usability sessionsWhether people can complete a task with your product or prototypeWhether they want the product at all
SurveysHow many people report an attitude or experience, once you know what to askExplaining why; follow-up questions
Analytics and A/B testsWhat people actually do in a live product, at volumeReasons behind the behavior; they need a product and traffic
Existing records (support tickets, sales and churn notes, public reviews)Recurring complaints and the words customers useNeeds of people who never contacted you

Nielsen Norman Group's guide to research methods maps 20 methods on the same lines: qualitative for why and how to fix it, quantitative for how many and how much.

What people say and what they do often differ

The same guide separates attitudinal research (what people say) from behavioral research (what people do). A receptionist may tell you they always call the waitlist when someone cancels. The call log might show they do it only on quiet days.

Interviews and surveys collect accounts; observation, analytics and records show behavior. When a decision rests on behavior, such as whether people will pay, look for what they actually did: a recent example, a record or a real purchase.

The right method changes with your stage

Early on, you are deciding what to build and for whom. NN/g groups interviews, field studies, diary studies, surveys and concept testing as generative methods for this stage. Of those, start with interviews: they are quick to arrange and let you follow an answer you did not expect.

With a design, usability testing shows where people get stuck. After launch, analytics, A/B tests and surveys measure performance, and interviews explain the numbers.

Surveys are easy to send and hard to do well

NN/g's article on when to run a survey argues they fit questions that are both quantitative and about attitudes, such as what share of users feel confident after a task. A why question belongs in a qualitative method. The interviews versus surveys guide covers that choice.

Read your own records before you recruit anyone

Support tickets, sales call notes, reasons for cancelling and competitors' public reviews cost nothing to read and show customers' own words for the problem. They skew toward people who bothered to write, so treat them as leads for interviews, not a measure of how common a problem is.

A five-step sequence for a small team

  1. Write the decision you face and the one or two claims you are unsure about.
  2. Read the records you already have and list what they cannot tell you.
  3. Interview people who did the job recently: for the dental example, receptionists, office managers and someone who owns several practices. The finding customers guide covers where to find them, and the interview count guide helps you decide how many to plan.
  4. If a question about frequency remains, count it with records or a survey written in the vocabulary you heard in interviews.
  5. When you have something to show, watch people use it.

A small decision may need only a handful of conversations and the records you already hold.

Interviews only work if you can reach the people

Most teams can start interviews this week, if they can reach people who do the work. Your own customers you can email directly. For receptionists and office managers at practices that don't use you, describe the role in a people search or paste the LinkedIn URLs of people you've found; the directory page for operations professionals in dental services shows who you could reach. You choose a call or a written answer and set what each person receives. Our fee is added on top (a $100 offer costs you $125), and you're charged only when someone books or answers. A call suits the stories in step 3; a written answer suits one narrow question, such as what a practice calls a patient who misses an appointment.

Before you invite anyone, write down the one question each conversation needs to answer.