Budget for feature discovery and adoption
When developing a budget for implementation of a new AMS, one recommendation I always make to my clients is to budget for things staff will discover they want to do once they've learned how to use the new system.
In a nutshell, once staff has started using the new AMS and discover all the new functionality that it brings, they'll want to start using that functionality. Using the new functionality may require training and/or vendor support, so budgeting for this is important. (The vendors are aware of this. For example, Salesforce training calls this "feature discovery and adoption.")
Although on the surface this looks like just one more item for the expense column, feature discovery and adoption is actually a really good thing. What it means is the staff is using the system! And they are trying to get the system to do even more work for them.
As I've written before, user adoption is key to long-term data management success. Feature discovery and adoption is a great illustration of user adoption and one that should be strongly encouraged. So be sure to budget for it.
![]()
Wes's Wednesday Wisdom Archives
Who should “own” the database?
Who should “own” the database? One of the most common questions I get from my […]
What makes you weird?
What makes you weird? When I work with clients on selecting a new association management system, one […]
Why “AMS Consortiums” Don’t Work
Why “AMS Consortiums” Don’t Work About once a year I will get a call from […]
Your vendor will disappoint you
Your vendor will disappoint you I follow politics as a hobby. A past publisher from […]
Learn how to lose
Learn how to lose “Winning is great, sure, but if you are really going to […]
Ownership is Required
Ownership is required When asked for the most common reason AMS implementations fail, I typically respond […]
It’s all relative…
It’s all relative… Over the course of my 22 years of consulting, I’ve consulted with […]
Eliminate to optimize
Eliminate to optimize So much of data management is habit (both good and bad) which is […]
For data governance, ask “Why?”
For data governance, ask “Why?” Recently I’ve had the opportunity to work on several data […]
More on Meetings
More on Meetings I’ve written before about the importance of making sure your meetings are […]
