INSPIRED
Title: How do you build technology products that customers love?
Inspired by Marty Cagan is effectively the “bible” of modern product management. Cagan’s main point is: “Many companies produce product in a way that belongs to decades ago and is doomed to fail.”
If you do not want to read the whole book, these are the most important ideas you should keep in mind:
1. The difference between a “product team” and a “feature team”
Organizations’ biggest mistake is using technical teams as mercenaries, not missionaries.
- Feature team (feature factory): Management tells them what to build (a list of features or a roadmap). Their success is measured by “output” (how many tasks got done?).
- Real product team: They are given a “problem” to solve. Their success is measured by outcome (for example: user churn drops 10%).
2. Managing the four main risks
Cagan argues that the product manager’s job is to neutralize these four risks before a single line of code is written (the most expensive part of the work):
- Value risk: Will the customer even buy this product or use it?
- Usability risk: Can the user figure out how to work with it?
- Feasibility risk: Can our engineers build it with the technology, time, and budget we have?
- Business viability risk: Does this solution fit the rest of the business (sales, legal, finance, and marketing)?
3. Separating product discovery from product delivery
Cagan splits the product process into two parts that should run at the same time, in parallel:
- Product discovery: Its goal is to answer “what should we build?” This part is fast and cheap (using prototypes).
- Product delivery: Its goal is to answer “how do we build it at high quality?” This part is expensive and time-consuming (real coding).
Golden rule: You should never put something into delivery unless you have proven in discovery that it is worth building.
4. The real role of the product manager (PM)
In Inspired, the product manager is neither a boss nor a secretary who only takes notes. The PM must be an expert in four domains:
- Knowing the customer: Their pains, needs, and behaviors.
- Knowing the data: Monitoring users’ real behavior (not only what they say).
- Knowing the business: Stakeholders, legal constraints, and the revenue model.
- Knowing the industry: Competitors and market trends.
5. Prototyping instead of writing documents
Cagan is strongly against writing long documents (50-page PRDs). He argues that a product team’s main tool for communicating with everyone else is the prototype. Prototypes let the team test ideas with real users at very low cost and kill large failures in the cradle.
Final takeaway for you:
If you want to work by the principles of this book, you have to go from being an order-taker (who only ticks off the CEO’s feature list) to a problem-solver. Your success is not in how many features you released, but in how much change you created in user behavior and in the company’s profitability.
The book’s famous line: “It doesn’t matter how good your engineering team is; if they work on the wrong product, talent is wasted.”