--- title: "Developer surveys" canonical: "https://support.appfire.com/space/FD/1801945306/Developer%20surveys" format: markdown --- > Macro (aura-html) Once your survey ends, you can view aggregate survey data to understand where your team currently stands. You can also view conversation starters and resources to help you decide where to focus next. ## Permissions All users can automatically access the Developer surveys report in Flow. All users who have taken a survey can see aggregate team results for that survey, as well as resources for additional learning. Additional permissions can be configured to give more survey visibility to individual users. Configure these permissions at the role level. - Ability to view comments and conversation starters. - Ability to view survey results for all surveys, regardless of whether they've taken a survey. ## Developer thriving survey overview The Developer thriving survey is a research-backed approach to understanding and improving team health. The Developer Success Lab wanted to understand how real-world developers and their teams achieve success. Their findings were based on quantitative data from 1,300 developers and rich qualitative data from 15+ hours of interviews and focus group conversations. After analyzing their research, they discovered four factors foundational to a positive developer experience and better team outcomes, such as higher-quality code and greater productivity. The four factors were: - Motivation and self-efficacy - Learning culture - Support and belonging - Agency The Developer thriving survey was designed by the Developer Success Lab to help teams and organizations understand how they are performing on each of the four pillars so they can take steps to improve their culture. As a result of this work, Flow provides you with access to a survey that measures the health of each Developer thriving pillar for both individual teams and your entire organization. This is accompanied by research-backed recommendations from the Developer Success Lab based on your survey results, as well as resources to help you learn more about how to create a healthy culture on your software development teams. ## Understanding Developer thriving aggregate metrics To view aggregate survey results, first select the team you want to view metrics for. If you only have permissions to view your own survey data, you must select the team you were part of when you took the survey. Once the team is selected, you can see the survey's start and end dates, as well as its total response rate. This response rate is determined by the total number of available users who could have taken the survey and the total number of users who did take the survey. If the response rate is below 65%, you'll receive a warning about low participation, and you should encourage your team members to complete the next survey to obtain more accurate and representative results. > ✅ Try one of these recommendations to improve survey participation for your teams: > ✅ > ✅ - Communicate when and how survey results will be reviewed with your teams. > ✅ - When you review survey feedback, identify at least one change your team or organization can make based on the feedback. Make the change, then make sure your team knows this change is a direct result of survey feedback. This helps your teams know their feedback leads to tangible changes. > ✅ - Keep asking for feedback on the change you've made, and adjust accordingly. > ✅ - Keep at it. Participation will increase when your teams are confident that their survey feedback is being listened to and acted on. Next, look at the aggregate survey results for each pillar. These are calculated by averaging the pillar scores across all respondents in the survey. Any users who answered **Prefer not to answer** to more than 50% of the pillar questions will not have their survey responses counted for that pillar. ## Developer sentiment next steps Click each pillar's aggregate data to see more information about that pillar. Here, you can see the aggregate data again, as well as the proportion of users who took the survey whose data is included in the aggregate score. Any user who responded **Prefer not to answer** to more than 50% of questions in the pillar will not have their responses included in the aggregate score. For each pillar, see more information about how it's defined and why it matters. All users have access to the *Resource* tab to learn more about the pillar and the Developer thriving research to help you understand how to improve this pillar. Users with additional survey views also have access to the *Conversation starters* and *Survey comments* tabs. The *Conversation starters*** **tab generates recommended conversation starters for your team based on your pillar score and whether it's high, neutral, or low. Flow gives different recommendations for leaders and managers so you can tailor your conversations to your audience. The *Survey comments* tab lists the comments users left on each question in the pillar. Toggle between questions to see what comments were left for each one.