Amazon calculates a product’s star ratings based on a machine learned model instead of a raw data average. The model takes into account factors including the age of a rating, whether the ratings are from verified purchasers, and factors that establish reviewer trustworthiness.
Apart from the fact that the 6 questions at the back of the book make it worth the read all on their own, the rest of this great book covers what it take to build a true product-led company where anything (everything) is possible. I really enjoyed the flow of the narrative as the book progresses and how Melisa points out so many things which caused me to think ah-ha! If I had one critique I’d ask for more visuals linking key ideas and concepts together, there is so much here, I’d suggest you bring a pen and a notebook to draw out the ideas shared yourself, as you read along. Having said that, this book is a must read!
For practitioners (and particularly consultants), the best business books effectively articulate 'that nagging feeling that we should be thinking and acting differently,' accessible to anyone working in the domain. Escaping the Build Trap achieves this superlatively.
Written with clarity and plenty of illustrative examples borne out of long, hard-won experience, it explains both the 'How should we work?' and 'Why is that important?' in language that doesn't require a doctorate in Agile to understand.
I suspect that many copies of this will be 'conveniently' left on the desks of exec stakeholders. Some of them by me.
Excellent book—easy to read, with just the right (for me) mix of clear and concise explanations, humour, and illustrative anecdotes.
It's short enough to read in a few hours, but can introduce you to many concepts and practical practices worth further reading.
Covers the benefits of product led organisations, and how to create alignment around mission, vision, goals, strategy, as well as how to iterate & experiment towards success at all levels. In contrast to top-down edicts, elaborate plans, locked down budgets & immutable roadmaps.
Worth a read for anyone from those considering a move into product management, to software engineers who want to deliver value, to executives who want to be successful.
Even if the content and concepts aren't new to you, it's likely to be an inspiring reminder of what good looks like.
This book is absolutely hands down the best practical product management book out there right now. Rather than simply preach the theory like many other books it also gives a number of practical steps, examples and frameworks on the modern outcome focused practice of product management and helps set the benchmark by which product managers should be aiming to work. I had been battling with the theories taught by Marty Cagan, Jeff gothelf et al and how to pratically apply them but more so how to articulate in a practical way to my teams.
I work in a large scale 10k plus organisation with large scale nationally important products. I have already shared and bought this book for other product managers struggling with what good modern product management looks like and as a guide on the best practice.
I thank Melissa for writing such an easy to follow book with the right mix of theory and craft with practical frameworks to help.
Must read for anyone getting to grips with product management in 2019.
I've seen Melissa talk about this topic at conferences so was eager to see how she pulled this material together in a book. I liked how it assumed you knew nothing about product development, agile, or service design, but dropped the relevant parts in as you needed to know about them. The moving back and forth from the theory and practice to the ongoing fictional scenario showing how the ideas were used for the company was really useful too. These aspects of the book are why I recommended that my students get a copy of this book. You should get one too if you're thinking of (or indeed have) started a company, or are a product owner at a software company.
An insightful and refreshing book on product management. Well written, well paced and opinionated, this book matters.
There's nuance and learning in every paragraph. From how to structure product teams, to how to think about strategy, to projects vs products vs services, there's incredible learning to be had for everyone, regardless of where they are in their PM careers.
If you read a bunch, and you find most books lately to rhyme the same, be excited to know that this one doesn't. It stands out. And that's remarkable.
I really enjoyed the book, and I would recommend picking it up. My only complaint is perhaps that I wish that the fourth and fifth parts were a bit longer and went deeper into the techniques and practices of product-led organizations. I almost wish I could have a companion book, in the same way, that the The Phoenix Project was later complemented by The DevOps Handbook. Overall, it is worth a read for anyone who is stepping into the product world or wants to learn about new ways to help their team or organization to achieve more.
This book tackles the fundamental problem in software - building the wrong thing. It does so by focusing on valuable outcomes and gives insight, ideas and methods to help the reader. It has the great virtue of being short with each chapter building on the previous to give you a richer understanding of what product management means and why organisations need to put it front and centre. Like Wodtke's 'Radical Focus' and Goldratt's 'The Goal' is uses narrative and story to great effect. I bought it for myself and then bought another copy for a colleague. Recommended.
A super book. If you’re struggling to become a product-led organisation then this needs to be on your bookshelf. From organisational culture to the product management role Melissa has delivered a great guide to spotting and solving the problems companies have shifting from an output to an outcome focus. I’ve already bought several copies for my clients.
Melissa's book provides actionable guidance for developing a product led organisation, with particular focus on understanding what should be built and why over hap-hazard feature development. I'm recommending it to anyone who will listen.