The trap is asking users if your product will solve their problems. They usually say yes — but what you really need to learn is how they do their work today, what frustrates them, and what they would pay for.
Gathering feedback from users is not a one-off task. It is a continuous discipline that shapes your product at every stage — from early validation to ongoing improvement. Your actual job is to get beyond surface-level answers and understand the real problems, behaviors, and desires of your customers.
Many PMs fall into the trap of asking broad, leading questions like "Will this product solve your problem?" The usual answer is "Yes," but that tells you nothing. Instead, you must learn how users currently do their work, what frustrates them, and what they would pay to fix.
This lesson teaches you how to design and run feedback processes that produce actionable insights — not just noisy opinions.
The trap of vague questions
When you ask users, "Do you think this product will resolve your problems?" you get a blanket yes or no. Users want to be polite or hopeful, so they often say yes without really reflecting.
What you want to do instead is ask about their current workflow and pain points. For example:
- "Walk me through how you currently do [task]."
- "What are the biggest challenges you face when doing this?"
- "Have you tried any workarounds or hacks to solve this?"
- "What would make this easier or better for you?"
These questions reveal the context and motivations behind their behavior. That is where the real insights live.
User interview with a small business owner in Pune
You (PM): “Can you describe how you track your daily expenses?”
User: “I keep a notebook and jot down everything. But sometimes I forget, so the records aren’t accurate.”
You (PM): “What happens when you forget? How do you catch up?”
User: “I try to remember at the end of the day, but it’s messy and takes time. I often miss things.”
This tells you the pain point is manual tracking and forgetfulness — not just 'expense tracking' as a generic need.
Avoiding vague yes/no answers and uncovering real pain points
Start small and scale up your feedback
You do not start by surveying thousands of users. That is a mistake. Large surveys early on produce noisy data with little pattern.
Start with a small, focused group — 10 to 20 users — and conduct deep interviews. This helps you understand the problem space and validate your hypotheses.
Once you have clarity, expand to larger samples — 100, then 200 users — to test whether your insights hold at scale.
Methods for collecting feedback
User feedback comes in many forms. Choose the right method based on your product type and stage:
- User interviews: One-on-one conversations that uncover motivations, workflows, and pain points. Best for early-stage discovery.
- Surveys: Structured questionnaires that gather quantitative data on satisfaction, feature usefulness, and priorities. Best for measuring trends over time.
- In-app feedback forms: Contextual prompts after key tasks that capture immediate reactions. Useful for ongoing product iteration.
- Customer support logs: Analyzing tickets and calls to identify common issues and feature requests.
- Net Promoter Score (NPS): A standard survey question that measures customer advocacy and loyalty over time.
- Usability tests: Observing users interact with your product to spot friction and confusion.
Prioritizing feedback for product decisions
Not every piece of feedback deserves equal weight. Your job is to distinguish between noise and signal.
Ask:
- Does this feedback align with known pain points?
- How many users report this issue or request this feature?
- What is the impact on key metrics like retention, acquisition, or revenue?
- Does it fit your product vision and strategy?
- What are the costs and risks of implementing this change?
Avoid being a feature factory that builds every user request. Instead, use feedback to validate assumptions and prioritize work that delivers the highest customer and business value.
Product prioritization meeting at a Series A fintech in Bangalore
You (PM): “Several users want a dark mode. It’s a nice-to-have, but our churn is driven by onboarding issues.”
Engineering Lead: “Dark mode is low effort. Can we do it alongside onboarding fixes?”
You (PM): “Onboarding fixes will improve retention and revenue. Dark mode can wait for Q3.”
Prioritizing impact over nice-to-haves is the key lesson here.
Balancing user requests with strategic priorities
Validating ideas before launch
Before you build a product or feature, validate your ideas with real users.
- Conduct user interviews to test whether the problem you want to solve is real and painful.
- Use prototypes or mockups to get early reactions on your solution.
- Run small pilots or internal tests to catch major flaws before a big launch.
This reduces the risk of building something nobody wants.
Measuring customer satisfaction after launch
Feedback does not stop after launch. You must continuously measure how well your product meets customer needs.
Two key methods:
- Surveys that ask users what features they find most useful or frustrating.
- Net Promoter Score (NPS) to track customer loyalty and advocacy over time.
For example, an NPS question might be: "On a scale of 0-10, how likely are you to recommend our product to a friend or colleague?"
Tracking NPS trends helps you understand if your product improvements are working.
Field exercise: Designing a feedback plan (20 min)
Pick a product you are currently working on or interested in. Write down:
- What are the key user problems you want to validate?
- Which feedback methods will you use at each stage: discovery, pre-launch, post-launch?
- How will you prioritize and analyze the feedback you get?
- What metrics will you track to measure customer satisfaction and product impact?
This exercise forces you to think systematically about feedback, not just reactively.
Test yourself: Prioritizing user feedback at a Series B SaaS startup
You are a PM at a Series B SaaS startup in Mumbai. Customer support tickets show frequent requests for a new reporting dashboard. At the same time, your analytics show a 10% drop in active users after onboarding. The CEO wants you to focus on the dashboard because it sounds more exciting.
The call: How do you prioritize between building the new dashboard and fixing the onboarding drop-off? How do you communicate your decision to the CEO and the customers?
Your reasoning:
You are a PM at a Series B SaaS startup in Mumbai. Customer support tickets show frequent requests for a new reporting dashboard. At the same time, your analytics show a 10% drop in active users after onboarding. The CEO wants you to focus on the dashboard because it sounds more exciting.
Your task: How do you prioritize between building the new dashboard and fixing the onboarding drop-off? How do you communicate your decision to the CEO and the customers?
your reasoning:
Where to go next
- If you want to learn how to conduct effective user interviews: User Research Methods
- If you want to translate user feedback into product strategy: Product Vision and Strategy
- If you want to measure customer satisfaction effectively: Metrics and KPIs
- If you want to deepen your skills in prioritization: Prioritization Frameworks