It was definitely months of design. I think that especially when it comes to developer experience and like understanding that experience is definitely the hardest part. There's also a bunch of stuff that you have to do and then you get the data back and like, and you have to analyze all of it and decide what you're going to do with it. And then we ended up writing a report and so we call it the state of developer experience at Peloton because he actually like produced this pretty long report which goes out to our leadership and platform team.
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