Don’t Leave Your 2021 Goals to Your Future Self
Subscribe 12min Premium for under $0,1/day and get more knowledge now!
This microbook is a summary/original review based on the book: Inspired: How To Create Products Customers Love
Available for: Read online, read in our mobile apps for iPhone/Android and send in PDF/EPUB/MOBI to Amazon Kindle.
Also available in audiobook, download now:
Widely considered one of the best books on product management ever written, “Inspired” by Marty Cagan, the founder of the Silicon Valley Product Group, was first published long before Agile was well established in product companies and even longer before Customer Development and Lean Startup nomenclature became popularized. Since most teams nowadays use these techniques, Cagan decided to update the first edition of “Inspired” in 2017 to reflect the changes in the tech world.
Even though he had planned to modify no more than 20% of the original content, he ended up rewriting the entire book – in his words, not because he regretted what he had written in 2007, but because he felt that there were much better ways of explaining the topics originally covered by the book. Indeed, the second edition of “Inspired” reads a lot better than the first one and – partly due to Cagan’s more in-depth familiarity with his subject and partly due to improved techniques – it feels like it covers a lot more substantial ground.
Allow us to focus on just a few essentials from the first part and get ready to learn some of the key lessons from top tech companies while discovering the main concepts that form the foundation of modern product work!
Nine out of 10 product releases fail. The reasons are many, but if they can be summed up in two words, “waterfall processes” should do just fine. Namely, according to Cagan, the old waterfall model – in which there is no overlapping of phases, as each phase must be completed before the next phase can begin – is outdated and, moreover, incompatible with the modern tech industry. In fact, he implies, when it was first adopted for software development decades ago, it was merely in the absence of alternatives, not because people believed it worked.
In the waterfall model, everything starts with ideas, which can come from inside or outside, that is to say, either from executives, owners and stakeholders or from prospective customers. Then, these ideas are prioritized in a roadmap with the help of relevant business cases which eventually help product teams to narrow down the list. Once an idea makes it to the top, a product manager talks to the stakeholders and the two come up with a set of “requirements,” which are usually functional specifications, but can also be user stories. Next, the user experience design team provides the visual design or, in cases of physical devices, the industrial design. That’s the model engineers work with to build the test product. After a few iterations – or “sprints” as they are usually called – the QA team gives a green light and the new idea is finally deployed to actual customers.
There are problems with this way of working at almost any stage. First of all, the waterfall model leads to “sales‐driven specials and stakeholder‐driven products.” Moreover, it disempowers the team that actually makes the product: rather than missionaries, its members become mercenaries. Roadmaps are an even bigger issue because even the most carefully planned among them fail to take into consideration the two inconvenient truths about products. Namely, that half of our ideas don’t actually work and that the ones that do take several iterations to be refined to the point of delivering the necessary business value.
Unfortunately, the waterfall model makes product managers merely project managers because, by the time they enter the story, the product is already out of their hands and they can only gather the requirements and document them for the engineers. The same holds true for designers whose contribution to the creation of a product in the waterfall model can be likened to putting “lipstick on the pig.” However, the biggest missed opportunity in the model – at least according to Cagan – is the fact that engineers are brought in way too late. “The little secret in product is that engineers are typically the best single source of innovation,” he writes. “Yet, they are not even invited to the party in this process.”
By its very design, the waterfall model is “project-centric.” Unfortunately, writes Cagan, “projects are output and product is all about outcome.” By putting customer validation at the very end, the waterfall model sets companies up for predictable failure. After all, there’s no bigger waste of resources than to ideate, design, build, test and deploy a feature or product only to find that your customers don’t like it or that it was not what they needed in the first place.
Fortunately, that’s the key principle in Lean and Agile – to reduce waste. Both of these methods encourage teams to deliver fast by managing flow and by including most members of the team – as well as the customers – at all stages of product development. Unsurprisingly, most top companies today use Lean and Agile. In Cagan’s experience, however, the best among them go even beyond these two methods, showing religious devotion to the following three overarching principles:
According to Cagan, no more than a few key concepts form the foundation of modern product work. Here they are:
So, to sum up using the words of Cagan, “We use prototypes to conduct rapid experiments in product discovery, and then in delivery, we build and release products in hopes of achieving product/market fit, which is a key step on the way to delivering on the company's product vision.” Skip any of the steps, and you risk dealing with a lot of waste, and even devastating failures.
The first edition of “Inspired” was exceptional in itself; the second is even better. Both function simultaneously as an introduction to the process of modern product development, and a product management reference guide. Filled with personal stories and numerous relevant tips and tricks, “Inspired” is certainly one of the best-loved books by technology product managers today.
To quote Chad Dickerson, the former CEO of Etsy, “If you only have one book on product management, this is the one.”
If your company tackles product risks at the end of the production process, then it’s not following Lean and Agile principles, but the old waterfall model – whatever you might think. Define and design products collaboratively and include as many members of the team as possible at every stage of development.
Marty Cagan is an American entrepreneur and product manager, the founder of the Silicon Valley Product Group. Previously, he served as an executive responsible for defining and building products for many o... (Read more)
Now you can! Start a free trial and gain access to the knowledge of the biggest non-fiction bestsellers.