It also depends on how many comments you write and so it's really interesting to when we're looking at the survey results sometimes we get paragraphs and paragraphs of comments. And other people are just like one liners or they're like me and they don't write any comments at all. So assuming people like me are going through it a little bit quicker, I would say at least 25 minutes on it, which is a chunk of time for sure. The process was very, very long and very responsive for us to be able to get to a place where we're like okay this feels good. Even now we're going into a year of it. We're now thinking okay how does this evolve
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