2 of 2 people found the following review helpful
on 15 September 2011
As an experienced Product Manager who has been working for major internationally recognised brands for many years it would be easy for me to assume that I knew it all. I would be wrong. Marty knows it all. In this book he has delivered a template on, as the title says, how to create products customers love. The book is a must have for anyone who is, wants to be, or has to work with a Product Manager. The writing is clear and the online support gives the reader the tools she needs to excel in the role. I have recommended this book to my peers, the people I manage and my boss and everyone has raved about it.
The techniques described in the book save time and money and stress and if properly applied with enable organisations to deliver the products that their users and customers need.
Product Management need be misunderstood and poorly done no longer.
Thanks to Marty we can all look forward to enjoying creating and using interactive products a whole lot more.
on 21 August 2010
This book is a great practical reference for a product manager or someone managing a product management team. It has a lot of best practices (common in many companies now, for instance, interaction designers, personas and usability testing), but also a lot of ideas and suggestions (using high-fidelity prototype instead of a spec. In fact, everyone who has ever written a spec or (much rarer) has read one thinks it is for the most part a waste of time - so why do we keep doing it?).
* What to do when engineering tells you that your platform is about to collapse, and how to prevent this situation.
* Product manager should work with interaction designer to create a prototype and test it with customers a lot (no, seriously, A LOT). This prototype should be a throw-away, not the actual product. Involve and architect in this as well to make sure that the solutions PM and Designer come up with will be implementable.
* Minimal product: the role of the product manager is to figure out the minimal product that the market wants and deliver it (benefit of cost and time for the company and low learning curve for the customer).
* Rapid response team: have a small team that can work on "there is a bug here we need to fix it urgently" without distracting the team that is working on delivering another version of the product.
* Emotional adoption curve: look for users who are angry at something - this is where an opportunity lies if you can fix the thing that annoys them.
* Ideas how to innovate and succeed in large companies
Also, check out Marty's blog at svpg(dot)com, a lot of ideas in the book are discussed there.
on 31 October 2011
I love this book, and have recommended it in person to a number of people. It's a GREAT description of how to get the best product management process going in your organisation, and a whole load more besides. The focus is mostly on digital (software) products, but there's lots to inspire people working in other industries too.
For some reason, it's not easily available in physical form in the UK, but I would strongly recommend ordering (and waiting for) a copy from the US if (like me) you like to cover your books in sticky highlight flags. I have lots in my copy!
1 of 1 people found the following review helpful
on 30 December 2013
Very good and inspiring. Easy to read, easy to follow and comprehend. I recommend this book for every PM, mainly from IT.
0 of 1 people found the following review helpful
on 22 April 2013
Big five stars. Timeless book. Lots of practical, timeless advice and fact more than opinion. I struggle with project versus product manager not by his definition but in how industries blend both roles together, a hard glue to dissolve.
My inference: The designers should code model applies here in that the 'design sprint' is involved in the exploratory sprint before implementation. Designs take shape in a prototype of HTML and CSS. This encourages live style guides.