Once a survey clears the anonymity threshold, its results unlock under the Insights tab of the Surveys page. DevPerform goes beyond raw averages to help you find what to actually do.
A single survey’s results page is split into two tabs: Overview (the Experience Index, follow-through from the previous wave, focus-area triage, per-dimension scores, the team heatmap, and the experience-vs-delivery drivers) and Questions (every question’s full results, filterable by question set — DX Core 4, Engagement, AI Impact, eNPS). Use the team filter to scope either tab to one team.
Engagement scorecard
A Full Engagement survey is shown as a scorecard — the whole instrument on one page:
- Overall engagement — a single 0–100 score, with the change since your previous wave.
- Every dimension — Manager, Growth, Recognition, Enablement, Wellbeing, Belonging, and Engagement — each with its score, a bar, and the wave-over-wave change.
Use the Team selector to scope the entire scorecard (overall, dimensions, drivers, and comparison) to a single team. A team’s scores stay hidden until it clears the anonymity threshold on its own.
Key drivers
Driver analysis finds which dimensions most correlate with engagement across respondents — the levers that actually move it. A dimension with high impact but a low score is flagged as a focus area: high leverage, currently weak. Click any dimension to drill into which of its questions are doing the driving, so you go from “Growth is dragging engagement” to the specific item behind it.
Key-driver analysis is a correlation, so it needs a few responses to be meaningful — it stays hidden until a survey has enough.
Compare over time
Pick any two administrations to compare (this quarter vs. last, H1 vs. H2, year over year) and the overall and per-dimension deltas update to that baseline. An overall-engagement trend line plots every wave so you can see the trajectory at a glance.
DX Index
For DX-style surveys (DX Core 4 and other Likert templates), responses roll up into a single trackable DX Index — one number you can watch over time, rather than juggling a dozen question scores.
Compare across teams and time
The Insights explorer lets you trend any single metric — Engagement / DX Index, eNPS, or response rate — over time, with one line per team plus a company-wide overall, and a current-period bar comparison across teams. Pick the metric, the teams, and a date range.
Per-survey heatmap
For a single survey, the heatmap shows scores by question across teams, so you can spot at a glance which group is struggling with which dimension. It respects the anonymity threshold per cell — small segments stay hidden.
Delivery driver analysis
Beyond the in-survey key drivers above, DevPerform can correlate survey sentiment with your actual delivery telemetry — connecting, for example, low scores with measured cycle-time or review-pickup data. This is unique to having both datasets in one place: it ties how the team feels to how it’s delivering.
Saved views
Save a metric + team + filter combination as a named view, shared across your account’s admins — so “Engagement by Platform team” or “eNPS, last quarter” is one click away for everyone.
Anonymity, everywhere
Every scored view — the scorecard, dimensions, drivers, comparisons, heatmap cells, and trends — enforces the minimum-response threshold. If a segment is too small to be anonymous, its numbers are withheld rather than shown. (Response rate, a participation count rather than an answer, is always available.)
The Experience Index
Every survey’s likert questions roll up into a single Experience Index (0–100): each 1–5 question is averaged across respondents, those averages are averaged, and the result rescales to 0–100. eNPS, free-text, and quantitative bucket questions never feed it. The results page shows the index with a trend against your previous survey wave (waves suppressed by the anonymity threshold are skipped, never leaked), per-team indices under the same thresholds, and a “how is this computed?” breakdown — one number is a conversation starter, not a verdict.
Where a survey includes eNPS, results show the standard interpretation bands (above 0 good, above 20 favorable, above 50 excellent, above 80 world class — the Bain & Company thresholds as published by Qualtrics; the UI notes this is the general NPS scale, not an engineering-specific benchmark).
Focus areas — closing the loop
Admins can triage each survey dimension right on the results: mark it Focus, Watching, or No action, with a short note (“pairing rotation starts next sprint”). Statuses and notes are visible to the whole team — the point is that everyone sees leadership responded, which is what keeps response rates healthy.
Marking a dimension as Focus offers one-click goal creation: a real goal targeting that survey dimension (e.g. “Ease of delivery above 69/100”) that evaluates automatically against each new survey wave.
When your next survey closes, its results open with follow-through receipts: the previous wave’s Focus and Watching areas with their score deltas — commitment, then evidence. Dimensions suppressed by the anonymity threshold can’t be triaged and never appear in comparisons. 
