Don’t move too quickly OR too slowly

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

Perfection is expensive (in fact, it’s not possible!)

April 22, 2026

Perfection is expensive (in fact, it’s not possible!) “Perfection is expensive. The last 5 percent […]

AI is a journey, not a destination

April 15, 2026

AI is a journey, not a destination Lately I’ve noticed a lot of associations talking […]

Action produces information

April 8, 2026

Action produces information “Action produces information. If you’re unsure of what to do, just do […]

Why a single source of truth is so beneficial…

March 25, 2026

Why a single source of truth is so beneficial… The holy grail of data management is […]

Just because you can, doesn’t mean you should

March 18, 2026

Just because you can, doesn’t mean you should I’ve worked in and with associations for well […]

Data doesn’t need to be perfect to be useful

March 4, 2026

Data doesn’t need to be perfect to be useful “Your data doesn’t have to be […]

Don’t just clean data, clean reports and queries

February 25, 2026

Don’t just clean data, clean reports and queries One of the reasons I exhort my […]

Don’t forget, your staff have day jobs…

February 18, 2026

Don’t forget, your staff have day jobs… The vast majority of my work is finite […]

Beware the automated “How did we do?” trap!

February 11, 2026

Beware the automated “How did we do?” trap! One of the downsides of technology is […]

Hindsight is 20/20

February 4, 2026

Hindsight is 20/20 I’m currently working with a client that is moving from their legacy […]

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top