Give experienced admins an "opt-out" on in-app notifications

Lets not forget many features roll out as MVPs and are not ready to be used widely.  I understand that Gainsight needs feedback but we have to focus on our teams trusting the system and MVPs take away from that trust

Our adoption of Gainsight fragile as we get CSMs to adopt current features. If they get messages about new features, it will hurt our adoption. I’d love to turn off this feature so I can have them focus on using the current tools. 

+1 on all the points made above, especially anything to do with requiring IT/legal approval. 

Our users have a hard enough time knowing what to do with their day, we don’t need any additional conflicting advice on feature usage. Not to mention unwanted pop-ups that distract them from completing their work.

Gainsight: “We are going to send you less email!”

Also Gainsight: sends an email to tell us that

But in all seriousness... as a program manager for my org’s digital CS program, I found this was a really odd email to receive. The purpose of digital comms is to tell customers what they really need to know. This email was not worth the time.

+1

We turn on features to test but do not roll them out all the time. GS requires strict enablement due to how configurable the tool is and this kind of notification undermines our ability to do our due diligence

Agree with what everyone has said here. Our teams are constantly being inundated with new tools and new features, so we’re very calculated about when we introduce new things, and also provide detailed use cases specific to the org and not just a general overview so that it speaks more to how they could use it.  Adding in more noise to their day or a general description may serve to annoy rather than empower.  There are also features that just flat out won’t work for certain roles - looking at you Group Send.  So, telling ALL our users about a feature that they can’t even use seems like it would only make more work for an already overwhelmed admin.  Now, if you gave me the ability to customize the message and the audience, that would be another story.  Please consider allowing an opt out.

I’m not sure what else new I can add here, but in addition to agreeing with my colleagues above I would add/reiterate two other points:

1. Some items in Gainsight are “on” and you can’t really turn them off, even if you don’t use them. So I’d be concerned that Gainsight’s definition of “deployed” vs. what any given org would for any given feature.
2. My one slight disagreement is that I don’t think this should be an opt-out. I think this should be an opt-in. This could be an interesting feature for orgs that want or need it, but we should be able to decide if we want to join the program(s), not have to take extra steps to get out of the program(s).
   1. As a follow up to this - Gainsight is notorious for making changes and not really announcing them, so we’d have to constantly monitor if there is a new thing we have to “switch off”. Or, more concerning, things that get “switched back on” because it’s somehow different now so it’s technically a new thing (e.g., just look at reporting on Source in things like Asset usage - you have Dashboard, DASHBOARD, HOME_PAGE - all reporting. Do I have to manage toggles for all of these???)

Disagree. If Gainsight is going to start flooding my end users with in-app messages, I absolutely want to be informed before they do so that I can register my strongest opposition to it. This is exactly the type of email I want to receive from Gainsight - just not the BS marketing stuff.

Fantastic idea, ​@bradley. I’d much rather get a notification that a new feature/communication/etc. is available for us to toggle on (default state = opted out), than to be told that something will be/has been turned on, and know that we need to take action and toggle it off (default state = opted in) because our environment is now doing something we didn’t ask for.