I've loved this conversation because we've woven in so many of your reflections as you're thinking about your next devx survey. And then I'm going to focus around focusing on getting that invite from executive leadership. One thing you had mentioned to me before the show was that you had gone into that previous surveys and even the time period following those surveys with some nervousnessaround the value of these surveys. Yeah, I mean, I think actually my entire time he's peloton has been this theme of standing up a new function or like okay I hope this is going to be useful and I hope it is.
Thansha Sadacharam, who leads Tech Learning and Insights at Peloton walks us through the journey of building the company’s developer experience survey. She shares what went into the survey’s design, rollout, and maintenance, as well as the different teams involved.
Discussion points:
- (1:19) Where the idea for running a developer survey originated
- (6:36) Advice for other leaders getting buy-in for these initiatives
- (11:27) The first steps in designing the survey
- (18:21) How the survey incorporated benchmarking
- (20:30) Measuring developer satisfaction
- (22:37) Refining the question items
- (25:50) How long the survey was
- (26:50) What was involved in trimming the questions
- (29:28) Writing survey questions
- (33:12) How much time was spent developing the survey
- (35:19) The communication plan for launching the survey
- (42:05) Driving participation rates
- (45:21) Sampling and how often surveys are being sent
- (49:21) How the information was presented
- (54:10) Feeling nervous about sending out surveys
Mentions and links
Follow Thansha on LinkedIn