Span DX Surveys: Complete Guide

Overview

Span DX (Developer Experience) Surveys are comprehensive, research-backed tools designed to measure and improve developer experience within your engineering organization. They help you systematically collect developer feedback across predefined and custom dimensions that impact software engineering productivity and satisfaction.

What Are DX Surveys?

Key Benefits

• Structured Measurement: Assess developer experience using industry-aligned frameworks with 16+ predefined themes

• Actionable Insights: Transform survey responses into prioritized improvement areas through built-in voting mechanisms

• Benchmarking: Compare results against Q4 2024 industry benchmarks

• Integration: Connect survey feedback directly to Span's broader dev analytics platform

• Executive Summaries: AI-powered automatic summarization of findings with priority highlights

DX Surveys vs. Pulse Surveys

Creating a DX Survey

Step 1: Settings

• Define your survey name

• Select survey type (DX Survey)

• Choose anonymity level:

  • Non-Anonymous: Track responses by individual

  • Confidential: Hide individual identifiers while maintaining data analysis

Step 2: Questions & Themes

Predefined Themes (16+ available with industry benchmarks):

Question Types Supported:

1. Sentiment/Rating Questions - 5-point scales with 7 rating types:

   • Agreement (Strongly Disagree → Strongly Agree)

   • Satisfaction (Very Dissatisfied → Very Satisfied)

   • Quality (Very Poor → Very Good)

   • Ease (Very Difficult → Very Easy)

   • Frequency (None of the Time → All of the Time)

   • Amount (Not at All → A Lot)

   • Enthusiasm (Not Enthusiastic → Very Enthusiastic)

2. Free Text Questions - Open-ended responses for detailed feedback

3. Multiple Choice Questions - Single or multi-select options

Custom Questions: Create organization-specific questions and themes beyond the predefined library.

Step 3: Priority Voting

Configure how participants identify top improvement areas:

• Disabled: No voting

• Pick 1-3: Flexible selection (1 to 3 priorities)

• Pick 3: Mandatory selection of exactly 3 priorities

This voting mechanism ensures you focus on the highest-impact improvements based on team consensus.

Step 4: Participants

Select participants using:

• Team/org structure filters

• Individual selection

• Custom criteria

Smart Exclusions:

• Exclude people recently surveyed (configurable days)

• Exclude specific individuals

• Set participant limits with randomization

Step 5: Communications

Launch Message:

• Customizable subject and body

• Available placeholders: [Company Name], [Employee First Name], [Survey Name], [Survey Button], [Close Date]

• Distribution via Email + Slack

Reminders (optional):

• First Reminder: Customize timing and message (e.g., mid-survey window)

• Final Reminder: Last chance notification (e.g., 1-2 days before close)

Close Date: Set survey end date (typically 1-2 weeks)

Step 6: Confirm & Launch

Review all settings and launch immediately or save as draft for later.

Survey Lifecycle

Draft → Live → Closed → Archived

• Draft: Fully editable, not accepting responses

• Live: Actively collecting responses; can add participants or send reminders

• Closed: No longer accepting responses; results available

• Archived: Historical record

Taking a Survey (Respondent Experience)

Multi-Page Interface:

Page 1 - Ratings

• Theme-organized sentiment questions

• 5-point rating scales with clear labels

• Optional comment fields for context

Page 2 - Priority Voting

• Select which areas need most improvement

• Enforces configured vote count (1-3 or exactly 3)

• Optional comments per selection

Page 3 - Additional Questions

• Free text responses

• Multiple choice selections

Features:

• Auto-save as you progress

• Progress indicators

• Mobile-responsive design

• Clear submission confirmation

Analyzing Results

Summary Dashboard

• Overall completion and participation rates

• Positive/neutral/negative sentiment breakdown

• Top priority areas identified by voting

• Favorable themes and low-scoring areas

Heatmap Visualization

Cross-tabulate responses by:

• Team

• Manager

• Job Level

• Tenure

• Custom Fields

Interactive drill-down enables deeper pattern discovery.

Question-Level Analytics

• Sentiment distribution (positive/neutral/negative %)

• Total responses per question

• Comments and feedback

• Comparison to previous surveys and industry benchmarks

Comments & Feedback

• Aggregated comments by theme

• AI-powered summarization of comment themes

• Privacy-respecting visibility controls

AI-Generated Insights

Automatic generation of:

• Executive summary of key findings

• Top 3 priority areas by vote

• Top 3 themes with highest positive sentiment

• Top 3 themes with lowest sentiment

• Comment theme summarization

Best Practices

Survey Design

✅ Keep focused: 10-20 questions for balanced coverage without fatigue

✅ Choose relevant themes: Select 4-6 themes matching your org's current priorities

✅ Enable priority voting: Always configure voting to identify high-impact areas

Participant Selection

✅ Include all engineers: Don't exclude key teams or levels

✅ Avoid survey fatigue: Use exclusion filters for recently surveyed participants ✅ Enable segmentation: Use custom fields for post-hoc analysis

Communication

✅ Personalize messages: Customize beyond generic templates

✅ Set realistic timelines: 1-2 weeks typical

✅ Plan reminder cadence: Mid-survey (3-5 days) + Final (1-2 days before close)

✅ Use Slack impersonation: Send from trusted leaders for better engagement

Results & Action

✅ Review multiple perspectives: Check summary, heatmap, and comments

✅ Focus on priority voting: Those areas reflect respondent consensus

✅ Benchmark: Compare to previous surveys and industry data

✅ Close formally: Don't leave surveys "live" indefinitely

Timing & Cadence

✅ Quarterly cadence: Comprehensive DX surveys every quarter

✅ Avoid clustering: Don't run multiple concurrent surveys

✅ Post-initiative timing: Launch 2-4 weeks after major changes

✅ Align with planning: Tie survey cycles to quarterly planning

Integration with Span Platform

Metrics Available

• Survey completion and participation rates

• Sentiment metrics (positive/neutral/negative %)

• Priority voting metrics

• Comment count metrics

• Response metrics per question

Organizational Data

• Linked to Span's people directory

• Uses org structure for filtering and heatmaps

• Custom people tags enable advanced segmentation

• Respects team hierarchy in visualizations

Data Export

• CSV export of all responses

• Report generation for external sharing

• API access to survey data

When to Use DX Surveys

Ideal Use Cases:

• ✅ Comprehensive developer experience assessment

• ✅ Baseline measurement for improvement initiatives

• ✅ Cross-team comparison and benchmarking

• ✅ Board/executive reporting on engineering health

• ✅ Identifying systemic improvement areas

When to Use Pulse Surveys Instead:

• Rapid feedback on specific topics

• Quick validation of improvements

• Event-triggered surveys (after outage, process change)

• Frequent lightweight checks

Getting Started

1. Navigate to the Surveys section in Span

2. Click "Create Survey" and select "DX Survey"

3. Follow the 6-step wizard to configure your survey

4. Preview as a respondent before launching

5. Launch when ready

6. Monitor participation during survey lifecycle

7. Analyze results and identify improvement priorities

8. Take action and re-survey to measure impact

Support & Questions

For additional help with DX Surveys, contact your Span customer success team or refer to the in-platform documentation.