Ideally, you don't just talk to them. You watch them work. Observe, and gather clues about what will serve their needs. And when people tell you what they think they want, don't assume that's the product spec; treat that also as an opportunity to listen to clues that will help you understand their needs.
The best products are designed around how people work, not necessarily what people say about how they work.
This reflects a lot my experience: People actions >>>> People words.
while there are problems with that assertion, hiring is largely serendipity. as an extrovert, serendipity for me is found while out and about.
- UX Product Managers (close to users)
- Technical Product Managers (close to developers)
I've written about this a little bit here for the curious: https://alexpetralia.com/posts/2019/10/14/product-management...
In my humble experience, I think the real value of a TPM is being the interface between management and technology. They're able to frame technical jargon in a way that the business can understand. i.e. Why we have to do this refactor? If we don't it will cost the company money. (contrive but you get the point)
Running A/B tests is IMO, a good proxy, to understand customers unbiased binary views on feature changes, and objectively better.
A/B tests let you know if you've solved the problem.
There is a use case for both.
Well, no, that's the sales job. First being a product manager is different in every company. And second there is a lot of differences depending of the type of business you are working in.
For example if you work in Saas b2b enterprise you can easily be a very good product manager and almost never meet the customers nor the users [1], because that's not what is important for the business.
On the contrary if you work in Saas b2c, talking (or doing surveys) to customers is crucial. So I would say that your advice apply well to B2C, in which there is no sales people
[1] https://blog.luap.info/product-management-in-saas-b2b-enterp...
You can’t trust a salesperson to think about the broader good when half their comp is tied to specific deals.
Salespeople usually have more influence on the customers than on the roadmap, so they're better of trying to influence the decision making of the customer, than the product.
Salespeople focus on their sales targets, trying to change a product roadmap is not a very effective way to reach short term targets.
Obviously, a product manager should reach out to sales to try and understand their perspective on the product and the customer needs.
That's a different product focus from the end user (who probably finds the new operations checkboxes demanded by the decision maker a horrible pain) and instead of actually using it, their perception will be shaped by middle management feedback and some claims made by the enterprise salesperson about how much money their business can save from staff being able to complete X faster or Y being shared, but it very much is a product based decision. Otherwise the lowest bidder (or at least the lowest bidder with an SLA) or incumbent would win every time.
OK not in times of COVID but there has to be someone who actually talks to customers or potential customers in person and builds _qualitative_ opinions / insight into what really needs to be built and where the real opportunities are. And that’s not to knock analytics, surveys and various other forms of customer feedback ... it’s just if you’re not directly talking to customers product development becomes an echo chamber of unvalidated opinions about how the world works. And there’s always huge and surprising insights to be gained from direct communication with customers...
From there you have to sift out signal from noise and create product vision and priorities.
Doing this PM function well quickly becomes full time and conflicts with the job of being a PO and working closely with developers.