What is the SPACE framework?
Updated
The SPACE framework is a model for measuring developer productivity across five dimensions: Satisfaction and well-being, Performance, Activity, Communication and collaboration, and Efficiency and flow. Introduced in 2021, it argues that productivity is multidimensional and cannot be captured by any single number such as lines of code, commits, or story points.
SPACE was published by researchers including Nicole Forsgren in the article The SPACE of Developer Productivity (ACM Queue, 2021). Its central guidance is to measure across at least three of the five dimensions at once, so that a gain in one area (raw activity) is not mistaken for real progress while another (developer well-being or quality) quietly degrades.
The five dimensions of SPACE
SPACE is an acronym for five categories of developer productivity. The framework does not prescribe specific metrics; it provides the dimensions and asks teams to choose measures that fit their context. The point is coverage across dimensions, not a fixed scorecard.
| Dimension | What it captures | Example signals |
|---|---|---|
| Satisfaction and well-being | How fulfilled and healthy developers feel about work, team, and tools | Developer satisfaction surveys, retention, burnout indicators |
| Performance | The outcome or quality of work, not the volume | Change quality, reliability, customer or business impact |
| Activity | Counts of actions and outputs produced | Commits, pull requests, deployments, code reviews completed |
| Communication and collaboration | How well people and work connect across the team | Review turnaround, discoverability of docs, onboarding time |
| Efficiency and flow | The ability to make progress with minimal interruption or delay | Handoff delays, wait times, uninterrupted focus time |
Why SPACE exists: single metrics mislead
SPACE was written as a corrective to productivity measurement that leans on one convenient number. Counting lines of code rewards verbosity; counting commits rewards fragmentation; counting hours rewards presence over output. Any single metric is easy to game and tends to optimize the wrong behavior once people know it is being watched.
The framework's answer is triangulation. Because the five dimensions can pull against each other — pushing activity up can push satisfaction and quality down — looking at several at once reveals trade-offs a single metric hides. A healthy read shows movement in the same direction across dimensions, not one dial spun while the others slip.
How to use SPACE in practice
The framework offers a few working rules. Measure across dimensions, not within one: pick metrics from at least three of the five categories. Combine perceptual data (surveys about satisfaction and flow) with system data (activity and performance signals), because each catches what the other misses. And measure at the level of the team or system, not to rank individuals — using SPACE to compare individual developers is a well-known misuse that erodes trust and the data itself.
SPACE is deliberately not a benchmark. It does not ship target numbers or elite tiers. It is a lens for choosing a balanced set of measures, which is why many teams pair it with an outcome-focused framework such as DORA for delivery performance and use SPACE to keep the human and quality dimensions in view.
SPACE vs DORA
SPACE and DORA are complementary, not competing. DORA measures software delivery performance through four outcome metrics — deployment frequency, lead time for changes, change failure rate, and time to restore service. SPACE is broader and more diagnostic: it spans satisfaction, collaboration, and flow that DORA does not attempt to capture.
A common pattern is to use DORA to answer how the delivery system performs and SPACE to understand why — whether slow lead time is a flow problem, a collaboration bottleneck, or a well-being issue. DORA's delivery metrics fit naturally inside the Performance and Activity dimensions of SPACE, so the two are frequently used together rather than as alternatives.
Frequently asked questions
Who created the SPACE framework?
SPACE was introduced in the article The SPACE of Developer Productivity, published in ACM Queue in 2021 by a group of researchers including Nicole Forsgren, Margaret-Anne Storey, Chandra Maddila, Thomas Zimmermann, Brian Houck, and Jenna Butler. It draws on both software-engineering research and organizational psychology.
How is SPACE different from DORA metrics?
DORA measures software delivery performance through four outcome metrics. SPACE is a broader model covering five dimensions — satisfaction and well-being, performance, activity, communication and collaboration, and efficiency and flow. DORA fits inside SPACE's performance and activity dimensions; SPACE adds the human, collaboration, and flow dimensions DORA does not measure.
Do you have to measure all five SPACE dimensions?
No. The framework's guidance is to measure across at least three of the five dimensions rather than relying on one, and to combine perceptual data (surveys) with system data. The goal is a balanced view that reveals trade-offs, not a complete scorecard of every dimension at once.
Published by ShipReady Metrics, an evidence-based technology and compliance intelligence platform. This guide is educational and vendor-neutral.