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
People fear uncertainty, not change
People fear uncertainty, not change If you’ve ever worked on any big project that was […]
“Working with you is like going to therapy.”
“Working with you is like going to therapy.” I was working with a client last […]
The best ideas are stolen
The best ideas are stolen I don’t remember where I first heard it, but someone said […]
It’s all about expectations
It’s all about expectations One of the most critical contributors to the success of a […]
Either you test, or your members will
Either you test, or your members will If I was forced to choose the single […]
But are you really willing to change?
But are you really willing to change? When any organization is making a change in data management […]
Two tips for data conversion
Two Tips for Data Conversion I’ve written a lot about data conversion over the years […]
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 […]
