You need to know the product and if the product is software, you should be familiar with its quirks or can chat with developers at that level.
You don’t have to know how code works to know something about how it works. Ideally, you should be able to give directions to your QA person on how to get started interactively testing new features, etc.
Leading developers requires tech knowledge, leading product managers requires strong product knowledge as well as an understanding of what’s possible and what might not be possible, which one develops over time learning an app.
Might not align well with the above statements, but I recommend the following books for product folks:
You don’t have to know how code works to know something about how it works. Ideally, you should be able to give directions to your QA person on how to get started interactively testing new features, etc.
Leading developers requires tech knowledge, leading product managers requires strong product knowledge as well as an understanding of what’s possible and what might not be possible, which one develops over time learning an app.
Might not align well with the above statements, but I recommend the following books for product folks:
INSPIRED: How to Create Tech Products Customers Love https://g.co/kgs/CxFues
EMPOWERED: Ordinary People, Extraordinary Products https://g.co/kgs/2DhX7s
Product Roadmaps Relaunched: How to Set Direction While Embracing Uncertainty https://g.co/kgs/EthDBf
Product can contribute strong to the visible software while leaving the tech and implementation decisions to technical teams…