Mick Pollard Explains How (and Why) Platform Teams Track Developer NPS

July 25, 2019 Dormain Drewitz

 

We've all seen those Net Promoter Score (NPS) surveys ("On a scale of 0 to 10, how likely are you to recommend this product or service...") in our consumer lives. But what if platform teams collected NPS as a metric for developer satisfaction? In this episode, Mick Pollard (@aussielunix, which I totally mispronounced as "aussie linux"... think UNIX!) shares how using NPS shifted the mindset of a platform team. Instead of measuring on velocity, the team ran a simple NPS survey and was shocked at what they found.

Mick shares what the NPS represents, as well as how to go about running the survey. He also shares what needs to happen before and after the survey to build trust with developers and turn the metric into impact. Tune in to hear his recipe for success. 

Resources

Show Notes

 

 

About the Author

Dormain Drewitz

Dormain leads Product Marketing for Pivotal Platform Ecosystem, including GemFire, Pivotal's PCF Services offerings, and ISV offerings for PCF. Previously, she was Director of Product Marketing for Mobile and Pivotal Data Suite. Prior to Pivotal, she was Director of Platform Marketing at Riverbed Technology. Prior to Riverbed, she spent over 5 years as a technology investment analyst, closely following enterprise infrastructure software companies and industry trends. Dormain holds a B. A. in History from the University of California at Los Angeles.

Follow on Twitter More Content by Dormain Drewitz
Previous
PAS, PKS, & RabbitMQ on kubernetes
PAS, PKS, & RabbitMQ on kubernetes

Next
A small batch of validated features is better than a big batch of completed features, with Franck Liso
A small batch of validated features is better than a big batch of completed features, with Franck Liso

An app-tastic tale of lean product design.

Subscribe to Pivotal Conversations on iTunes

Subscribe