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

Some context, please

April 21, 2021

Some context, please A pet peeve of mine: A report about associations (e.g., marketing benchmarks report) where …

Some context, please Read More »

Eventually automated emails get ignored

April 14, 2021

Eventually automated emails get ignored During the discovery and development phase of implementing a new …

Eventually automated emails get ignored Read More »

The challenge the AMS providers see

April 7, 2021

The challenge the AMS providers see Over the years I’ve asked AMS providers what they …

The challenge the AMS providers see Read More »

Be careful about “solutioning” too quickly

March 31, 2021

Be careful about “solutioning” too quickly One of the great things about software developers is …

Be careful about “solutioning” too quickly Read More »

What’s our next action?

March 24, 2021

What’s our next action? As you can imagine, I spend a lot of time in …

What’s our next action? Read More »

Don’t automate for the sake of automation

March 17, 2021

Don’t automate for the sake of automation I’m the laziest person in the world. I …

Don’t automate for the sake of automation Read More »

Don’t forget about what got better

March 10, 2021

Don’t forget about what got better Negativity bias is the tendency to focus on only …

Don’t forget about what got better Read More »

Give a little at a time rather than taking away

March 3, 2021

Give a little at a time rather than taking away I’m sure there’s research somewhere …

Give a little at a time rather than taking away Read More »

First, you gotta have the data

February 17, 2021

First, you gotta have the data When I work with clients on a new AMS …

First, you gotta have the data Read More »

Work on your relationship with your AMS vendor

February 10, 2021

Work on your relationship with your AMS vendor It is no coincidence that my most …

Work on your relationship with your AMS vendor Read More »

Scroll to Top