If you're sent a link to the Developer sentiment survey, it means your organization wants to understand your team's health and culture.
Before taking the survey, there are a few things you should know about survey responses so you can feel comfortable sharing your true and honest feelings.
In this article
How Flow handles and protects survey responses
Survey responses are anonymous. Neither survey creators nor other admins on your Flow plan can see or access information about who has or hasn't taken a survey. They also cannot associate individual survey responses with the users who have taken a survey.
To additionally protect survey responses, a minimum of five responses must exist before aggregated data for a survey will be shown in Flow.
Comments left during the survey will be shown as written in the survey response. There's no minimum number of comments needed before comments will display, as long as there are at least five total survey responses.
By default, all users can view aggregate survey data for surveys they've taken. Comment access is restricted and must be enabled at the role level. Users can be given permissions to view aggregate survey data for all surveys and teams, even if they haven't completed them.
If you have any questions about how your survey data is being used by your organization, reach out to the survey creator or your leader for additional information.
Accessing the survey
Depending how your survey is configured, you'll either receive a link shared directly by the team leading the survey at your organization, or Flow will send an automated Slack message to your team channel.
This survey link cannot be accessed or used before the survey start date. If you try to use it ahead of time, you'll receive an error message. Similarly, you cannot access the survey link once the survey has ended. You must have access to log into Flow to take the survey. If you don't have access, talk to your leader about how to get access so you can participate in the next survey.
Surveys are taken in Flow, No third-party survey processor is involved.
You can only take a survey once. Depending how your organization shares the survey links, you may receive multiple identical links—but you can only take the survey once. Survey links are unique per survey, not unique per user. There can be no more than one survey per organization per quarter.
Surveys are open for 10 full weekdays (Monday–Friday) and cannot end on a weekend day. Usually this means the survey will end 14 days after the start date, but if the start date is on a Saturday or Sunday, it will end the second Friday after it starts, meaning it will be open for 12 or 13 days. Slack survey notifications automatically include the start and end dates of the survey, but if you're not sure about the survey dates, reach out to the survey creator.
Taking the survey
The survey is made up of ten questions across the four Developer thriving pillars: Agency, Learning culture, Motivation and self-efficacy, and Support and belonging. The survey should take about five minutes.
For each question, respond on a scale from Strongly agree to Strongly disagree. Add an optional comment to each response, as desired. Questions are broken up into four pages, one for each pillar. You cannot skip any questions, but you can respond Prefer not to answer for as many questions as you'd like.
Use the Previous and Next buttons to navigate between pillars while taking the survey. You can't navigate to the next pillar until all previous pillars' questions have been answered.
Once you're finished, submit the survey and close the browser window.
You can't save an in-progress survey. If you close the window before you submit the survey, all progress will be lost and you'll need to start from the beginning.
Once your survey has been submitted, you can't view your responses or the survey again.
As soon as the survey window closes, survey results are available to view. Learn more about Developer sentiment surveys.