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
But are you really willing to change?
But are you really willing to change? When any organization is making a change in data management […]
Two tips for data conversion
Two Tips for Data Conversion I’ve written a lot about data conversion over the years […]
Who should “own” the database?
Who should “own” the database? One of the most common questions I get from my […]
What makes you weird?
What makes you weird? When I work with clients on selecting a new association management system, one […]
Why “AMS Consortiums” Don’t Work
Why “AMS Consortiums” Don’t Work About once a year I will get a call from […]
Your vendor will disappoint you
Your vendor will disappoint you I follow politics as a hobby. A past publisher from […]
Learn how to lose
Learn how to lose “Winning is great, sure, but if you are really going to […]
It’s all relative…
It’s all relative… Over the course of my 22 years of consulting, I’ve consulted with […]
Eliminate to optimize
Eliminate to optimize So much of data management is habit (both good and bad) which is […]
For data governance, ask “Why?”
For data governance, ask “Why?” Recently I’ve had the opportunity to work on several data […]
