Customer Research

Customer research is the process of learning directly from real users what problems they face, how they currently solve those problems, and what would make their lives easier. Every good product decision starts here. Skipping research means guessing — and guessing is expensive.

Why Research Comes Before Building

Imagine a baker who bakes 200 chocolate cakes without asking the neighborhood what they want. On delivery day, everyone says they wanted vanilla. The baker wasted time, money, and ingredients. The same thing happens in product development when teams skip customer research.

The Three Things Research Tells You

• Problems: What frustrates users in their current situation?
• Behaviors: What do users actually do (not just what they say they do)?
• Needs: What outcome does the user really want?

Types of Customer Research

1. User Interviews

The PM talks directly with customers, one at a time, for 30–60 minutes. The goal is to understand their world, their habits, and their frustrations — not to pitch the product.

Good interview questions:

• "Walk me through the last time you tried to do [task]."
• "What was the hardest part about that?"
• "What do you do today to handle this problem?"

Bad interview questions (avoid these):

• "Would you use a feature that does X?" — People say yes to features they will never use.
• "Do you think our app is good?" — This invites flattery, not truth.

2. Surveys

Surveys collect opinions from a large number of users at once. They are faster than interviews but provide less depth. Use surveys to confirm patterns you already suspect, not to discover new insights from scratch.

3. Usability Testing

The PM watches real users try to complete a task inside the product. This reveals exactly where people get confused, lost, or frustrated. No survey or interview tells you this — only watching someone struggle with the product does.

4. Data Analysis

Product data shows what users actually do. If 80% of users drop off at Step 3 of your signup form, the data tells you there is a problem. Combine this with interviews to understand why.

5. Support Tickets and Reviews

Customer complaints are a goldmine. App store reviews and support tickets show real problems that real users experience. A PM who reads 50 support tickets a week stays closely connected to what is breaking.

Diagram: Research Methods by Scale and Depth

         HIGH DEPTH
              |
  User        |   Usability
  Interviews  |   Testing
              |
--------------+-------------- 
              |
  App Reviews |   Surveys
              |
         LOW DEPTH
     FEW USERS      MANY USERS

Use high-depth methods (interviews, usability testing) to discover problems. Use large-scale methods (surveys, data analysis) to measure how widespread the problem is.

How Many Users to Research

Research by Jakob Nielsen, a usability expert, shows that 5 user interviews reveal about 85% of usability problems. You do not need to interview 500 people to find the main issues. Start with 5 interviews, spot the patterns, then use surveys to measure how common those patterns are.

Turning Research Into Insights

Raw research is just notes. The PM's job is to find patterns across conversations and data. Here is a simple process:

• Collect all notes from interviews and surveys.
• Group similar observations together.
• Write one sentence for each group that starts with: "Users struggle to _____ because _____."
• Rank these by frequency and severity.

The most frequent and most severe problems become the PM's top priorities.

The Danger of Research Without Action

Some teams collect research and then ignore it. Research only creates value when it changes what the team builds. Every research finding should answer: "What will we do differently because of this?"

Key Takeaway

Customer research is not optional — it is the foundation of every product decision. PMs who talk to customers regularly build products that solve real problems. PMs who skip research build products that nobody asked for.