When implementing a new AMS (association management system), we typically see all value of the functionality it brings: Things like the ability to process online orders, or being able to capture key data in one system. But one of the greatest values of implementing a new association management software system is often overlooked: re-engineering business processes.
I know, it doesn't sound very exciting, but improving your business processes can be (should be?) a nice side-effect of implementing a new data management system. Any new database should force you to look at how you process everything, from adding records, to adding transactions, to running reports. Implementing a new system gives you an excuse to look at what you're doing now to try and determine if you could be doing things better.
The alternative is that you implement new software that replicates your old processes, which would be an incredible waste of time and money. So when implementing a new system, look for the opportunities to re-engineer, including throwing out processes you don't need anymore.
Nice post. I’d like to add that most AMS vendors have created their process around industry best practices. This means…unless it’s absolutely critical for the delivery of the member experience, adapt your processes to the system. Unnecessary customizing can cause some real headaches down the road.