Inspired: How to Create Tech Products Customers Love book club questions

1. 1.

   Cagan describes the feature factory as the most common failure mode in product organizations. What does it look like in practice, and what are the conditions that create it?

2. 2.

   What is the difference between product discovery and product delivery? How should a team allocate time between the two?

3. 3.

   Cagan says PMs must be deeply knowledgeable about customers, business, technology, and market. How do you build that knowledge, and what happens when any one of the four is missing?

4. 4.

   The book argues that design should be a first-class partner, not a service. What does it look like when design is treated as a service, and what does the product experience feel like as a result?

5. 5.

   Have you seen a product team that was genuinely empowered to discover and deliver — not just execute on a roadmap? What made that possible?

6. 6.

   Cagan says the roadmap is often the enemy of good product work. What's the right relationship between a long-term product vision and a short-term execution plan?

7. 7.

   How do you run a prototype test that is genuinely informative rather than just confirmatory? What makes customers tell you what you want to hear instead of what is true?

8. 8.

   What is outcome over output, and how do you measure outcomes for products where the metrics are lagging rather than leading indicators?

9. 9.

   Inspired is primarily about consumer and enterprise software. How much of the framework applies to products that are not primarily software?

10. 10.

    Cagan describes a strong PM as someone who understands the customer better than anyone and the business constraints well enough to make hard tradeoffs. How do you develop that kind of judgment?

11. 11.

    What's the difference between a product manager and a project manager? Have you seen organizations that confuse the two roles, and what was the effect?

12. 12.

    If you were redesigning how a product team works today based on Cagan's framework, what would you change first and why?

How to run the discussion

• Pick six to eight, not all of them. An hour of real discussion covers fewer questions than anyone expects, and racing the list is what makes a book club feel like homework.
• Open with what people noticed, not what they concluded. Asking for a verdict first hardens opinions before anyone has heard each other.
• Let the disagreement run. The questions below that split a room are the ones worth the time; the ones everyone answers the same way can be skipped.
• Ask the quiet person a specific question. A direct, narrow question is far easier to answer than an open invitation to contribute.