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
Once you know, what will you do?
Once you know, what will you do? I’ve yet to meet a client who didn’t […]
If it’s not in your AMS, why not?
If it’s not in your AMS, why not? I like to tell my clients they’ll […]
Why checkboxes and tags are awesome and dangerous
Why checkboxes and tags are awesome and dangerous One of the most common functions in […]
Don’t miss obvious engagement data
Don’t miss obvious engagement data What I’ve experienced with my clients over the years is […]
All data requires active management
All data requires active management It’s a simple fact of data management that is often […]
Documentation is critical for consistency
Documentation is critical for consistency There are so many reasons why documenting your data management […]
Consumer demands change and technology changes
Consumer demands change and technology changes When I work with clients on the selection of […]
Why I write
Why I write Thirty years ago, I started a new job as director of membership […]
DAN – The Data Analytics Network
DAN – The Data Analytics Network I’m a huge fan of users groups (both internal […]
Process before technology
Process before technology In a conversation with a client recently, I was reminded (yet again) […]