Good PMs listen to users.
Great PMs know when not to.
That took me a while to understand.
When you first get into product, you treat every user conversation like gospel.
A user says they want a feature.
You write it down.
Three users say the same thing.
You call it validation.
Ten users say it.
Now it’s on the roadmap.
But here’s the trap:
Users are usually right about their pain.
They are not always right about the solution.
They’ll tell you:
“Add a dashboard.”
“Give me more filters.”
“Send me more reminders.”
“Make it like this other tool.”
But underneath that request is usually a deeper problem:
I’m confused.
I don’t trust the output.
I don’t know what to do next.
I don’t feel progress.
I’m scared of making the wrong decision.
The PM’s job is not to copy-paste user requests into Jira.
The PM’s job is to translate messy human frustration into a product decision.
That means listening deeply but not literally.
It means asking:
What are they really trying to accomplish?
What anxiety is this request hiding?
What workaround are they using today?
What would make this feel obvious instead of complicated?
This is where product judgment comes in.
Because if you build exactly what users ask for, you often end up with a bloated product.
But if you understand why they asked for it, you can build something much sharper.
User feedback is not the answer key.
It’s the raw material.
The PM’s job is to turn it into insight.