Apply the SPACE framework, measure DORA metrics, identify friction points, reduce cognitive load with platform engineering, and design developer surveys.
0 / 5 completed
1 / 5
What does the SPACE framework measure and what does each letter stand for?
SPACE framework: proposed by GitHub and Microsoft researchers, it addresses the limitation of single-metric productivity measurement (e.g. lines of code or commits/day). Satisfaction captures burnout and engagement; Activity measures outputs like PRs and deployments; Efficiency captures wait times and interruptions. Using all five dimensions avoids perverse incentives from optimising one metric.
2 / 5
What are the four DORA metrics and what do they measure?
DORA metrics: from the State of DevOps research (Google/DORA). High performers deploy multiple times per day (DF), take less than one day from commit to production (LT), have a change failure rate < 5%, and restore service within one hour (MTTR). These four metrics correlate with organisational performance and can be derived from CI/CD pipeline data.
3 / 5
What is a friction point in developer experience measurement?
Friction points: examples include waiting 45 minutes for CI to complete, needing 3 approvals for a one-line change, or a dev environment that takes an hour to set up. DX platforms (Cortex, Port) track these by measuring tool usage, pipeline durations, and PR cycle times, surfacing which friction points impact the most engineers.
4 / 5
What is cognitive load in developer experience and how do platform teams reduce it?
Cognitive load: when developers must understand Kubernetes YAML, Terraform, observability tooling, and CI/CD configuration to ship a feature, cognitive load is high. Platform engineering reduces this by providing pre-configured service templates, self-service environment provisioning, and curated observability dashboards — so developers focus on product logic.
5 / 5
What role do developer surveys play in DX measurement and what is their limitation?
Developer surveys: tools like the DXKPI survey (derived from the SPACE framework) ask developers to rate satisfaction with their tools, environment, and processes. Combined with objective telemetry (CI duration, PR cycle time), surveys triangulate the human experience behind the numbers. Purely survey-based DX programmes miss systemic issues that developers have normalised.