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."
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
A client of mine recently wrote the following to me: “It’s so hard to set …
In Dan Gilbert’s book Stumbling on Happiness, he writes: “Experience is unobservable to everyone except …
Lewin’s equation says “behavior is a function of the person in their environment.” (He was …