If You Do This, You're the Worst Kind of Product Manager
If you do this, you're the worst kind of Product Manager.
A customer makes a request, and before they even finish, you jump in: "Oh, we already have that feature! Let me show you..."
A customer shares an issue, and you instantly respond: "Here's how you can fix that..."
A customer provides negative feedback on a new release, and you immediately start defending: "We did a good amount of research..."
Each of these responses feels helpful in the moment. You're being proactive. You're being responsive. You're showing that you know the product.
But each one shuts down the conversation before it starts.
TL;DR: When you jump to solutions before listening, you lock yourself into your interpretation of the problem. When you slow down and ask "tell me more," you uncover context that changes everything. Customers don't just want features or fixes. They want to feel heard. And when they feel heard, they trust your judgment.
The three responses that kill conversations
The premature feature showcase
Customer: "We're struggling with tracking which team members have completed their..."
PM: "Oh! We already have that. Let me pull up the dashboard. Here, you can see completion rates by team member, and there's even a filter for..."
What just happened: You assumed you knew what they needed based on three words. Maybe they don't need a dashboard. Maybe they need a notification. Maybe the "tracking" problem is actually a process problem, not a tool problem. You'll never know because you stopped listening.
The instant solution
Customer: "When we try to export the monthly report, it takes forever and sometimes..."
PM: "You can fix that by switching to the scheduled export. Go to settings, then reports, then..."
What just happened: You solved the surface symptom without understanding the root issue. Maybe the export works fine but they need it in a different format. Maybe "takes forever" means the data set is too large because they don't know about filters. Maybe they need the data in another tool entirely.
The defensive reflex
Customer: "The new workflow doesn't really work for our team because..."
PM: "Actually, we did extensive research before building this. We interviewed 20 teams and the current design solves for the most common pattern..."
What just happened: You told the customer they're wrong. You made them feel like their experience doesn't matter because your research says otherwise. Even if your research was thorough, this customer is telling you their reality. And their reality is valid.
What great Product Managers do instead
Great PMs know this: if it's a request or feedback, listen and ask for use cases before proposing existing features.
Instead of: "We already have that!" Try: "Tell me more about when this comes up. What does your current workflow look like?"
If it's a concern, listen and ask for scenarios before offering solutions.
Instead of: "Here's the fix." Try: "Can you walk me through what happens when you hit this issue? What's the impact on your team?"
If it's negative feedback, listen and probe before defending.
Instead of: "We researched this thoroughly." Try: "That's useful to hear. Can you tell me specifically where it breaks down for your team?"
Why listening changes the outcome
When you don't listen, you lock yourself into your interpretation of their request or problem. And your interpretation is filtered through your knowledge of the product, not their knowledge of their workflow.
When you slow down and ask questions like:
- "Tell me more about when this happens"
- "What is the impact on your workflow?"
- "How are you handling this currently?"
- "What would the ideal solution look like for you?"
You uncover the context. And context changes everything:
- The "feature request" turns out to be a training gap
- The "bug" turns out to be a process mismatch
- The "complaint" turns out to be a specific use case you hadn't considered
- The "negative feedback" turns out to reveal a segment you're not serving well
Each of these insights is more valuable than solving the surface-level problem. And you only get them by listening first.
Customers want to feel heard
This is the part that most PMs miss. The functional outcome (feature, fix, solution) is only half of what customers want from interactions with you.
The other half: they want to feel heard.
When they feel heard:
- They're more open to your ideas (even if the answer is "we can't build that")
- They're more trusting of your judgment (even if you push back on their request)
- They're more likely to see you as a partner rather than a vendor
When they don't feel heard:
- Every "no" feels dismissive
- Every workaround feels like you don't care
- Every interaction feels transactional
The 30 extra seconds of listening buys you exponentially more trust and cooperation. It's the cheapest investment you can make in a customer relationship.
The pattern to practice
Next time a customer says anything (request, complaint, feedback, concern), try this:
- Listen fully. Let them finish. Don't interrupt. Don't formulate your response while they're talking.
- Acknowledge. "I hear you. That sounds frustrating." (Not agreement. Acknowledgment.)
- Ask one clarifying question. "Can you tell me more about [specific thing they mentioned]?"
- Ask one context question. "How often does this come up? What's the impact when it does?"
- Then respond. Now you have enough context to offer something useful, whether that's an existing feature, a workaround, a future plan, or simply "I need to think about this."
The whole thing takes 2 minutes longer than jumping to a solution. But the quality of the outcome is 10x better.
This applies beyond customers
This is not just a Product Management skill. It's basic professional etiquette.
Whether with customers, colleagues, or stakeholders: listening first and probing for clarity before defending your point of view almost always leads to better outcomes.
- An engineer pushes back on your spec? Listen first. Ask why. Maybe they see a constraint you missed.
- A stakeholder disagrees with your priority? Listen first. Ask what they're seeing. Maybe they have customer context you don't.
- A designer challenges your direction? Listen first. Ask what they're thinking. Maybe they see a user need you overlooked.
In every one of these situations, the person who listens first wins. Not because listening is "nice." Because listening gives you information that makes your response better.
The bottom line
The worst PMs are the ones who talk first. Who assume they know what the customer needs before the customer finishes speaking. Who defend before understanding.
The best PMs are the ones who listen first. Who ask questions that reveal context. Who make people feel heard before offering solutions.
It's a small shift. Two extra questions. Thirty extra seconds. But it changes every customer interaction, every stakeholder conversation, and every team discussion.
Agree?
How ProductResume helps
Listening, empathy, and customer understanding show up on strong PM resumes as evidence of deep discovery work. If your bullets say "implemented customer-requested features," they miss the point. If they say "uncovered 3 unaddressed workflow gaps through customer interviews, driving a 20% reduction in support tickets," that signals real listening. Score your PM resume to see how your customer-facing experience reads.