Business · Book club
Accelerate book club questions
Here are 12 book club questions for Accelerate by Nicole Forsgren, Jez Humble, and Gene Kim, ordered to open easily and end somewhere worth arguing about. Copy them, print them, or bring them up one at a time.
Accelerate is the research-backed account of what actually makes software delivery teams fast without sacrificing stability.
Nicole Forsgren, Jez Humble, and Gene Kim · 2018 · 4h 45m
Full summary and key takeaways →The 12 questions
- 1.
Which of the four key metrics does your organization measure, and which ones are invisible to leadership?
- 2.
Forsgren argues that speed and stability are not in tension for high performers. Where in your organization does the assumed trade-off show up, and is it real?
- 3.
What approval gates slow down your team's deployments? Which ones are genuinely risk-reducing and which are theater?
- 4.
The book links architecture to autonomy. What about your system's architecture prevents teams from deploying independently?
- 5.
How would you describe your organization's culture using Westrum's three types — pathological, bureaucratic, or generative? What evidence supports that reading?
- 6.
The authors found that psychological safety predicts performance. What specific behaviors in your team make it safe or unsafe to raise problems?
- 7.
Change failure rate is one of the four metrics. What is your current rate, and what is your team's honest theory about why incidents happen?
- 8.
If your team could eliminate one manual step in your deployment process, what would it be and what is stopping you?
- 9.
The book was written in 2018. Which of its findings feel more true today than they did then, and which feel less relevant?
- 10.
Forsgren is explicit about the limits of the research. Where do you think the data's conclusions break down for your context?
- 11.
What does your organization reward — speed, caution, or learning from failure? How does that reward structure shape behavior?
- 12.
Who in your organization has the authority to remove the biggest constraint on delivery performance right now?
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.
Themes worth steering toward
If the conversation stalls, these are the threads that usually restart it.
Common questions
What are good book club questions for Accelerate?
Here are 12 book club questions for Accelerate by Nicole Forsgren, Jez Humble, and Gene Kim, ordered to open easily and end somewhere worth arguing about. The strongest openers ask what each reader noticed rather than what they concluded, and the discussion usually turns on software delivery, organizational performance, devops.
How long should a book club discussion of Accelerate last?
Most groups run 60 to 90 minutes of actual discussion. That is roughly six to eight questions, not all of them, so pick the ones that suit your group rather than working down the list in order.
What are the main themes in Accelerate?
Software delivery, Organizational performance, DevOps, Continuous improvement, Leadership. Those are the threads most likely to divide a room, which makes them the useful places to steer a discussion that has gone quiet.
Picking the next one? See books like Accelerate or questions for other book club picks.
