Skip to lesson
Exit
CI/CD, release engineering & the toolchain1 / 3

1 min lesson

DORA and constraint thinking: argue on their scoreboard

Give a plain answer to "Why must you never quote a Cursor-driven DORA speed gain without its stability companion?" Then ground it in one lesson detail.

Step 1 of 3

You don't win a platform team by inventing a new metric. You win by arguing on the scoreboard they already keep and for most engineering orgs that scoreboard is DORADORA metrics. Four widely-used delivery measures: deployment frequency, lead time for changes, change failure rate and time to restore service. Press Enter for the full definition.. Learn it well enough to coach with it, not just recite it.

The four DORA metrics - speed and stability, always paired

Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.

diagram: dora

Deployment frequency and lead time for changes measure throughput. Change failure rate and failed-deployment recovery time (formerly MTTR) measure stability. The whole point is that elite teams move fast AND stay stable. Never quote a speed gain without its stability companion.