One of the most popular Team Goals that GitClear offers is the goal to "Ensure Developer Satisfaction." It's a good sign that so many managers recognize the essential value of Developer Experience in their product success!
One of the hardest challenges in implementing a Developer Experience strategy that goes beyond lip service: how to quantify the rate to which a team is succeeding at ensuring a positive environment? It's one thing to quantify the rate of code evolution in a repo -- GitClear offers several goals in this vein. But, alas, it's more difficult to quantify "human sentiment" than it is "rate of code change."
Developer Sentiment Surveys are the perfect tool to quantify the otherwise-squishy world of the analog: enthusiasm, emotions, and energy.
linkSet up a Developer Sentiment Survey
Any team on a Pro plan or above can set up and send out regular sentiment surveys to identify opportunities to boost morale or improve consistent deliverability.
The starting point for a new survey is the "Work in Review" => "Developer Sentiment Review" tab.
Upon arriving at this page, a manager can browse through the catalog of developer evaluation questions utilized by the Google DORA team in their published research.
"Satisfaction" is one of 10 different question categories that managers can target
As questions are chosen, they will be added to the list of questions included in the survey:
As questions are chosen, they are added to the survey. The "X" beside a question can be used to remove it.
If you want to re-order the questions, they can be dragged up or down and dropped to a different order within the list of questions. We recommend keeping surveys to 20 questions or less, since developer willpower is likely to wane by the time they reach their tenth question.
linkSurvey anonymity
Near the bottom of the survey creator is a set of options controlling the anonymity of the survey respondents. If you are looking to maximize the veracity of responses, allowing or requiring anonymity is a sound approach.
When a survey is marked as "anonymous optional," the survey owner will be able to see a respondent's responses only if they are logged in when they take the poll. When they arrive at the poll starting page, they will see a message informing them that they can respond anonymously by visiting the poll in a private browsing instance.
When a survey is marked "All responses anonymous," then even if a user is logged in when they respond, their responses will not be associated with their user identity. A notice atop the poll will inform respondents that their responses will not be associated with their user profile.
linkSurvey owner / who can view results?
The poll editor will allow its creator to specify who can view poll results.
For users eligible to view poll results, a link to the results will be provided in the "Publish" section near the top of the poll editor once responses have been recorded.
linkDelivering a new survey to the team
Once you have chosen some questions and a title, your survey is ready to publish. 🚀
Your survey will be sent to all seated team members with a user account on GitClear. Recall that user accounts are free to create. Each registered GitClear user will receive the survey link in an email. The survey creator can preview the poll questions and layout at any time by clicking the survey preview link, located near the title of the poll once it has been published:
Clicking the "n responses received" will show the results for the survey
linkConnection with Developer Satisfaction Team Goal
When you set a goal for Developer Satisfaction, we will periodically send you a reminder to create a new poll. As responses to your poll come in, you will receive periodic notifications in accordance with your notification settings.