5 exercises — the language of the SPACE framework and how to use each dimension in conversations with engineering leadership.
SPACE at a glance
S — Satisfaction and well-being
P — Performance (outcomes delivered)
A — Activity (volume of actions)
C — Communication and collaboration
E — Efficiency and flow
0 / 5 completed
1 / 5
An engineering manager says: "According to the SPACE framework, we can't just count commits or tickets closed — we need to look at Satisfaction alongside performance indicators." What does the S in SPACE stand for, and why is it included?
S = Satisfaction and well-being in the SPACE framework (Forsgren et al., 2021). It captures how developers feel about their work, tools, and environment — measured through surveys and questions like "Would you recommend this team as a great place to work?" Satisfaction correlates strongly with productivity and retention; a team that is burned out or frustrated will underperform on every other metric. Common measures: developer satisfaction score, eNPS, perceived productivity rating, onboarding experience rating. Key phrase in conversations: "Our satisfaction scores dropped 8 points this quarter — that's a leading indicator of attrition."
2 / 5
A DX lead presents to the CTO: "We measure onboarding time as a proxy for the E dimension of SPACE — it tells us how much friction new developers face before they're productive." What does the E in SPACE stand for?
E = Efficiency and flow. This dimension captures how smoothly developers can move through their work without unnecessary delays, interruptions, or process friction. Onboarding time — the number of days until a new hire ships their first change — is a classic efficiency metric because it exposes friction in the development environment, documentation, and tooling. Other efficiency metrics: build time, PR review wait time, CI pipeline duration, number of manual approval steps. In conversation: "Our onboarding time increased from 3 days to 12 days after the security policy change — we need to automate that compliance step."
3 / 5
During a quarterly review, a platform engineer says: "Our perceived productivity scores are high, but the A dimension shows developers are spending 40% of their time on manual release tasks instead of feature work." What does the A in SPACE stand for?
A = Activity. Activity captures the volume of actions in the development process — commits, pull requests opened and reviewed, CI runs triggered, incidents handled, documentation updated. Importantly, SPACE cautions that activity metrics should never be used in isolation: high commit counts do not equal high value. The example in the question illustrates a common finding — perceived productivity (S dimension) can be high while activity analysis (A) reveals significant toil. Activity metrics are best used as diagnostics, not performance targets. In conversation: "Activity data shows the team is shipping — but most of that activity is rework, not new value."
4 / 5
A developer experience researcher explains: "The C dimension in SPACE is often overlooked — it's not just about meetings, it's about whether developers can get answers quickly and contribute to decisions." What does the C in SPACE stand for?
C = Communication and collaboration. This dimension looks at how well developers share knowledge, get help when blocked, participate in code reviews, and contribute to cross-team decisions. Poor collaboration shows up as long review wait times, knowledge silos, and developers who feel excluded from architectural decisions. Measures include: PR review turnaround, documentation contribution, cross-team dependency resolution time, and qualitative survey questions like "Can you easily get a code review from another team?". In presentation language: "The C dimension data shows our platform team is a bottleneck — 67% of developers wait more than two days for cross-team input."
5 / 5
An engineering director summarises a DX initiative: "Before we invest in a new CI system, let's baseline all five SPACE dimensions so we can show P improvements to the board." What does the P in SPACE stand for, and what metrics typically represent it?
P = Performance. This dimension focuses on the outcomes of work rather than the effort. Did the work delivered actually provide value? Performance metrics include: change failure rate, mean time to recovery (MTTR), customer-reported defect rate, feature adoption rate, and reliability. SPACE explicitly distinguishes performance from activity — a team can be very busy (high A) while delivering poor outcomes (low P). When presenting to a board or CTO, performance metrics answer: "Is developer investment producing business value?" Example: "After the DX programme, our change failure rate dropped from 12% to 4%, and release frequency tripled — that's the P dimension improving."