This book will probably be incomprehensible to someone not already working as a product manager in the technology industry. It's poorly written, excessively abstract / short on examples, and densely packed with industry jargon. Still, there seem to be very few books on product management, and this one does have more than a few useful insights. Also, it's short (~80 pages).
Some highlights:
- "It is the product manager's responsibility to identify customer problems worth solving. It is engineering's role to identify technical solutions to those problems."
- "Product managers must constantly accomplish their goals through organizational functions over which they have no direct authority. They must use their skills of persuasion and diplomacy to make things happen."
- "At Facebook they like the mantra, 'Don't fall in love,' as a way to ensure that the product team doesn't get so enamored of their own ideas that they ignore or rationalize feedback from the people that matter."
- "Have every pertinent piece of information documented. You can measure your success by the frequency people quote or refer to your documents."
- "Imagine a world where the problem has already been solved. This is the core of most good science fiction. Take a problem that has been solved by some advanced technology and explroe the resulting world or environment."
- Be a good listener. Don't formulate a response prior to the end of a conversation.
- Good product marketing is spending marketing dollars wisely by identifying what influences your target market. For example, friends, influential blogs, thought leaders, or particular publications or news sources.
- "Successful product managers don't argue their own position on what the product should be. Instead, they present a point and support it with real live customer insights and feedback."