Yesterday,
What do you wish you’d known, back when you were first an admin?
For me, personally, I wish someone had told me to build less. Standardize/improve on one area of CSMs’ work. Then really follow through on enabling the CSMs, seeing how Gainsight was helping (or not), etc.
All y’all experienced admins, how would you answer that question?
The driving factor should always be about what the expected outcome is, not what the proposed solution is. It can be easy to drift into a narrow focus on a solution you are working on only to discover it completely missed the mark of what the goal/expected outcome was.
Just because you can build it, doesn’t mean you should.
And I’ll affirm
I’ll come in with another idea:
Some of what we build takes a lot of thought, energy, bandwidth, trial-and-error (and sometimes tears). Even perfectly-built solutions may not “work” because the results weren’t meaningful or the impact not obvious. Or the company changed strategic directions and thus that work isn’t as interesting as it was before.
That’s OK.
That’s progress.
That’s not an indictment of your expertise as a Gainsight Administrator.
When we construct something cool, we can get wrapped up in the personal pride of delivering a solution, and the sunk cost of the efforts to build. We may want to hang onto it as long as possible because “that’s my baby and I love it.” It’s OK--and it’s even wise--to turn things off, to clean up what’s not used, and to move on to something else that’s providing more value in your CSOps space.
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
