There's no way to answer this in a comment...you can take a full course on tech product management and still not have all the answers. But I'll at least offer some advice: Just be very good at measuring and presenting data from all the channels in your company. Your customers, your prospective customers, your customer engineers, your sales people, your support team, your engineering managers, directly from developers…
This is a great comment. Love it. On my end, I’ve recently started working on documenting (still very, very early) on the “measuring” part at https://datadriventeam.org . It is backed by an open source GitHub repo and I hope people would contribute once I’ve gotten the initial version out.
> Good PMs know the importance of talking to customers frequently. Good PMs listen intently to customers to develop their product hypothesis. Great PMs also listen to what isn’t said and anticipate where the industry overall is headed when developing their product hypothesis.
How do you think about balancing data (customer) driven approach and product vision? This is an age-old question. I sided with the former and am learning that there's also wisdom in the latter. This might be a better way to put it: there's time and place for each approach, in a product's life cycle.