5 exercises — vocabulary for designing, running, and presenting developer experience surveys, including eNPS, Likert scales, friction points, and journey mapping.
DX survey vocabulary at a glance
eNPS — Employee Net Promoter Score (−100 to +100)
Likert scale — ordered 5- or 7-point response options
Friction point — a step causing unnecessary delay or frustration
Developer journey map — visual workflow from idea to production
Cognitive load — mental effort to navigate systems and processes
0 / 5 completed
1 / 5
A DX lead reports in an all-hands: "Our eNPS dropped 12 points this quarter — down from +32 to +20. That's still in the positive range, but the downward trend is a signal we can't ignore." What is eNPS (Employee Net Promoter Score) and how is it calculated?
eNPS (Employee Net Promoter Score) is the internal adaptation of NPS for measuring employee loyalty and satisfaction. The key question: "On a scale of 0–10, how likely are you to recommend this company as a great place to work?" Scoring: 9–10 = Promoters, 7–8 = Passives (ignored), 0–6 = Detractors. Formula: eNPS = % Promoters − % Detractors. Range: −100 (all detractors) to +100 (all promoters). Benchmarks: below 0 is poor, 0–30 is acceptable, 30–70 is good, above 70 is excellent. In the example, a drop from +32 to +20 in a single quarter is significant. Presentation language: "Our eNPS dropped 12 points this quarter — we ran qualitative follow-up interviews and identified tooling reliability as the primary driver."
2 / 5
A developer experience researcher explains their survey design: "We use a Likert scale rather than free text for most questions because it gives us data we can trend over time — but we always include open-ended follow-ups to understand the 'why'." What is a Likert scale in the context of DX surveys?
A Likert scale (named after psychologist Rensis Likert, pronounced "LICK-ert") presents a statement and asks respondents to choose from ordered options: Strongly Disagree / Disagree / Neutral / Agree / Strongly Agree (5-point) or with additional gradations (7-point). In DX surveys, example questions: "I have the tools I need to do my work effectively" or "I can complete a feature without waiting on other teams." Why Likert scales are preferred for DX: they produce quantitative data that can be tracked over time, compared across teams, and correlated with business outcomes. Limitation: they capture what developers say, not what they do — always pair with behavioural data. Key vocabulary: response options, ordinal data, trend analysis, benchmark comparison, statistical significance.
3 / 5
In a DX survey analysis session, a researcher says: "The highest-rated friction point this quarter was the local development environment setup — 68% of developers called it a significant obstacle to their daily work." What is a friction point in developer experience vocabulary?
Friction point is a UX concept applied to the developer experience: any place in the developer's workflow where unnecessary effort, waiting, confusion, or frustration occurs. Identifying friction points is the core purpose of DX surveys. Common categories: tooling friction (slow builds, broken local environments), process friction (excessive approval gates, unclear ownership), knowledge friction (missing documentation, tribal knowledge silos), social friction (PR review delays, unclear code review expectations). Presentation language: "We've mapped seven friction points in the feature delivery workflow — the top three account for 80% of the delay." Related concept: developer journey mapping — creating a visual representation of every step a developer takes from idea to production, marking friction points along the way.
4 / 5
A DX programme manager introduces a new initiative: "This quarter we're running a developer journey mapping workshop — we want to walk through the entire experience from onboarding to first production deployment and identify where developers get stuck." What is developer journey mapping and where does the concept come from?
Developer journey mapping is adapted from customer journey mapping — a UX research tool that documents every touchpoint a user has with a product or service. Applied to developer experience, it maps the steps a developer takes across key workflows (onboarding, daily coding, PR process, deployment, on-call). Each step captures: what the developer does, what tools they use, how they feel, and what pain points arise. Output: a visual map that makes invisible friction visible to leadership. Key phases in a typical developer journey: onboarding → local dev setup → feature development → code review → CI/CD → production monitoring → incident response. Facilitation language: "Let's walk through the journey from branch creation to merge and note every point where someone had to wait, ask for help, or work around a broken tool."
5 / 5
A DX lead presents quarterly survey results: "The survey data shows high cognitive load scores — developers report that understanding how to deploy a service requires knowing at least six different systems." What does cognitive load mean in a DX survey context?
Cognitive load (from educational psychology, originally described by John Sweller) refers to the mental effort required to process and work with information. In DX, high cognitive load means developers must hold too many complex, interconnected pieces of information in working memory — architecture decisions, tool quirks, process exceptions, undocumented behaviours — just to complete routine tasks. This causes errors, slowdowns, and exhaustion. DX survey questions that measure cognitive load: "I understand how to deploy a service without asking for help", "Our systems are easy to reason about", "I can make changes confidently without fear of breaking something I don't know about." Presentation language: "Our cognitive load scores indicate our internal platform is too complex — developers need a simpler, paved-road deployment path."