Always, ALWAYS budget for more training
Always, ALWAYS budget for more training.
I don't know how else to say this. But for 98% of all associations implementing a new AMS (or any major new system), the training budget needs to be increased, not decreased.
Yes, I know; systems should be more intuitive; there should be more online, on-demand training options available; and on and on and on. And all of that is happening.
But the reality is, an AMS is a complex system, even for the smallest and "simplest" association. And another reality is, no matter how good the training is that you receive, most learners forget most of what they were taught. (Look at these terrifying stats.)
So yeah, you'll need that initial training, and you'll need some follow-up training. But you'll also need follow-up training to the follow-up training.
So when you look at the training budget, don't cut it, increase it. You'll be happy you did.
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) […]