One of the most insightful pieces that I've read. The emphasis to be on the field is so on to the point. We need to know about our users before building anything for them. The defination of PM is also correctly pointed out as PMs need to solve problems via product.
I would just like to add a bit here, as PM job is not just to solve problems via product but also ensuring that the target users are using the product to solve the problem.
As many a times it happens that the product is able to solve a problem but the users are not using it (due to various reasons like complexity, doing things manually is more easy etc) and to me that's a failed product and the PM has not done their job.
One of the most insightful pieces that I've read. The emphasis to be on the field is so on to the point. We need to know about our users before building anything for them. The defination of PM is also correctly pointed out as PMs need to solve problems via product.
I would just like to add a bit here, as PM job is not just to solve problems via product but also ensuring that the target users are using the product to solve the problem.
As many a times it happens that the product is able to solve a problem but the users are not using it (due to various reasons like complexity, doing things manually is more easy etc) and to me that's a failed product and the PM has not done their job.