LogoLogo
Book a demoLog in
  • Swarmia documentation
  • Getting started
    • Get started in 15 minutes
    • Integrations
      • GitHub
        • GitHub Enterprise Server
        • Multiple GitHub organizations
        • Forked repositories
        • Troubleshooting
          • Reinstalling the Swarmia GitHub app
          • Updating app permissions
          • Installing Swarmia outside of GitHub Marketplace
      • Jira
        • Jira Server and Jira Data Center
        • Multiple Jira organizations
      • Linear
        • Private Linear teams
        • Disconnect Linear
      • Slack
        • Private Slack channels
      • Authentication
        • Google Single Sign-On
          • Frequently asked questions
        • Okta Single Sign-On
      • HR systems
      • Data export
        • Data cloud
        • Export data as a CSV file
      • Other integrations
        • Other issue tracker integrations
        • Other source code hosting integrations
  • Configuration and data quality
    • Teams & members
      • Creating & managing teams
        • Teams API
      • Contributors
      • Roles and permissions
      • Inviting team members
    • Issue tracker configuration
      • Jira configuration
      • Jira best practices
      • Linear configuration
    • Pull request exclusions
    • Linking pull requests to issues
    • Investment categories
    • Deployments
      • Generate deployments from merged pull requests
      • Generate deployments from GitHub deployments
      • Generate deployments from GitHub checks
      • Generate deployments via the API
        • Generate deployments for monorepos via the API
    • Sprint configuration
  • Use cases
    • Improve pull request flow
      • Pull request insights
      • Reducing pull request cycle time
      • Review code faster
      • Managing pull requests in progress with the Pull Request view
      • Diagnosing low pull request throughput
      • Analyzing pull request batch size
  • Improve your team's focus
    • Optimizing issue cycle time
    • Analyzing activity patterns on Work Log
    • Grouping activity on the Work Log view
    • Focus summary
  • Balance engineering investments
    • Activity and effort-based models
    • Categorizing work
    • Common problems with balancing engineering investment
  • Deliver strategic initiatives
    • Forecasting initiatives
  • Capitalize software development costs
  • Run developer experience surveys
    • Creating a survey
    • Managing surveys
    • Viewing and sharing survey results
    • How we show your survey responses
    • Survey communication guide and templates
  • Track DORA metrics
    • Automatic change failure detection
    • How Swarmia links PRs to deployments
  • Coach software developers
  • Get visibility into your CI pipeline
  • Continuous improvement
    • Working agreements
  • Notifications
    • Team notifications
    • Personal notifications
  • Retrospectives with Swarmia
  • Metrics & definitions
    • Pull request cycle time
      • What's the difference between "Change lead time" and "Pull request cycle time" metrics in Swarmia?
    • Issue cycle time
      • Defining issue lifecycle and cycle time
    • Developer effort (FTEs)
  • DORA metrics
    • Change lead time
    • Deployment frequency
    • Mean time to recovery
    • Change failure rate
  • Throughput
  • Time to deploy
  • Batch size
  • Flow efficiency
  • Scope creep
  • Sprints
  • Frequently asked questions
    • How do you treat weekends in metrics?
    • Tracking squashed commits
    • How do merge queues affect my metrics?
    • Why is my commit not visible in Swarmia?
    • How do I account for people leaving my organization?
  • Resources
    • Security & data retention
      • Data security
      • Data access
      • Swarmia IP Addresses
      • Single Sign-On (SSO) / SAML
      • Can I get a copy of the SOC 2 Type II audit report?
      • Deleting your organization
  • Pricing & plans
    • Compare plans
    • Free plan
    • Do I need a credit card to start a free trial?
    • What are the differences between the individual modules and the standard plan?
    • How do you determine the number of developers for billing?
    • What happens to customers with the Lite plan after the December 2024 pricing and plan change?
  • Changelog
On this page
  • Analyzing the results
  • Heatmap
  • Comparisons
  • Questions & comments
  • Participation
  • Related metrics
  • Publishing the results
  • Downloading the results
  • Scores
  • Comments
  • Participation

Was this helpful?

  1. Run developer experience surveys

Viewing and sharing survey results

After a survey ends, you can review the results, publish them to your teams, or export them

PreviousManaging surveysNextHow we show your survey responses

Last updated 1 month ago

Was this helpful?

Results are available only from surveys that have ended. You can't view results from live surveys, but you can .

To access a survey's results, click on the name of a survey that has ended, or select View results from the right-side menu.

Analyzing the results

Heatmap

The heatmap shows a color-coded overview of each team's average ratings across the survey.

You can see the number of responses from a particular team by hovering your mouse on the row.

The scores are aggregated on all levels of the team hierarchy. You can expand and collapse teams to view just the scores you're interested in.

The main overview shows average scores across all the questions in a topic. You can expand the topics to see a more detailed breakdown of each question.

You can click any of the cells in the heatmap to see more details on the Questions & comments tab.

Comparisons

The "Compare with..." menu in the heatmap offers you three ways to compare survey results:

  • Survey average: Shows how much each team is above or below the survey’s average (all teams) in each topic and question.

  • Industry benchmarks: Shows how your results compare with average survey ratings for each question from 50+ companies using Swarmia. You can choose from three percentiles: p50 (median), p75, and p90.

    • The topic average benchmarks are calculated only based on the questions you have included in the survey.

    • Any custom questions you have created are ignored in the topic averages.

  • Another survey: Select any of your surveys and see the changes in scores between them.

    • If the two surveys have a different set of questions, the topic averages are calculated based on the overlapping questions. Questions available only for one of the surveys are ignored.

    • Each team is considered the same team across the two surveys, regardless of any changes to its members or sub-teams.

    • The ratings for the "All teams" row are calculated based on the teams that are included in both surveys. In other words, it's based on all the team scores visible in the heatmap, ignoring the scores not shown in the heatmap.

Questions & comments

On the Questions & comments tab, you can see all the comments and the detailed distribution of ratings by topic, question, and team.

On the left side, you have controls for topic and team filters.

On the right, you have options for sorting by

  • Original order

  • Highest score

  • Lowest score

  • Most comments

  • Most skips

Click any of the questions to see its comments.

You can hover over the distribution bar to see the detailed rating counts.

Participation

On the Participation tab, you can see the response rate in each team.

Related metrics

Some of the survey questions have related metrics to provide more context on the results. You can find them by expanding the questions on the Questions & comments tab. You can click the metrics to access the relevant Swarmia page filtered by the selected team.

Publishing the results

If the results contain sensitive or offensive comments, contact Swarmia to get them removed.

When you're ready to show the results to others, select Publish results in the top-right corner. Everyone in your Swarmia organization will get access to the results. You'll also get a link to share them easily with the teams.

Published results can be unpublished by clicking the Published button.

Downloading the results

You can also export the results to use them elsewhere. Just click the Download survey results button in the top-right corner.

You'll get a ZIP archive with three comma-separated values (CSV) files:

Scores

One row for each team-question pair:

  • question: The question the rating relates to

  • questionGroup: The topic the question belongs to

  • team: The team associated with this rating (selected as their primary team by the respondents)

  • rating: The average rating the team gave for the question on a scale from 1 to 5 (excluding skips). If everyone in the team skipped the question, the value is null.

  • numberOfSkips: The number of responses that skipped the question

  • totalNumberOfRespondents: The number of people in the team who selected it as their primary team and responded to the survey (= rated or skipped the question)

  • numberOf1Ratings: The number of score 1 ratings (strongly disagree) given

  • numberOf2Ratings: The number of score 2 ratings (disagree) given

  • numberOf3Ratings: The number of score 3 ratings (neutral) given

  • numberOf4Ratings: The number of score 4 ratings (agree) given

  • numberOf5Ratings: The number of score 5 ratings (strongly agree) given

Comments

One row for each comment:

  • question: The question the comment relates to

  • questionGroup: The topic the question belongs to

  • team: The primary team the comment's author selected in the survey

  • comment: The contents of the comment

  • authorName: The name of the user who wrote the comment

Participation

One row for each team:

  • totalNumberOfRespondents: The number of people in the team who responded to the survey

  • totalNumberOfTeamMembers: The number of people in the team who had access to the survey

The benchmarks are available for .

The links work also the other way around. You can see the latest survey results for the selected team within the selected timeframe next to your , , and . To see the rating distribution and comments, simply click on the score to access the detailed survey report.

After the survey ends, the results are first available only to the survey creator and . This allows you to review them before sharing them with your team.

Swarmia’s built-in questions
pull request data
issue insights
DORA metrics
admins
view their participation numbers