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
What’s our next action?
What’s our next action? As you can imagine, I spend a lot of time in […]
Don’t automate for the sake of automation
Don’t automate for the sake of automation I’m the laziest person in the world. I […]
Don’t forget about what got better
Don’t forget about what got better Negativity bias is the tendency to focus on only […]
Give a little at a time rather than taking away
Give a little at a time rather than taking away I’m sure there’s research somewhere […]
First, you gotta have the data
First, you gotta have the data When I work with clients on a new AMS […]
Work on your relationship with your AMS vendor
Work on your relationship with your AMS vendor It is no coincidence that my most […]
Dashboards for Data Integrity
Dashboards for Data Integrity I’ve written a bunch on data integrity reports. (Click here for […]
Next-to-Nothing Goals
Next-to-Nothing Goals I saw a Ted Talk by Christine Carter recently discussing the concept of […]
Just because you can…
Just because you can… In response to a recent Wednesday Wisdom on averages hiding the […]
Always ask “Why?”
Always ask “Why?” Little kids ask “Why?” all the time, because they are sponges for […]
