I often get asked by leaders who are thinking about Devax and developer productivity. And I tell them, no, it's going to be a long, longer journey. So we committed right up front to those check ins and to share back to the engineering organization at least twice a year. We did it all hands quarterly. By doing so, I think we helped alleviate that concern of like, Oh, you're going to go away and spend a lot of money or a lot of engineering efforts and then not do thing for 18 months.
Mike Fisher, the former CTO at Etsy, spearheaded a multi-year developer experience initiative aimed at improving developer happiness and efficiency during his time at Etsy. Here, he shares the story of that initiative, including the pillars of the program and the investment that went into it. Towards the end of the conversation, Mike also shares his perspective on measuring developer productivity.
Discussion points:
- (1:31) What was happening at Etsy when Mike joined
- (4:08) The scaling challenges Etsy faced
- (6:08) Deciding on the term “developer experience”
- (9:35) Whether developer experience is a new approach
- (11:24) The pillars of Etsy’s DevEx initiative
- (15:49) Converting the length of time required for this initiative
- (18:11) The investment allocated to the initiative
- (20:04) Talking about the ROI of devex initiatives
- (22:50) Who was actually leading this work
- (24:37) Etsy’s experience with platform teams
- (30:42) Advice for leaders championing DevEx initiatives
- (34:45) Framing the conversation about getting budget for a DevEx initiative
- (37:45) How leaders can address the efficiency conversation
- (42:00) Measuring productivity
- (45:49) The “experiment velocity” metric
Mentions and links:
Follow Mike on LinkedIn or Twitter
Subscribe to Mike’s newsletter, Fish Food for Thought