New York

October 15–17, 2025

Berlin

November 3–4, 2025

London

June 2–3, 2026

How to design (and listen to) a developer survey

A well-designed developer survey is only the first step towards measuring team health, the important part is knowing how to listen to the results.
October 09, 2023

A well-designed developer survey is only the first step towards measuring team health, the important part is knowing how to listen to the results.

Software teams can be a hard group to measure. Raw output metrics like lines of code written, features shipped, and bugs squashed can go some way towards telling you how a team is doing – but they leave a lot unsaid. Do your developers feel they are being used effectively? Are they able to get the focused time they need? Or are they managing to ship in spite of bureaucratic obstacles, too many meetings, and a lack of direction? To get that kind of information, you need to conduct a developer experience survey.

Join LeadDev.com for free to access this content

Create an account to access our free engineering leadership content, free online events and to receive our weekly email newsletter. We will also keep you up to date with LeadDev events.

Register with google

We have linked your account and just need a few more details to complete your registration:

Terms and conditions

 

 

Enter your email address to reset your password.

 

A link has been emailed to you - check your inbox.



Don't have an account? Click here to register