Empowered: Ordinary People, Extraordinary Products book club questions

1. 1.

   Cagan says most product organizations are feature factories. What are the organizational conditions that create a feature factory, and what does it take to change them?

2. 2.

   What is the difference between giving a team a problem to solve and giving them a solution to implement? Have you seen both, and what was the difference in outcomes?

3. 3.

   Product managers require deep knowledge of customers, business, technology, and market. Which of these four is hardest to develop, and what investment is required to develop it?

4. 4.

   Cagan is critical of top-down OKR processes. What goes wrong when OKRs are mandated rather than negotiated? Have you seen effective OKR implementations?

5. 5.

   The product strategy layer is where Cagan says most organizations fail. What makes it hard to create a product strategy that is specific enough to guide teams but flexible enough to allow discovery?

6. 6.

   Empowered requires a different kind of product leader than the feature factory. What experiences and capabilities distinguish a leader who can run an empowered organization from one who can only run a delivery-focused one?

7. 7.

   How does the empowered team model interact with the governance and accountability structures that most large organizations require?

8. 8.

   Cagan argues that designers should be first-class partners, not service providers. What changes in how design is structured, resourced, and evaluated if you treat it that way?

9. 9.

   The book is explicit that empowered product teams are not appropriate for all companies — organizations that are executing a well-understood playbook at scale may not need them. When is a delivery model actually the right model?

10. 10.

    How do you measure whether a product organization is empowered or a feature factory? What observable signals would you look for in a thirty-minute audit?

11. 11.

    Empowered focuses on technology product teams. How much of the framework applies to product development in non-technology companies?

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.