Intermediate
Vocabulary
#dx
#space-framework
#developer-productivity
SPACE Framework Vocabulary
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 / 33 completed
1 / 33
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?
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 / 33
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?
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 / 33
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?
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 / 33
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?
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 / 33
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?
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."
6 / 33
HTTP/1.1 200 OK
The 'D' in SPACE stands for Developer Experience (DX). While delight, debugging, and discoverability are certainly aspects of good DX, the core concept is broader. The comment highlights a specific metric – Time to First Byte – which directly impacts developer productivity and satisfaction when dealing with API performance issues. It's crucial to remember that DX isn't just about individual feelings but the overall conditions affecting how developers work.
7 / 33
{code}
// API Response - High Latency
{
"status": "200",
"data": {
"user_profile": {
"name": "John Doe"
}
},
"responseTime": 1.5, // seconds
"timeToFirstByte": 800 // milliseconds
}
A developer is reviewing an API response and notes the high 'Time to First Byte' metric. They suggest investigating how this relates to the 'D' dimension of SPACE. What does the 'D' in SPACE stand for, and why is it relevant here?The 'D' in SPACE – Developer Diagnostics – is about understanding the *technical* challenges that developers are facing. High 'Time to First Byte' indicates a performance bottleneck related to the API response itself – it's not directly about developer happiness or satisfaction. This metric highlights a problem with the underlying code, infrastructure, or network configuration impacting the developer's ability to efficiently deliver the API request.
8 / 33
HTTP/1.1 200 OK
The 'D' in SPACE stands for Developer Experience (DX). While delight, debugging, and discoverability are certainly aspects of good DX, the core concept is broader. The comment highlights a specific metric – Time to First Byte – which directly impacts developer productivity and satisfaction when dealing with API performance issues. It's crucial to remember that DX isn't just about individual feelings but the overall conditions affecting how developers work.
9 / 33
{code}
// API Response - High Latency
{
"status": "200",
"data": {
"user_profile": {
"name": "John Doe"
}
},
"responseTime": 1.5, // seconds
"timeToFirstByte": 800 // milliseconds
}
A developer is reviewing an API response and notes the high 'Time to First Byte' metric. They suggest investigating how this relates to the 'D' dimension of SPACE. What does the 'D' in SPACE stand for, and why is it relevant here?The 'D' in SPACE – Developer Diagnostics – is about understanding the *technical* challenges that developers are facing. High 'Time to First Byte' indicates a performance bottleneck related to the API response itself – it's not directly about developer happiness or satisfaction. This metric highlights a problem with the underlying code, infrastructure, or network configuration impacting the developer's ability to efficiently deliver the API request.
10 / 33
HTTP/1.1 200 OK
The 'D' in SPACE stands for Developer Experience (DX). While delight, debugging, and discoverability are certainly aspects of good DX, the core concept is broader. The comment highlights a specific metric – Time to First Byte – which directly impacts developer productivity and satisfaction when dealing with API performance issues. It's crucial to remember that DX isn't just about individual feelings but the overall conditions affecting how developers work.
11 / 33
{code}
// API Response - High Latency
{
"status": "200",
"data": {
"user_profile": {
"name": "John Doe"
}
},
"responseTime": 1.5, // seconds
"timeToFirstByte": 800 // milliseconds
}
A developer is reviewing an API response and notes the high 'Time to First Byte' metric. They suggest investigating how this relates to the 'D' dimension of SPACE. What does the 'D' in SPACE stand for, and why is it relevant here?The 'D' in SPACE – Developer Diagnostics – is about understanding the *technical* challenges that developers are facing. High 'Time to First Byte' indicates a performance bottleneck related to the API response itself – it's not directly about developer happiness or satisfaction. This metric highlights a problem with the underlying code, infrastructure, or network configuration impacting the developer's ability to efficiently deliver the API request.
12 / 33
HTTP/1.1 200 OK
The 'D' in SPACE stands for Developer Experience (DX). While delight, debugging, and discoverability are certainly aspects of good DX, the core concept is broader. The comment highlights a specific metric – Time to First Byte – which directly impacts developer productivity and satisfaction when dealing with API performance issues. It's crucial to remember that DX isn't just about individual feelings but the overall conditions affecting how developers work.
13 / 33
{code}
// API Response - High Latency
{
"status": "200",
"data": {
"user_profile": {
"name": "John Doe"
}
},
"responseTime": 1.5, // seconds
"timeToFirstByte": 800 // milliseconds
}
A developer is reviewing an API response and notes the high 'Time to First Byte' metric. They suggest investigating how this relates to the 'D' dimension of SPACE. What does the 'D' in SPACE stand for, and why is it relevant here?The 'D' in SPACE – Developer Diagnostics – is about understanding the *technical* challenges that developers are facing. High 'Time to First Byte' indicates a performance bottleneck related to the API response itself – it's not directly about developer happiness or satisfaction. This metric highlights a problem with the underlying code, infrastructure, or network configuration impacting the developer's ability to efficiently deliver the API request.
14 / 33
During a daily standup, Sarah says: "I spent most of the last hour debugging this integration. The error logs were really difficult to decipher.". Which SPACE dimension is Sarah *most likely* referring to?
Sarah's statement explicitly focuses on her negative feelings—difficulty deciphering error logs. This directly relates to Satisfaction within the SPACE framework. Incorrect options focus on different aspects of developer experience; Flow is about ease and enjoyment, while Productivity is more about output rather than emotional state.
15 / 33
Mark, a DX engineer, is writing a PR description for a new automated testing pipeline. He writes: "We've reduced the number of manual deployments by 70% and decreased deployment failure rates to under 5%." Which SPACE dimension does Mark primarily highlight?
Mark focuses on the measurable improvements in deployment processes – reduced manual deployments and lower failure rates. This aligns directly with the Satisfaction dimension within SPACE, reflecting how developers feel about their work environment and tools. Options A and B relate to different aspects of efficiency/performance metrics but don't capture the subjective positive impact.
16 / 33
During a code review, David comments on an API endpoint: "The response time is consistently above 2 seconds. This is unacceptable for this level of service." Considering the SPACE framework, what aspect is David *primarily* concerned about?
David specifically mentions 'response time' and 'latency,' referencing 'Time to First Byte' which is a core metric used to measure API performance. This directly relates to the Performance dimension within SPACE – it's about how quickly systems respond. While frustration may be present, the comment centers on the quantifiable measurement.
17 / 33
A developer, Alex, is describing a recent project retrospective. He says: "We spent too much time in meetings discussing minor UI changes – it felt like we were getting bogged down in details and not focusing on the core functionality." Which SPACE dimension does Alex most strongly indicate needs attention?
Alex highlights the excessive time spent on minor UI changes in meetings. This directly relates to the Cognitive Load dimension within SPACE – it's about the mental effort developers expend on tasks, particularly unproductive ones. The other options represent different aspects of developer experience but don't capture this specific issue.
18 / 33
You're analyzing data from a new monitoring system and see a high number of 'unassigned' tickets in the backlog. The team reports feeling overwhelmed and lacking clarity on priorities. Which SPACE dimension is most impacted?
An unassigned backlog and a feeling of being overwhelmed strongly suggest that the Performance dimension is suffering. When developers don't have clear priorities or understand their tasks, it directly impacts their ability to efficiently complete work – this is what's measured within the performance metric.
19 / 33
During a daily standup, Sarah says: "I spent most of the last hour debugging this integration. The error logs were really difficult to decipher.". Which SPACE dimension is Sarah *most likely* referring to?
Sarah's statement explicitly focuses on her negative feelings—difficulty deciphering error logs. This directly relates to Satisfaction within the SPACE framework. Incorrect options focus on different aspects of developer experience; Flow is about ease and enjoyment, while Productivity is more about output rather than emotional state.
20 / 33
Mark, a DX engineer, is writing a PR description for a new automated testing pipeline. He writes: "We've reduced the number of manual deployments by 70% and decreased deployment failure rates to under 5%." Which SPACE dimension does Mark primarily highlight?
Mark focuses on the measurable improvements in deployment processes – reduced manual deployments and lower failure rates. This aligns directly with the Satisfaction dimension within SPACE, reflecting how developers feel about their work environment and tools. Options A and B relate to different aspects of efficiency/performance metrics but don't capture the subjective positive impact.
21 / 33
During a code review, David comments on an API endpoint: "The response time is consistently above 2 seconds. This is unacceptable for this level of service." Considering the SPACE framework, what aspect is David *primarily* concerned about?
David specifically mentions 'response time' and 'latency,' referencing 'Time to First Byte' which is a core metric used to measure API performance. This directly relates to the Performance dimension within SPACE – it's about how quickly systems respond. While frustration may be present, the comment centers on the quantifiable measurement.
22 / 33
A developer, Alex, is describing a recent project retrospective. He says: "We spent too much time in meetings discussing minor UI changes – it felt like we were getting bogged down in details and not focusing on the core functionality." Which SPACE dimension does Alex most strongly indicate needs attention?
Alex highlights the excessive time spent on minor UI changes in meetings. This directly relates to the Cognitive Load dimension within SPACE – it's about the mental effort developers expend on tasks, particularly unproductive ones. The other options represent different aspects of developer experience but don't capture this specific issue.
23 / 33
You're analyzing data from a new monitoring system and see a high number of 'unassigned' tickets in the backlog. The team reports feeling overwhelmed and lacking clarity on priorities. Which SPACE dimension is most impacted?
An unassigned backlog and a feeling of being overwhelmed strongly suggest that the Performance dimension is suffering. When developers don't have clear priorities or understand their tasks, it directly impacts their ability to efficiently complete work – this is what's measured within the performance metric.
24 / 33
During a daily standup, Sarah says: "I spent most of the last hour debugging this integration. The error logs were really difficult to decipher.". Which SPACE dimension is Sarah *most likely* referring to?
Sarah's statement explicitly focuses on her negative feelings—difficulty deciphering error logs. This directly relates to Satisfaction within the SPACE framework. Incorrect options focus on different aspects of developer experience; Flow is about ease and enjoyment, while Productivity is more about output rather than emotional state.
25 / 33
Mark, a DX engineer, is writing a PR description for a new automated testing pipeline. He writes: "We've reduced the number of manual deployments by 70% and decreased deployment failure rates to under 5%." Which SPACE dimension does Mark primarily highlight?
Mark focuses on the measurable improvements in deployment processes – reduced manual deployments and lower failure rates. This aligns directly with the Satisfaction dimension within SPACE, reflecting how developers feel about their work environment and tools. Options A and B relate to different aspects of efficiency/performance metrics but don't capture the subjective positive impact.
26 / 33
During a code review, David comments on an API endpoint: "The response time is consistently above 2 seconds. This is unacceptable for this level of service." Considering the SPACE framework, what aspect is David *primarily* concerned about?
David specifically mentions 'response time' and 'latency,' referencing 'Time to First Byte' which is a core metric used to measure API performance. This directly relates to the Performance dimension within SPACE – it's about how quickly systems respond. While frustration may be present, the comment centers on the quantifiable measurement.
27 / 33
A developer, Alex, is describing a recent project retrospective. He says: "We spent too much time in meetings discussing minor UI changes – it felt like we were getting bogged down in details and not focusing on the core functionality." Which SPACE dimension does Alex most strongly indicate needs attention?
Alex highlights the excessive time spent on minor UI changes in meetings. This directly relates to the Cognitive Load dimension within SPACE – it's about the mental effort developers expend on tasks, particularly unproductive ones. The other options represent different aspects of developer experience but don't capture this specific issue.
28 / 33
You're analyzing data from a new monitoring system and see a high number of 'unassigned' tickets in the backlog. The team reports feeling overwhelmed and lacking clarity on priorities. Which SPACE dimension is most impacted?
An unassigned backlog and a feeling of being overwhelmed strongly suggest that the Performance dimension is suffering. When developers don't have clear priorities or understand their tasks, it directly impacts their ability to efficiently complete work – this is what's measured within the performance metric.
29 / 33
During a daily standup, Sarah says: "I spent most of the last hour debugging this integration. The error logs were really difficult to decipher.". Which SPACE dimension is Sarah *most likely* referring to?
Sarah's statement explicitly focuses on her negative feelings—difficulty deciphering error logs. This directly relates to Satisfaction within the SPACE framework. Incorrect options focus on different aspects of developer experience; Flow is about ease and enjoyment, while Productivity is more about output rather than emotional state.
30 / 33
Mark, a DX engineer, is writing a PR description for a new automated testing pipeline. He writes: "We've reduced the number of manual deployments by 70% and decreased deployment failure rates to under 5%." Which SPACE dimension does Mark primarily highlight?
Mark focuses on the measurable improvements in deployment processes – reduced manual deployments and lower failure rates. This aligns directly with the Satisfaction dimension within SPACE, reflecting how developers feel about their work environment and tools. Options A and B relate to different aspects of efficiency/performance metrics but don't capture the subjective positive impact.
31 / 33
During a code review, David comments on an API endpoint: "The response time is consistently above 2 seconds. This is unacceptable for this level of service." Considering the SPACE framework, what aspect is David *primarily* concerned about?
David specifically mentions 'response time' and 'latency,' referencing 'Time to First Byte' which is a core metric used to measure API performance. This directly relates to the Performance dimension within SPACE – it's about how quickly systems respond. While frustration may be present, the comment centers on the quantifiable measurement.
32 / 33
A developer, Alex, is describing a recent project retrospective. He says: "We spent too much time in meetings discussing minor UI changes – it felt like we were getting bogged down in details and not focusing on the core functionality." Which SPACE dimension does Alex most strongly indicate needs attention?
Alex highlights the excessive time spent on minor UI changes in meetings. This directly relates to the Cognitive Load dimension within SPACE – it's about the mental effort developers expend on tasks, particularly unproductive ones. The other options represent different aspects of developer experience but don't capture this specific issue.
33 / 33
You're analyzing data from a new monitoring system and see a high number of 'unassigned' tickets in the backlog. The team reports feeling overwhelmed and lacking clarity on priorities. Which SPACE dimension is most impacted?
An unassigned backlog and a feeling of being overwhelmed strongly suggest that the Performance dimension is suffering. When developers don't have clear priorities or understand their tasks, it directly impacts their ability to efficiently complete work – this is what's measured within the performance metric.
Frequently Asked Questions
What does the "SPACE Framework Vocabulary" exercise practise?
Practice the vocabulary of the SPACE framework: Satisfaction, Performance, Activity, Communication, and Efficiency — and how to discuss each dimension with engineering leadership.
How many questions are in this exercise?
This exercise has 33 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Developer Experience Metrics category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "SPACE Framework Vocabulary" part of a larger series?
Yes — it's one exercise in the Developer Experience Metrics category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Developer Experience Metrics category page for related exercises, or browse the main Exercises hub for other IT English topics.