Pain Points

IN THIS LESSON

Once you have chosen a customer, the next step is to understand what that customer is actually trying to do and where the experience breaks down for them.

This is one of the clearest opportunities in a Product Sense interview to demonstrate customer empathy. You are being asked to reason from another person’s point of view, often in a space you know only indirectly. You need to use what you know about the customer, the context, analogous experiences from your own life, and your broader understanding of how people behave to build a credible picture of their experience.

The objective is to identify a pain point that follows naturally from the customer you selected. A strong pain should reveal something about what this particular customer wants, what they actually do, and why some part of that experience is difficult enough to create an opportunity for a product.

What this task proves about you

Product managers rarely work only on products they personally use or for customers whose lives look exactly like their own. They need to understand people with different expertise, motivations, constraints, responsibilities, and behaviors well enough to make good decisions on their behalf.

Pain-point analysis gives the interviewer evidence about whether you can do that.

A candidate with strong customer empathy can take a customer they may know only in broad terms and construct a plausible account of that person’s experience. They can infer what the customer is trying to accomplish, describe the behaviors involved, identify where those behaviors become difficult, and distinguish a problem that genuinely follows from the customer’s circumstances from a generic inconvenience that could have been attached to almost anyone.

You do not demonstrate customer empathy by saying that you are customer-focused. You demonstrate it through the quality of the observations you make about the customer.

Start with what the customer is trying to accomplish

Pain points make sense only in relation to a motivation. Something becomes painful because it prevents a person from achieving an outcome they care about.

Suppose you have selected goal-based learners preparing for an exam. Their situation is more specific than simply wanting to learn something. They have a particular outcome they need to achieve, a finite amount of time before the exam, some existing knowledge, some gaps, and uncertainty about how best to use the time they have left.

Those circumstances create the basis for pain-point analysis. You might begin the section by saying:

Now that I’ve chosen goal-based learners, I want to understand what gets in the way of reaching that goal. I’m going to think through what they’re actually doing as they prepare and look for the parts of that experience that are most difficult.

That transition explains why the section exists and keeps the reasoning connected to the customer you already chose.

Reconstruct the customer’s behavior

When a pain point does not come immediately to mind, work through what the customer actually does.

For the learner preparing for an exam, there is a period before studying when they decide what to work on and how to spend their limited time. While studying, they consume material, practice, revisit things they do not understand, and try to judge whether they are improving. As the exam approaches, they have to decide whether they are ready and where the remaining risks are.

You could describe this as a user journey, but the journey itself is not the point. A long inventory of every step consumes time without demonstrating much. A rough beginning, middle, and end is usually enough to expose the behaviors you need to reason about.

The useful question is what becomes difficult within those behaviors. Perhaps the learner has far more material available than they could possibly consume before the exam and cannot tell what deserves their attention. Perhaps they can spend hours studying without knowing whether the material they are reviewing addresses their actual weaknesses. Perhaps they have no reliable way to judge whether they are sufficiently prepared until they take the real test.

Working from behavior helps the pain points emerge from the customer’s experience rather than from a list of generic product problems.

When you present several candidate pains, Why-Anchor each one rather than leaving the interviewer with a label. State the pain, provide whatever behavior or circumstances are necessary to make the problem legible, and then explain why it matters by reconnecting it to the customer’s motivation. For example, “planning uncertainty” is only a label. A stronger version explains that the learner has two weeks left, cannot tell which topics deserve the remaining time, and risks spending a meaningful part of that window on material that will not improve the outcome they care about. Once the interviewer understands the problem and why it is consequential for this customer, that pain-point unit is complete and you can move to the next one.

Use what you know to understand experiences you have not lived

Many interview prompts will put you in a domain where you are not the customer. Customer empathy does not require pretending that you have direct experience you do not have. It requires making reasonable inferences from the information available.

You may never have managed operations during an airline disruption, for example, but you understand situations where someone has to make consequential decisions with incomplete information, limited resources, changing conditions, and people waiting for an answer. From there, you can reason about what an airline employee might actually need to do: understand which flights and passengers are affected, evaluate alternatives, coordinate scarce seats and crews, communicate changes, and keep revising the plan as the situation evolves.

Personal experience can give you useful analogies, but it should help you understand the customer rather than turn the customer into you. The question is not what would annoy you personally. The question is what the customer’s goals, behaviors, constraints, and circumstances give you reason to believe would matter to them.

Find pains that belong to the customer you chose

Generic pain points are easy to produce because they require very little understanding of the customer.

Consider the goal-based learner again:

They don’t know where to start.

That may be true, but it could describe someone beginning almost any unfamiliar activity. It does little to explain why the customer segment you chose matters.

A more specific pain follows from the circumstances that define the customer:

They have two weeks before the exam and don’t know which topics deserve the limited study time they have left.

Now the problem reflects the customer’s goal and constraint. The limited time creates a decision about what to learn, what to skip, where to focus, and whether the learner is making enough progress. The pain could not have been generated as easily without understanding what makes this customer different.

The same distinction applies to other cases. Saying that a new homeowner finds gardening confusing describes the category broadly. Describing a homeowner who notices that a plant is deteriorating but lacks the experience to distinguish watering problems, disease, pests, soil conditions, or ordinary seasonal change gives you a much clearer account of what they are actually experiencing.

Specificity matters because it is evidence that the customer analysis is doing real work. The selected customer should shape which pains you find.

Look for the experiences that matter most

A customer journey contains many inconveniences, but most products cannot and should not address all of them. Once you have identified several credible pains, choose the one that creates the strongest opportunity to improve an outcome the customer actually cares about.

This judgment should follow from the experience you just described. Consider how seriously the problem interferes with the customer’s motivation, how often or predictably it appears in their experience, and what happens when it goes unresolved. You usually do not need to turn those considerations into a scoring table. Explain why one pain is more consequential than the strongest alternative.

For the learner, that might sound like:

I think I’d focus on deciding how to use the remaining study time. They may also struggle to understand individual concepts, but the planning problem affects everything that follows. If they spend a meaningful part of those two weeks studying the wrong material, even good content may not help them achieve the result they care about.

The important information is the reasoning behind the choice. The interviewer can see what the customer wants, why this obstacle matters in their particular circumstances, and why you think it deserves attention before the alternatives.

The goal and company context established earlier can also inform a close decision. If two customer problems appear similarly important, a problem that the company is unusually well positioned to address or that more directly advances the established goal may be the better choice. That consideration should refine a credible customer problem rather than substitute for finding one.

Keep the pain separate from the solution

A pain point should describe the customer’s problem without committing to how you will solve it.

For the learner, this is already a solution:

They need an AI tutor that creates a personalized two-week study plan.

The underlying problem is broader:

They do not know how to allocate their limited time across what they already understand, what they still need to learn, and what matters most for the exam.

Keeping the problem at that level preserves the next stage of the case. Several different products might address the same pain, and you want the solution to emerge from a comparison of credible alternatives rather than from an idea that was embedded in the pain-point definition.

The point

Pain-point analysis is where an abstract customer group becomes a person whose behavior and circumstances you can reason about. Start from what that customer wants, reconstruct what they actually do, and look for the moments where an important motivation is blocked. The more specifically the pain follows from the customer you selected, the more clearly your reasoning demonstrates that you can understand people whose experiences may be different from your own.