Don’t try to do everything at go-live

Don't Try to do Everything at Go-live

When implementing a new AMS, there is a tendency to try to get everything done and "in the system" prior to go-live. After all, you've got this shiny new system with all kinds of new functionality. Why not go for it and have it do everything it can and have that all happen at go-live?

There are plenty of reasons not to do that, but one important one is this: The more you use the system, the more you'll know it and understand it, and the better your decision-making process will be about adding new features and/or processes.

For example, a client of mine was trying to decide whether or not to pay for some customization on their AMS to better manage fundraising. The baseline functionality was "just OK" but the client wanted more. After a long discussion about whether or not to pay for customization, my client said "How about we use the baseline functionality for now and see how it goes. Maybe we'll learn more about how the system works as we use it, and we'll find a better way to do it without having to pay for a customization."

Wise words!

It's literally impossible to know everything about your new software when you go-live. You will always learn more as you use the system. So as you make decisions about what should be available at go-live, consider those things that might make more sense to implement after you've been live with the new system for a while.

Even though it's new and shiny, not everything has to be ready at go-live.

Wes's Wednesday Wisdom Archives

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 »

Dashboards for Data Integrity

February 3, 2021

Dashboards for Data Integrity I’ve written a bunch on data integrity reports. (Click here for …

Dashboards for Data Integrity Read More »

Scroll to Top