“She created the most used frameworks for measuring developer experience called Dora and Space.”
DORA
By Nicole Forsgren and collaborators
1 recommend/use · 6 sourced episodes
Every sourced reference
Short attributed excerpts only. Timestamps are approximate.
“I have done Dora metrics their speed metrics their stability metrics”
“including those behind the Dora and Space frameworks.”
“designed by Leading researchers including Those Behind the Dora and space Frameworks”
“DX is designed by the researchers behind Frameworks such as Dora space and devx”
“this framework Dora that's an interesting way of just measuring developer experience developer happiness”
“Dora is it's an entire research program”
“Dora would be space four mostly that outer loop”
Related frameworks
Beautifully Simple Pricing
In your early days, price so a customer can repeat it back and it tells a value story.
Choose Your Abstraction Layer Deliberately
Delegate the work you don't enjoy to a higher abstraction; keep the parts that make you good and happy.
Energy-Aligned Writing
Write only what energises you, only what overlaps your job, and publish nearly all of it.
Focused Hours Over Long Hours
Overwork lets you skip the hard work of deciding what matters — force the constraint that makes you decide
Friction Smells: Signs Your Team Can Move Faster
The tell-tale signals that friction, not capability, is capping your team's speed
Imperfect Metrics as Education
Report an imperfect engineering metric on purpose, then use every question about it to educate upward.
Mastering B2B Negotiations Through Value
Extract full value from every deal via gives-and-gets, value selling, and disciplined negotiation tactics.
Mastery Before Management
Get technical skill into your bones before you leave IC — then stay technical by listening, not coding
Platforms Are Products
When to start a platform team, who staffs it, and the impact metrics that keep it honest
Prescriptive vs. Framework Metrics
Know whether your metric is a recipe or a lens — and never misuse a recipe
Prime-Then-Parallelize AI Coding Workflow
Front-load the architecture, fan out to agents, then step back and evaluate
Problem-First AI Adoption
Start from the customer problem and ask where AI helps — never from 'what do we do with AI?'
Product-Manage the Platform Team From the Side
Frustrated by a slow internal platform team? Supply the product management they don't have
Reframe Metrics to Leadership's Language
Pick two or three metrics that speak the exact word your leaders keep repeating
Stocks-and-Flows Pipeline Diagnosis
Model any org process as stocks and flows, then find where reality disagrees with the model.
Stop Churn Before It Happens
To stop churn, acquire customers who won't leave — churn is an acquisition problem, not a save problem.
Take People With You Before You Fix Anything
A new leader's toolbox is worthless until the team agrees a problem exists — build the why first.
The 20/80 Willingness-to-Pay Axiom
20% of what you build drives 80% of willingness to pay — and it's usually the easiest 20% to build.
The Attribution-Autonomy Pricing Matrix
Pick your AI pricing model by plotting value attribution against product autonomy, then climb toward outcome-based.
The Boring Engineering Strategy
Write the strategy down, get the diagnosis honest, then constrain options so energy goes to what matters.
The DevX Listening Tour
Before you build a tool, walk developers through their yesterday
The DORA Four Keys
Measure software delivery with two speed and two stability metrics that move in tandem.
The Four-Box Framework
Write your hypothesis in words before you touch data, so you can debug the idea and the measurement separately.
The Four PM Annoyances
The four PM behaviours that quietly destroy engineering trust — and the fix for each
The Frictionless Seven-Step DevX Program
A start-anywhere playbook to stand up a developer-experience initiative
The Honest-Applicable-Reversible Values Test
Three tests that separate values which drive decisions from values that just describe your self-image.
The Horizon-3 Research Team That Ships
Fund a 3-5 year research team, then bolt it to product so ideas actually reach production.
The Input-Metrics Stack for Developer Productivity
No single metric rules them all — combine per-component input metrics that ladder up to time-to-value.
The Measurement Journey
Start measuring from words and people, then scale into system data — don't wait for perfect.
The One-on-One Diet
Hold direct-report 1:1s sacred; cut nearly all the rest — relationship-by-1:1 doesn't scale
The POC as Business Case
Frame every pilot as co-creating an ROI model, charge for it smartly, and never anchor the commercial deal.
The Rewrite Trap and the Staged Evolution Plan
Never go away for a year to rebuild — uplift well-contained pieces of the system instead
The Shared-Fate EM/PM Pair
Give the eng manager and PM the same performance rating, and make them understand before they argue.
The SPACE Framework
Pick balanced developer productivity metrics across five dimensions — never rely on one.
The Top-Three Weighted DevX Survey
Force a top-three, weight by frequency, and never ask four questions at once
The Two-Engine Profitable Growth Architect
Master market share and wallet share together — equal attention, not equal effort — to avoid the single-engine trap.
The Weighted Decision Spreadsheet
List your options, weight your criteria to 100%, score and multiply — then let the reaction tell you the answer.
The Zero-Ask Assistant (Copilot Design Philosophy)
If the user has to ask for it or wait for it, they won't adopt it — build assistance that infers.
People in these episodes
Related resources
- Accelerate
- Accenture
- Airbnb
- Alien: Romulus
- All the Light We Cannot See
- Amazon
- Amazon Prime Video
- Amazon Web Services
- An Elegant Puzzle
- Apple Podcasts
- Atlassian
- AWS
- Back Mechanic
- Business Model Generation
- Calm
- Canva
- Carta
- Chameleon
- ChatGPT
- Claude
- Claude Code
- Coda
- COSRX
- Cursor
- Dare to Lead Like a Girl
- Designing Your Life
- Don't Think of an Elephant!
- DORA Quick Check
- dora.dev
- DX
- Eight Sleep
- Ender's Game
- Enterpret
- Failing Forward
- Fin
- Gemini
- getdx.com/Lenny
- GitHub
- GitHub Advanced Security
- GitHub Copilot
- GitHub Next
- Goldman Sachs
- Gong
- Good Strategy/Bad Strategy
- Good to Great
- Google Cloud
- Google Reader
- Google Search
- Greenhouse
- HelpBar
- How Big Things Get Done
- How to Measure Anything
- IBM
- Intercom
- Java
- Jira
- Jira Product Discovery
- JPMorgan Chase
- jQuery
- JURA coffee machine
- Lenny's Newsletter
- Lenny's Podcast
- Lenny's Podcast website
- Lennybot
- LennyPodcast.com
- lennyspodcast.com
- Love Is Blind
- Medium
- Mercury
- Microsoft
- Microsoft Azure
- Monetizing Innovation
- Netflix
- Never Have I Ever
- New Blue Sun
- Ninja CREAMi
- Notion
- OneSchema
- OpenAI
- OpenAI Codex
- Outlive
- Perplexity
- Persona
- PHP
- Platform Engineering: A Guide for Technical, Product, and People Leaders
- Python
- Ruby
- Sanity
- Scaling Innovation
- Shopify
- Shrinking
- Sierra
- Simon-Kucher
- Slack
- SPACE
- SPACE Framework
- Spotify
- Stripe
- Substack
- Suits
- Superhuman
- Tabnine
- Technology Strategy Patterns
- Ted Lasso
- The Crux
- The Matrix
- The Phoenix Project
- The SPACE of Developer Productivity
- The Three-Body Problem
- The Undoing Project
- The Value Flywheel Effect
- The Wheel of Time
- TomTom
- Top Chef
- Uber
- What Got You Here Won't Get You There
- When Things Fall Apart
- WHOOP
- WorkOS
- Zendesk
Spot an error or want this page removed? Request a correction or removal.