Product Management isn't as simple as just talking to your customers.
The reason why "talking to customers" is emphasized in PM books & circles a lot these days is because it's often not done regularly enough.
It's the first thing that gets put on the backburner when daily operations, spec work & delivery woes become overwhelming & chaotic.
However, while talking to customers is necessary, it's not sufficient.
To think that customer research will help you solve real-world problems is grossly over-simplifying the steep challenge of building a world-class & scalable product.
Product development certainly does start from creating empathy towards the end user.
However, here's where things become more complex:
When there are 5 different opinions on the same matter, who do you prioritize? You'll need a product strategy to target specific personas.
Customer discovery is an art of itself.
Uncovering jobs-to-be-done? It takes practice and a commitment to detach oneself emotionally from a specific solution or idea.
Now, you need to translate that into a solution that balances feasibility, usability and value. And while doing that, you also have to somehow upend the competition to make your product experience more compelling than theirs.
You can't simply relay what the customer said. You need to apply filters & fine-tune the edges.
From creating buzz to explaining benefits to stitching onboarding sequences, the product manager has to ensure they work with marketers & growth teams to select messages that resonate.
To sum up, taking out time to talk to customers (and churned users, prospects etc.) is an essential activity that a PM must carry out. And yes, understanding the problem clearly does set you up for later success.
However, it's only part of the job.
What comes after customer discovery is equally taxing & complex.
A PM is ultimately measured on their ability to timely ship a product that solves a problem at scale.
Don't just talk. Walk the talk.
As a Product Manager, you might be asked a lot of questions during an interview. One of them includes technical questions. Here are 4 types of technical questions that you might come across.