DORA vs SPACE: two lenses on software delivery

What DORA measures

DORA refers to the DevOps Research and Assessment program, whose multi-year research (popularized in the book Accelerate by Nicole Forsgren, Jez Humble, and Gene Kim) identified a small set of metrics that correlate with software delivery performance. These are commonly called the four keys. Two describe throughput and two describe stability, and the pairing is deliberate: measuring speed without stability rewards recklessness.

The four keys are deployment frequency, lead time for changes, change failure rate, and failed deployment recovery time (often discussed as time to restore service). Together they give a compact, team-comparable read on delivery health. Their strength is focus — they are outcome metrics about the delivery system, not measures of individual output — and they should never be used to rank individuals.

• Deployment frequency: how often the team successfully releases to production.
• Lead time for changes: time from code committed to code running in production.
• Change failure rate: the share of deployments that cause a failure needing remediation.
• Failed deployment recovery time: how long it takes to restore service after a failed change.

What SPACE measures

SPACE is a framework introduced in 2021 (Forsgren, Storey, Maddila, Zimmermann, Houck, and Butler) to counter the habit of reducing developer productivity to a single dimension like lines of code or deploy count. Its central argument is that productivity is multidimensional and must be captured across several categories at once, using a mix of perceptual (survey) and system data.

SPACE is an acronym for five dimensions: Satisfaction and well-being, Performance, Activity, Communication and collaboration, and Efficiency and flow. It is a framework for choosing metrics, not a fixed list — the guidance is to pick a few metrics spanning multiple dimensions, and specifically to avoid relying on a single metric or on activity counts alone.

• Satisfaction and well-being: how fulfilled, healthy, and unburned-out developers are.
• Performance: outcomes of the work, such as quality and reliability, rather than raw output.
• Activity: counts of actions like commits or deployments — useful but easy to misuse in isolation.
• Communication and collaboration: how well people and teams discover information and work together.
• Efficiency and flow: the ability to make progress with minimal interruptions and handoffs.

Why they are complementary, not competing

The two frameworks operate at different altitudes. DORA is a focused set of outcome metrics for the delivery pipeline; SPACE is a way of thinking that insists you look across several dimensions of productivity so you do not optimize one at the expense of others. They fit together cleanly: DORA's four keys map naturally into SPACE's Performance and Efficiency and flow dimensions, while SPACE reminds you to also look at satisfaction, collaboration, and activity so a delivery number is never read in isolation.

Read alone, either can mislead. Excellent DORA numbers can coexist with an exhausted, attrition-prone team — a gap SPACE's satisfaction dimension is designed to catch. Conversely, SPACE without concrete delivery metrics can become abstract. Using them together keeps the picture both grounded and humane: measurable delivery outcomes, framed by the wider system that produced them.

When to use which

Reach for DORA first when you want a compact, defensible read on delivery health that teams can compare and track over time — for example, when an engineering leader or board wants to know whether delivery is improving. The four keys are well understood, relatively cheap to instrument from delivery telemetry, and hard to argue with as outcome measures.

Reach for SPACE when the question is broader than delivery speed: whether a productivity initiative is helping or quietly burning people out, why a team with good delivery numbers still feels stuck, or how to pick a balanced metric set without gaming a single number. SPACE typically requires survey data alongside system data, which is more effort but captures things telemetry cannot.

• Use DORA for delivery-health tracking, before-and-after comparisons of delivery changes, and executive reporting on flow and stability.
• Use SPACE to design a balanced metric set, to include developer sentiment, and to guard against optimizing one dimension at another's expense.
• Use both when you want grounded delivery outcomes framed by the wider system — the common posture for mature engineering organizations.
• In every case, keep measurement at the team-and-system level; neither framework is intended to rank or evaluate individuals.

Common misuses to avoid

Both frameworks are frequently misapplied in the same way: turned into individual scorecards. DORA's authors are explicit that the four keys describe the delivery system, and SPACE explicitly warns against relying on a single metric or on activity counts alone. Using either to compare developers against each other produces gaming and erodes trust while telling you little about actual performance.

The other common error is treating activity as achievement — counting commits or deployments as if volume were value. SPACE's Activity dimension is included precisely because it is necessary but insufficient, and must be balanced by outcome and perceptual measures. Whichever framework you adopt, pair throughput signals with quality, stability, and human signals so the numbers stay honest.

Frequently asked questions