SPACE Metrics
Measure developer productivity across all five SPACE dimensions — Satisfaction, Performance, Activity, Communication, and Efficiency.
What is SPACE?
SPACE is a developer productivity framework developed by researchers at Microsoft Research and GitHub. It stands for:
| Dimension | What it measures |
|---|---|
| Satisfaction | Developer experience and well-being — are developers happy and productive? |
| Performance | Outcomes and DORA metrics — is the team delivering reliably? |
| Activity | Volume of work — commits, PRs, reviews per day normalized to baseline |
| Communication | Review depth and responsiveness — are teams collaborating effectively? |
| Efficiency | Speed — inverse of cycle time; lower cycle time = higher efficiency |
A core principle of SPACE is that no single metric tells the whole story. Optimizing one dimension at the expense of others (e.g., high activity but low satisfaction) creates unhealthy dynamics. The radar chart helps you see the full picture at a glance.
How Koalr computes each dimension
Satisfaction (0–100)
Derived from Well-Being check-in scores, normalized to 0–100. Requires at least 14 days of check-in data to appear. Falls back to a neutral 50 if no well-being data is available.
Performance (0–100)
DORA composite score:
- Deployment frequency → normalized against elite benchmark (multiple times/day = 100)
- Lead time for changes → normalized against elite benchmark (< 1 hour = 100)
- Mean time to restore → normalized against elite benchmark (< 1 hour = 100)
Change failure rate is inverted (lower failure rate = higher score).
Activity (0–100)
Commits + PRs opened per day, normalized against a 30-day rolling baseline. The baseline is your team's own average, not an industry benchmark — this prevents penalizing smaller or infrastructure-focused teams.
Communication (0–100)
Composite of:
- Review depth — average comments per PR (higher is better, capped at a ceiling to prevent noise)
- Responsiveness — inverse of time-to-first-review (faster = higher)
Efficiency (0–100)
Inverse of normalized PR cycle time. Cycle time is measured from first commit to merge. Lower cycle time = higher efficiency score.
Reading the dashboard
SPACE Radar Chart
The radar chart shows all five dimensions as a pentagon. A balanced, large pentagon indicates healthy overall productivity. A lopsided shape reveals where to focus improvement.
Ideal shape: Large and symmetric. Warning signs:
- Tiny Satisfaction → burnout risk, investigate with Well-Being
- Tiny Performance → DORA metrics lagging, check DORA
- Tiny Efficiency → cycle time bottleneck, see Cycle Time Bottleneck
Dimension cards
Each dimension card shows:
- Current score (0–100) with color coding: 🟢 ≥ 80, 🟡 40–79, 🔴 < 40
- 30-day trend sparkline
- The primary underlying metric
Trend chart
The 30-day trend line shows the aggregate SPACE score over time. Declining trends warrant a retrospective conversation.
Time ranges
Select 7, 30, or 90 days. The 90-day view smooths short-term noise and is recommended for quarterly reviews.
SPACE vs DORA
DORA metrics (Deploy Frequency, Lead Time, CFR, MTTR) map directly into the Performance dimension of SPACE. SPACE adds the human factors (Satisfaction, Communication) and volume signal (Activity) that DORA intentionally excludes.
Use DORA for release engineering decisions and SPACE for holistic team health conversations.