Open Stack

NPS is an industry standard measure.  It is also a super tough standard to score well.  I think people have a tendency to look at a 40 and think they are failing when that is a actually a pretty good score.

I’m a marketer so my bias is towards things like NPS that can show that people who are using OpenStack are more than satisfied with the platform.  This is also something that the naysayers can’t argue with.

I think if we drop NPS, then the haters will have an easy way to ask why and if we have something to hide.






Frank Days | VP, Marketing

Direct: +1.978.707.8010 ext. 1017
frank.days at tesora.com<mailto:frank.days at tesora.com> | @tangyslice | Skype: fmdays
125 CambridgePark Drive, Suite 400, Cambridge, MA 02140




On Dec 11, 2015, at 2:44 PM, Jonathan Proulx <jon at csail.mit.edu<mailto:jon at csail.mit.edu>> wrote:


Yes NPS is what is meant on the agenda.

I actually don't have any recallection why it was added to the
survey, so woudl welcome some discusson on that topic now.

It's on the currnet agenda because Roland was concerned with the delta
in the last two surveys and was looking for more insight into that.

If it's not a useful number (which I can see your case for that) then
we shouldn't collect it an dif we're not going to collect it in the
future there's no point in looking more deeply at it now.

Does anyone recall the thought behind adding NPS or have an argument
for its relevence in our context?

-Jon

On Fri, Dec 11, 2015 at 11:32:48AM -0800, Stefano Maffulli wrote:
:On 12/10/2015 04:11 PM, Shilla Saebi wrote:
:> This is a reminder to let everyone know that we have the monthly user
:> committee meeting scheduled for Monday December 14th at 1900 UTC in
:> #openstack-meeting on freenode.
:
:Thanks for the reminder. Unfortunately I won't be able to join the
:real-time conversation (conflicting work schedule).
:
:Looking at the minimalist agenda (copied below for convenience), I see
:topics that would be very useful to discuss on the mailing list for
:deeper analysis before bringing them to real-time chat.
:
:I would like to debate the NP score, which I assume is the Net Promoter
:score. There are many strong reasons for removing the NPS from the
:survey altogether.
:
:The main objection, NPS is used to track *customers* loyalty to a
:*brand*. For typical corporations, they can identify with precision
:customers and brand, therefore effectively measure such loyalty.
:
:OTOH OpenStack Foundation has many types of customers, the concept of
:its products is not exactly defined and ultimately OpenStack can't be
:considered a brand in the sense of the original article that launche NPS
:https://hbr.org/2003/12/the-one-number-you-need-to-grow/
:
:I'd argue that the NPS collected in the Survey in its current form has
:no value whatsoever. http://dilbert.com/strip/2008-05-08
:
:Is the User Committee convinced that an open source project like
:OpenStack gets any value from tracking this score? Why exactly is that
:number tracked in the survey, what exactly does the UC want to get from
:that number, what actionable results are expected from it?
:
:/stef
:
:PS adding the Proposed Agenda below so you all can see it without extra
:clicks
:
:* Meeting schedule - proposal to witch to biweekly (from monthly) & have
:alternating time with 1 APAC friendly
:* Next steps for Survey analysis (cuts against NP score)
:* discuss where we want to take the UC and what we can change
:
:
:_______________________________________________
:User-committee mailing list
:User-committee at lists.openstack.org<mailto:User-committee at lists.openstack.org>
:http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee

--

_______________________________________________
User-committee mailing list
User-committee at lists.openstack.org<mailto:User-committee at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20151211/56f16b31/attachment-0001.html>