Don't move too quickly OR too slowly
This may sound like a big "duh!" but I'll say it anyway: When it comes to selecting and implementing a new AMS, don't move too quickly or too slowly.
If you move too quickly, you are very likely to overlook things. During the selection process, this means overlooking functionality that you will need but hadn't thought to ask about. I've worked with clients who have come to me after selecting a system that they found out could not function the way they needed it to.
Moving too quickly during implementation manifests itself in taking things "live" before they've been thoroughly tested. And as I always tell my clients, either the staff tests before go-live or the customers will test after go-live.
Moving too slowly also has drawbacks. Moving too slowly during the selection process, especially when comparing multiple systems, can make it very difficult to remember which system does what, what systems look like, and so on.
During implementation, moving too slowly can result in a lack of focus by staff, dramatically increased budgets, and frustration from all parties.
What you're looking for is the "Goldilocks" speed. Fast enough that things don't bog down, but slow enough that avoidable mistakes aren't made. As a general rule of thumb, the selection process should be completed in three to four months, and the implementation process between six months and one year. Of course, this may vary dramatically for certain situations, but these are good guidelines to start with.
Remember: Not too quickly, but not too slowly!
![]()
Wes's Wednesday Wisdom Archives
Customer vs. staff
Customer vs. staff In a properly designed AMS, when the customer goes online to your […]
Measuring customer service
Measuring customer service When I work with clients on AMS selection, one question that often […]
Iterate or innovate?
Iterate or innovate? When moving to a new association management system, there is often an implicit […]
Who is in control?
Who is in control? Speaking with a client once about their database project, the client […]
Sometimes Staff Has to do the Work
Sometimes staff has to do the work… As a child, I was attracted to computers […]
Documentation and the Great Resignation
Documentation and the Great Resignation Unless you’ve been living under the proverbial rock, you’ve heard […]
Data Management Strategy
Data Management Strategy Do you know what your data management strategy is? If you have […]
It’s always about trust
It’s always about trust When I work with clients on almost any data management project, […]
You can’t outsource buy-in
You can’t outsource buy-in One factor consistent with all of my most successful projects is […]
Use it or lose it!
Use it or lose it! I’m referring here to the data you collect. If you […]
