Really loved this conversation about again not pursuing productivity but looking at it as a result of developer JOY! so lovely (though I wonder how many orgs fee the same) https://thenewstack.io/boost-developer-productivity-by-reducing-their-paper-cuts/

Love this! I think it really depends on the org honestly, I've seen both

A good read, thanks! I have some questions: 1. The team grew from 4 to 8 and supports 150 FTEs. Is that enough, or does it need to grow more? What would be too big for them? 2. Was NPS useful for them or more that it seemed the easiest to implement? (It's mentioned that they did it, but I'm dubious that it is the right methodology. Would love to hear whether it proved durable in any way.)

@Marsh Gardiner I have shared your Qs with Jason and asked if he wants to join this community

I guess they used NPS because it's (unfortunately) the "industry standard". CSAT would be much better for this kind of surveys.

Hi @Marsh Gardiner , thanks for your questions! 1. I think we could use a few more, there are some areas like core internal product-focused platforms and tools in addition to development-focused platforms and tools that I’d like to expand into. But it would also involve splitting the team a bit to help control scope. 2. I think NPS was easiest to try and we wanted to see what it might tell us. It wasn’t something we found that useful though, because of how many different things it could be related to.