Escaping the Build Trap book club questions

1. 1.

   Perri's build trap is defined by measuring features shipped rather than outcomes produced. How would you honestly describe the way your current or most recent team measured success?

2. 2.

   She argues that product managers in the build trap are really project managers. If you have worked in a product role, does that characterization ring true? What would have needed to change for the role to be genuinely strategic?

3. 3.

   The shift from output to outcome thinking requires changing not just individual practices but organizational incentives. What incentive structures in your experience have most strongly pushed teams toward output over outcome?

4. 4.

   Perri's distinction between product strategy and product roadmap is central to the book. Have you seen organizations confuse the two? What went wrong as a result?

5. 5.

   She argues that executives who specify the solution rather than the goal eliminate the strategic layer of the organization. Have you seen this happen? Is there any context in which it's appropriate?

6. 6.

   Discovery and delivery in parallel is the ideal she describes. What makes companies default to sequential discovery-then-delivery, and what would it actually take to change that?

7. 7.

   What is the role of direct customer research versus analytics in the discovery process she describes? When is each more valuable?

8. 8.

   The book focuses on product organizations, but the build trap pattern — measuring output rather than outcome — appears in many other contexts. Where else have you seen it, and does Perri's analysis apply?

9. 9.

   Her prescription requires real authority and strategic ownership for product managers. What happens to this proposal when the people setting strategy are unwilling to give up control of the solution?

10. 10.

    Perri identifies the build trap as partly a cultural problem — teams take pride in shipping. How do you change a culture that has organized its identity around delivery velocity?

11. 11.

    The book is concise at around 200 pages. What does that brevity make possible or foreclose in the argument?

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.