We try to really boil it down into like the top three areas of focus that are necessary. We kind of try to assess what's really going on and then provide some actionable solution steps. It takes this maybe half an hour to an hour maybe to read, we read through all the comments that people leave in the survey. And we go through it and and turn that into something that executives can get value from without having to wave through all the details.
Matthew and Luke lead Extend’s Developer Experience team, a team that has approached their work in a way that is more forward-thinking than most. In this episode, they cover how they deliver impact at multiple levels of the organization, their journey with productivity metrics, and how they’ve made DevEx a C-level concern.
Discussion points:
- (1:40) How the DevEx team started and where it fits at Extend
- (5:08) Tradeoffs of DevEx reporting into Platform
- (6:40) The mandate and tasks they focus on
- (12:07) The impact of learning and development efforts
- (16:33) How to drive team-level improvements
- (18:44) Why developer experience is becoming more prevalent
- (26:17) How they made DevEx a C-level concern
- (30:27) Their journey with productivity metrics
- (33:10) Advice for presenting DevEx data to executives
- (34:52) The team’s experience using git metrics tools
- (48:30) Being rigorous in leveraging metrics
Mentions and links:
Connect with Matthew and Luke on LinkedIn
Other podcasts mentioned: Manuel Pais; Peloton’s DevEx survey