“She wrote the most important book in the space called Accelerate”
← All resourcesbook
Accelerate
By Nicole Forsgren, Jez Humble, and Gene Kim
3 recommend/use · 4 sourced episodes
Every sourced reference
Short attributed excerpts only. Timestamps are approximate.
RecommendsThe engineering mindset
“one of the most influential books in the last decade um in kind of software engineering leadership and and kind of infrastructure is accelerate”
“there's Dora there I wrote a book called accelerate”
“also pick up a copy of accelerate on Amazon or your local retail establishment”
“the second one I think would probably be accelerate”
Related frameworks
Leadership4 steps
Chronic vs Acute Organisational Challenges
Work down the chronic issues so you have capacity to absorb the acute shocks.
Read →
Communication6 steps
Energy-Aligned Writing
Write only what energises you, only what overlaps your job, and publish nearly all of it.
Read →
Influence5 steps
Find the Loops Available to You
Even when told exactly what to build, you can still run most of the product loop.
Read →
Innovation4 steps
Frameworks as Job Aids, Reps as the Goal
Adopting a framework is never the goal; getting reps through the full loop is.
Read →
Leadership5 steps
Friction Smells: Signs Your Team Can Move Faster
The tell-tale signals that friction, not capability, is capping your team's speed
Read →
Productivity5 steps
Imperfect Metrics as Education
Report an imperfect engineering metric on purpose, then use every question about it to educate upward.
Read →
Productivity3 steps
Prescriptive vs. Framework Metrics
Know whether your metric is a recipe or a lens — and never misuse a recipe
Read →
Productivity4 steps
Prime-Then-Parallelize AI Coding Workflow
Front-load the architecture, fan out to agents, then step back and evaluate
Read →
Communication5 steps
Reframe Metrics to Leadership's Language
Pick two or three metrics that speak the exact word your leaders keep repeating
Read →
Strategy5 steps
Stocks-and-Flows Pipeline Diagnosis
Model any org process as stocks and flows, then find where reality disagrees with the model.
Read →
Strategy5 steps
The Boring Engineering Strategy
Write the strategy down, get the diagnosis honest, then constrain options so energy goes to what matters.
Read →
Innovation7 steps
The Data-Informed Product Loop
Strategy to models to measurement to bets to impact to learning — find the broken link.
Read →
Leadership4 steps
The DevX Listening Tour
Before you build a tool, walk developers through their yesterday
Read →
Productivity4 steps
The DORA Four Keys
Measure software delivery with two speed and two stability metrics that move in tandem.
Read →
Leadership5 steps
The Five Markers of High-Performing Product Teams
Coherence, stubborn beliefs, faith in product, matching words to actions, contextual skills.
Read →
Strategy5 steps
The Four-Box Framework
Write your hypothesis in words before you touch data, so you can debug the idea and the measurement separately.
Read →
Leadership7 steps
The Frictionless Seven-Step DevX Program
A start-anywhere playbook to stand up a developer-experience initiative
Read →
Leadership4 steps
The Honest-Applicable-Reversible Values Test
Three tests that separate values which drive decisions from values that just describe your self-image.
Read →
Strategy4 steps
The Measurement Journey
Start measuring from words and people, then scale into system data — don't wait for perfect.
Read →
Self-Mastery5 steps
The Pyramid of Leadership Self-Awareness
Four levels from knowing nothing about yourself to treating diverse worldviews as an asset.
Read →
Strategy4 steps
The Reverse Anna Karenina Principle
Dysfunctional companies all fail the same way; high performers succeed in wildly different ways.
Read →
Leadership5 steps
The Shared-Fate EM/PM Pair
Give the eng manager and PM the same performance rating, and make them understand before they argue.
Read →
Productivity4 steps
The SPACE Framework
Pick balanced developer productivity metrics across five dimensions — never rely on one.
Read →
Productivity5 steps
The Top-Three Weighted DevX Survey
Force a top-three, weight by frequency, and never ask four questions at once
Read →
Self-Mastery5 steps
The Weighted Decision Spreadsheet
List your options, weight your criteria to 100%, score and multiply — then let the reaction tell you the answer.
Read →
Self-Mastery4 steps
Unpack the Mindset Into Teachable Skills
Replace 'product sense' and 'high agency' with the specific competencies underneath them.
Read →
People in these episodes
Related resources
- Airbnb
- Amazon
- Amazon Web Services
- Amplitude
- An Elegant Puzzle
- Apple Podcasts
- Atlassian
- Back Mechanic
- Booba
- Calm
- Carta
- ChatGPT
- Claude Code
- Coda
- COSRX
- Cursor
- Designing Your Life
- Don't Think of an Elephant!
- DORA
- DORA Quick Check
- DORA Report
- dora.dev
- Drift
- DX
- Eight Sleep
- Ender's Game
- Eppo
- Figma
- Gemini
- getdx.com/Lenny
- GitHub
- GitHub Copilot
- Good Strategy/Bad Strategy
- Google Cloud
- Google Reader
- Google Search
- Greenhouse
- How Big Things Get Done
- How to Measure Anything
- IBM
- IKEA
- Intercom
- Java
- Jira
- JURA coffee machine
- LEGO
- Lenny's Newsletter
- Lenny's Podcast
- lennyspodcast.com
- Love Is Blind
- Medium
- Mercury
- Merge
- Microsoft
- Microsoft Azure
- Netflix
- Never Have I Ever
- Ninja CREAMi
- Nubank
- OneSchema
- OpenAI Codex
- Outlive
- Python
- Ruby
- Shrinking
- Slack
- Sooner Safer Happier
- SPACE
- SPACE Framework
- Spotify
- Stripe
- Substack
- Suits
- Tabnine
- Technology Strategy Patterns
- Ted Lasso
- The Crux
- The Knowledge Project
- The Phoenix Project
- The SPACE of Developer Productivity
- The Three-Body Problem
- The Undoing Project
- The Value Flywheel Effect
- Toast
- Top Chef
- Uber
- User Story Mapping
- Vanta
- WorkOS
Spot an error or want this page removed? Request a correction or removal.