Ownership is required
When asked for the most common reason AMS implementations fail, I typically respond "lack of testing." But implementation is only the first step in the process. Long-term success for the AMS requires ownership.
What do I mean by ownership? I mean that someone (or a team) internally has actual responsibility for the long-term success of the AMS. Too often what happens after implementation is each department takes ownership of only its own area, which ultimately leads to silos and, longer-term, to a system that is no longer working at optimal levels.
Once you're past implementation, someone (or a team) has to have responsibility for the ongoing maintenance and support of the system. If your organization doesn't or can't have a single individual do this, create a team of representatives from key areas (typically membership, events, and finance, along with others) that are responsible for working together to keep things on track. (Click here to read more about these teams.)
But whether it's one person or a team, the "owner" has to be clearly identified and has to focus on the long-term success of the system. The system will not take care of itself!
![]()
Wes's Wednesday Wisdom Archives
Look up PARTIAL names!
Look up PARTIAL names! Train your staff to do look ups on partial names, not full […]
Not Just Technology
Not Just Technology There was recently a discussion on the ASAE online community about project management […]
Consider quitting
Consider quitting Patient: “Doctor, it hurts when I do this.” Doctor: “Then stop doing that.” […]
There is nothing so permanent as business rules
There is nothing so permanent as business rules Nobel Prize-winning economist Milton Friedman said, “There’s nothing […]
Budget for feature discovery and adoption
Budget for feature discovery and adoption When developing a budget for implementation of a new […]
Customize staff pages for better user adoption
Customize staff pages for better user adoption The single most important element to data management […]
Don’t ask questions for which you already know the answer
Don’t ask questions for which you already know the answer I was recently completing an […]
All decisions involve risk
All decisions involve risk Whether it’s choosing a new AMS or introducing a new product […]
Try flowcharting your processes
Try flowcharting your processes Working with a client recently on their membership join process reminded me […]
“I just want a system I don’t have to fight with.”
“I just want a system I don’t have to fight with.” I asked my client: […]
